1. 12 Oct, 2016 1 commit
  2. 20 Sep, 2016 1 commit
  3. 16 Sep, 2016 1 commit
  4. 09 Sep, 2016 1 commit
  5. 07 Sep, 2016 1 commit
  6. 22 Jul, 2016 1 commit
  7. 01 Jul, 2016 2 commits
  8. 28 Jun, 2016 2 commits
    • Peng Fan's avatar
      common: add new boot media kconfig entry · faaef73f
      Peng Fan authored
      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: 's avatarPeng 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
    • Peng Fan's avatar
      Kconfig: make NOR_BOOT a common option · d14739ff
      Peng Fan authored
      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: 's avatarPeng 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: 's avatarSimon Glass <sjg@chromium.org>
      d14739ff
  9. 20 Jun, 2016 1 commit
    • Masahiro Yamada's avatar
      autoboot: add CONFIG_AUTOBOOT to allow to not compile autoboot.c · 41598c82
      Masahiro Yamada authored
      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: 's avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      41598c82
  10. 17 Jun, 2016 1 commit
  11. 09 Jun, 2016 1 commit
  12. 25 Jan, 2016 1 commit
    • Simon Glass's avatar
      Move all command code into its own directory · 72a8cf8d
      Simon Glass authored
      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: 's avatarSimon Glass <sjg@chromium.org>
      Reviewed-by: 's avatarBin Meng <bmeng.cn@gmail.com>
      Reviewed-by: 's avatarHeiko Schocher <hs@denx.de>
      Acked-by: 's avatarStefan Roese <sr@denx.de>
      Acked-by: 's avatarPrzemyslaw Marczak <p.marczak@samsung.com>
      72a8cf8d
  13. 14 Jan, 2016 1 commit
  14. 20 Nov, 2015 1 commit
    • Simon Glass's avatar
      console: Add a console buffer · 9854a874
      Simon Glass authored
      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: 's avatarSimon Glass <sjg@chromium.org>
      9854a874
  15. 18 Nov, 2015 1 commit
  16. 13 Nov, 2015 1 commit
  17. 22 Oct, 2015 1 commit
    • Nishanth Menon's avatar
      drivers: Introduce a simplified remoteproc framework · ddf56bc7
      Nishanth Menon authored
      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: 's avatarSimon Glass <sjg@chromium.org>
      Signed-off-by: 's avatarNishanth Menon <nm@ti.com>
      Acked-by: 's avatarSimon Glass <sjg@chromium.org>
      ddf56bc7
  18. 21 Oct, 2015 1 commit
  19. 31 Aug, 2015 2 commits
  20. 13 Aug, 2015 1 commit
    • Nikita Kiryanov's avatar
      kconfig: add config option for shell prompt · 181bd9dc
      Nikita Kiryanov authored
      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: 's avatarNikita Kiryanov <nikita@compulab.co.il>
      [trini: Add spring, sniper, smartweb to conversion]
      Signed-off-by: 's avatarTom Rini <trini@konsulko.com>
      181bd9dc
  21. 01 Jul, 2015 1 commit
  22. 26 Jun, 2015 1 commit
  23. 25 Jun, 2015 2 commits
  24. 08 Jun, 2015 2 commits
  25. 01 Jun, 2015 2 commits
  26. 15 May, 2015 2 commits
    • Przemyslaw Marczak's avatar
      dm: regulator: add regulator command · 6262b72b
      Przemyslaw Marczak authored
      This command is based on driver model regulator's API.
      The user interface provides:
      - list UCLASS regulator devices
      - show or [set] operating regulator device
      - print constraints info
      - print operating status
      - print/[set] voltage value [uV] (force)
      - print/[set] current value [uA]
      - print/[set] operating mode id
      - enable the regulator output
      - disable the regulator output
      
      The 'force' option can be used for setting the value which exceeds
      the constraints min/max limits.
      Signed-off-by: 's avatarPrzemyslaw Marczak <p.marczak@samsung.com>
      Acked-by: 's avatarSimon Glass <sjg@chromium.org>
      6262b72b
    • Przemyslaw Marczak's avatar
      dm: pmic: add pmic command · d89fdcf9
      Przemyslaw Marczak authored
      This is new command for the PMIC devices based on driver model PMIC API.
      Command features are unchanged:
      - list UCLASS pmic devices
      - show or [set] operating pmic device (NEW)
      - dump registers
      - read byte of register at address
      - write byte to register at address
      
      The only one change for this command is 'dev' subcommand.
      Signed-off-by: 's avatarPrzemyslaw Marczak <p.marczak@samsung.com>
      Acked-by: 's avatarSimon Glass <sjg@chromium.org>
      d89fdcf9
  27. 30 Apr, 2015 1 commit
  28. 21 Apr, 2015 1 commit
  29. 18 Apr, 2015 2 commits
  30. 10 Apr, 2015 1 commit
    • Linus Walleij's avatar
      common/armflash: Support for ARM flash images · 4bb66506
      Linus Walleij authored
      The ARM reference designs all use a special flash image format
      that stores a footer (two versions exist) at the end of the last
      erase block of the image in flash memory.
      
      Version one of the footer is indicated by the magic number
      0xA0FFFF9F at 12 bytes before the end of the flash block and
      version two is indicated by the magic number 0x464F4F54 0x464C5348
      (ASCII for "FLSHFOOT") in the very last 8 bytes of the erase block.
      
      This command driver implements support for both versions of the
      AFS images (the name comes from the Linux driver in drivers/mtd/afs.c)
      and makes it possible to list images and load an image by name into
      the memory with these commands:
      
      afs - lists flash contents
      afs load <image> - loads image to address indicated in the image
      afs load <image> <addres> - loads image to a specified address
      
      This image scheme is used on the ARM Integrator family, ARM
      Versatile family, ARM RealView family (not yet supported in U-Boot)
      and ARM Versatile Express family up to and including the new
      Juno board for 64 bit development.
      Reviewed-by: 's avatarTom Rini <trini@konsulko.com>
      Signed-off-by: 's avatarLinus Walleij <linus.walleij@linaro.org>
      4bb66506
  31. 05 Mar, 2015 1 commit
  32. 24 Feb, 2015 1 commit