1. 13 2月, 2017 1 次提交
    • M
      flash: complete CONFIG_SYS_NO_FLASH move with renaming · e856bdcf
      Masahiro Yamada 提交于
      We repeated partial moves for CONFIG_SYS_NO_FLASH, but this is
      not completed. Finish this work by the tool.
      
      During this move, let's rename it to CONFIG_MTD_NOR_FLASH.
      Actually, we have more instances of "#ifndef CONFIG_SYS_NO_FLASH"
      than those of "#ifdef CONFIG_SYS_NO_FLASH".  Flipping the logic will
      make the code more readable.  Besides, negative meaning symbols do
      not fit in obj-$(CONFIG_...) style Makefiles.
      
      This commit was created as follows:
      
      [1] Edit "default n" to "default y" in the config entry in
          common/Kconfig.
      
      [2] Run "tools/moveconfig.py -y -r HEAD SYS_NO_FLASH"
      
      [3] Rename the instances in defconfigs by the following:
        find . -path './configs/*_defconfig' | xargs sed -i \
        -e '/CONFIG_SYS_NO_FLASH=y/d' \
        -e 's/# CONFIG_SYS_NO_FLASH is not set/CONFIG_MTD_NOR_FLASH=y/'
      
      [4] Change the conditionals by the following:
        find . -name '*.[ch]' | xargs sed -i \
        -e 's/ifndef CONFIG_SYS_NO_FLASH/ifdef CONFIG_MTD_NOR_FLASH/' \
        -e 's/ifdef CONFIG_SYS_NO_FLASH/ifndef CONFIG_MTD_NOR_FLASH/' \
        -e 's/!defined(CONFIG_SYS_NO_FLASH)/defined(CONFIG_MTD_NOR_FLASH)/' \
        -e 's/defined(CONFIG_SYS_NO_FLASH)/!defined(CONFIG_MTD_NOR_FLASH)/'
      
      [5] Modify the following manually
        - Rename the rest of instances
        - Remove the description from README
        - Create the new Kconfig entry in drivers/mtd/Kconfig
        - Remove the old Kconfig entry from common/Kconfig
        - Remove the garbage comments from include/configs/*.h
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      e856bdcf
  2. 26 1月, 2017 4 次提交
  3. 24 1月, 2017 1 次提交
  4. 21 1月, 2017 1 次提交
  5. 04 12月, 2016 1 次提交
  6. 26 10月, 2016 1 次提交
  7. 24 10月, 2016 7 次提交
  8. 12 10月, 2016 2 次提交
  9. 20 9月, 2016 1 次提交
  10. 17 9月, 2016 1 次提交
  11. 10 9月, 2016 1 次提交
  12. 07 9月, 2016 1 次提交
  13. 22 7月, 2016 1 次提交
  14. 02 7月, 2016 2 次提交
  15. 28 6月, 2016 2 次提交
    • P
      common: add new boot media kconfig entry · faaef73f
      Peng Fan 提交于
      Add CONFIG_{SD|NAND|ONENAND|SPI|QSPI|SATA}_BOOT kconfig entries.
      
      SoCs supports loading U-Boot from different medias to DRAM, such as
      i.MX6/7 supports loading U-Boot to DRAM from sd/emmc/nand/qspi/spi/sata
      and etc. For i.MX, imximage will generate different IVT headers according
      to boot medias.
      Signed-off-by: NPeng Fan <peng.fan@nxp.com>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Heiko Schocher <hs@denx.de>
      Cc: Joe Hershberger <joe.hershberger@ni.com>
      Cc: Bin Meng <bmeng.cn@gmail.com>
      Cc: Christophe Ricard <christophe-h.ricard@st.com>
      Cc: Nikita Kiryanov <nikita@compulab.co.il>
      Cc: Francois Retief <fgretief@spaceteq.co.za>
      Cc: Tom Rini <trini@konsulko.com>
      faaef73f
    • P
      Kconfig: make NOR_BOOT a common option · d14739ff
      Peng Fan 提交于
      Not only am335x supports booting from NOR, i.MX6 SoCs also
      supports booting from NOR. Make NOR_BOOT a common
      option to let different SoCs share it.
      Signed-off-by: NPeng Fan <peng.fan@nxp.com>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Heiko Schocher <hs@denx.de>
      Cc: Joe Hershberger <joe.hershberger@ni.com>
      Cc: Christophe Ricard <christophe-h.ricard@st.com>
      Cc: Bin Meng <bmeng.cn@gmail.com>
      Cc: Francois Retief <fgretief@spaceteq.co.za>
      Cc: Tom Rini <trini@konsulko.com>
      Reviewed-by: NSimon Glass <sjg@chromium.org>
      d14739ff
  16. 20 6月, 2016 1 次提交
    • M
      autoboot: add CONFIG_AUTOBOOT to allow to not compile autoboot.c · 41598c82
      Masahiro Yamada 提交于
      Since commit bb597c0e ("common: bootdelay: move CONFIG_BOOTDELAY
      into a Kconfig option"), CONFIG_BOOTDELAY is defined for all boards.
      
      Prior to that commit, it was allowed to unset CONFIG_BOOTDELAY to
      not compile common/autoboot.c, as described in common/Makefile:
      
        # This option is not just y/n - it can have a numeric value
        ifdef CONFIG_BOOTDELAY
        obj-y += autoboot.o
        endif
      
      It was a bit odd to enable/disable code with an integer type option,
      but it was how this option worked before that commit, and several
      boards actually unset it to opt out of the autoboot feature.
      
      This commit adds a new bool option, CONFIG_AUTOBOOT, and makes
      CONFIG_BOOTDELAY depend on it.
      
      I chose "default y" for this option because most boards use the
      autoboot.  I added "# CONFIG_AUTOBOOT is not set" for the boards that
      had not set CONFIG_BOOTDELAY prior to the bad commit.
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      41598c82
  17. 17 6月, 2016 1 次提交
  18. 10 6月, 2016 1 次提交
  19. 25 1月, 2016 1 次提交
    • S
      Move all command code into its own directory · 72a8cf8d
      Simon Glass 提交于
      There are a lot of unrelated files in common, including all of the commands.
      Moving them into their own directory makes them easier to find and is more
      logical.
      
      Some commands include non-command code, such as cmd_scsi.c. This should be
      sorted out at some point so that the function can be enabled with or without
      the associated command.
      
      Unfortunately, with m68k I get this error:
      
      m68k:  +   M5329AFEE
      +arch/m68k/cpu/mcf532x/start.o: In function `_start':
      +arch/m68k/cpu/mcf532x/start.S:159:(.text+0x452): relocation truncated to fit: R_68K_PC16 against symbol `board_init_f' defined in .text.board_init_f section in common/built-in.o
      
      I hope someone can shed some light on what this means. I hope it isn't
      depending on the position of code in the image.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      Reviewed-by: NBin Meng <bmeng.cn@gmail.com>
      Reviewed-by: NHeiko Schocher <hs@denx.de>
      Acked-by: NStefan Roese <sr@denx.de>
      Acked-by: NPrzemyslaw Marczak <p.marczak@samsung.com>
      72a8cf8d
  20. 14 1月, 2016 1 次提交
  21. 20 11月, 2015 1 次提交
    • S
      console: Add a console buffer · 9854a874
      Simon Glass 提交于
      It is useful to be able to record console output and provide console input
      via a buffer. This provides sandbox with the ability to run a command and
      check its output. If the console is set to silent then no visible output
      is generated.
      
      This also provides a means to fix the problem where tests produce unwanted
      output, such as errors or warnings. This can be confusing. We can instead
      set the console to silent and record this output. It can be checked later
      in the test if required.
      
      It is possible that this may prove useful for non-test situations. For
      example the console output may be suppressed for normal operations, but
      recorded and stored for access by the OS. That feature is not implemented
      at present.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      9854a874
  22. 19 11月, 2015 1 次提交
  23. 13 11月, 2015 1 次提交
  24. 23 10月, 2015 1 次提交
    • N
      drivers: Introduce a simplified remoteproc framework · ddf56bc7
      Nishanth Menon 提交于
      Many System on Chip(SoC) solutions are complex with multiple processors
      on the same die dedicated to either general purpose of specialized
      functions. Many examples do exist in today's SoCs from various vendors.
      Typical examples are micro controllers such as an ARM M3/M0 doing a
      offload of specific function such as event integration or power
      management or controlling camera etc.
      
      Traditionally, the responsibility of loading up such a processor with a
      firmware and communication has been with a High Level Operating
      System(HLOS) such as Linux. However, there exists classes of products
      where Linux would need to expect services from such a processor or the
      delay of Linux and operating system being able to load up such a
      firmware is unacceptable.
      
      To address these needs, we need some minimal capability to load such a
      system and ensure it is started prior to an Operating System(Linux or
      any other) is started up.
      
      NOTE: This is NOT meant to be a solve-all solution, instead, it tries to
      address certain class of SoCs and products that need such a solution.
      
      A very simple model is introduced here as part of the initial support
      that supports microcontrollers with internal memory (no MMU, no
      execution from external memory, or specific image format needs). This
      basic framework can then (hopefully) be extensible to other complex SoC
      processor support as need be.
      Reviewed-by: NSimon Glass <sjg@chromium.org>
      Signed-off-by: NNishanth Menon <nm@ti.com>
      Acked-by: NSimon Glass <sjg@chromium.org>
      ddf56bc7
  25. 21 10月, 2015 1 次提交
  26. 31 8月, 2015 2 次提交
  27. 13 8月, 2015 1 次提交
    • N
      kconfig: add config option for shell prompt · 181bd9dc
      Nikita Kiryanov 提交于
      Add option to set shell prompt string from menuconfig and migrate
      boards globally.
      
      The migration is done as follows:
      - Boards that explicitly and unconditionally set CONFIG_SYS_PROMPT had the
        entry moved to their defconfig files.
      - Boards that defined some kind of #ifdef logic which selects the
        CONFIG_SYS_PROMPT (for example qemu-mips) got an #undef CONFIG_SYS_PROMPT
        right before the #ifdef logic and were left alone.
      - This change forces CONFIG_SYS_PROMPT to be a per board decision, and thus
        CONFIG_SYS_PROMPT was removed from all <soc>_common.h and <arch>_common.h
        files. This results in a streamlined default value across platforms, and
        includes the following files: spear-common, sunxi-common, mv-common,
        ti_armv7_common, tegra-common, at91-sama5_common, and zynq-common.
      - Boards that relied on <arch/soc>_common.h values of CONFIG_SYS_PROMPT were
        not updated in their respective defconfig files under the assumption that
        since they did not explicitly define a value, they're fine with whatever
        the default is.
      - On the other hand, boards that relied on a value defined in some
        <boards>_common.h file such as woodburn_common, rpi-common,
        bur_am335x_common, ls2085a_common, siemens_am33x_common, and
        omap3_evm_common, had their values moved to the respective defconfig files.
      - The define V_PROMPT was removed, since it is not used anywhere except for
        assigning a value for CONFIG_SYS_PROMPT.
      
      Cc: Tom Rini <trini@konsulko.com>
      Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>
      Cc: Stefano Babic <sbabic@denx.de>
      Cc: Igor Grinberg <grinberg@compulab.co.il>
      Signed-off-by: NNikita Kiryanov <nikita@compulab.co.il>
      [trini: Add spring, sniper, smartweb to conversion]
      Signed-off-by: NTom Rini <trini@konsulko.com>
      181bd9dc