1. 30 4月, 2019 1 次提交
  2. 19 1月, 2019 1 次提交
    • P
      Kconfig: Migrate BOUNCE_BUFFER · 2acc24fc
      Philipp Tomsich 提交于
      The bounce buffer is used by a few drivers (most of the MMC drivers)
      to overcome limitations in their respective DMA implementation.
      
      This moves the configuration to Kconfig and makes it user-selectable
      (even though it will be a required feature to make those drivers
      work): the expected usage is for drivers depending on this to 'select'
      it unconditionally from their respective Kconfig (see follow-up
      patches).
      
      This commit includes a full migration using moveconfig.py to ensure
      that each commit compiles.  To ensure bisectability we update
      dependencies of various drivers to now select BOUNCE_BUFFER when needed.
      
      [trini: Squash all patches to ensure bisectability]
      Signed-off-by: NTom Rini <trini@konsulko.com>
      Signed-off-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
      Reviewed-by: Otavio Salvador <otavio@ossystems.com.br> [dw_mmc portion]
      Reviewed-by: Fabio Estevam <festevam@gmail.com> [mxsmmc portion]
      Reviewed-by: Simon Glass <sjg@chromium.org> [tegra portion]
      2acc24fc
  3. 22 10月, 2018 1 次提交
  4. 17 8月, 2018 1 次提交
    • T
      configs: Migrate CONFIG_NR_DRAM_BANKS · 86cf1c82
      Tom Rini 提交于
      We have the following cases:
      - CONFIG_NR_DRAM_BANKS was defined, migrate normally
      - CONFIG_NR_DRAM_BANKS_MAX was defined and then used for
        CONFIG_NR_DRAM_BANKS after a check, just migrate it over now.
      - CONFIG_NR_DRAM_BANKS was very oddly defined on p2771-0000-* (to 1024 +
        2), set this to 8.
      Signed-off-by: NTom Rini <trini@konsulko.com>
      86cf1c82
  5. 09 4月, 2018 1 次提交
  6. 28 2月, 2018 1 次提交
  7. 24 2月, 2018 1 次提交
  8. 11 2月, 2018 1 次提交
    • T
      configs: Migrate CONFIG_SYS_TEXT_BASE · 278b90ce
      Tom Rini 提交于
      On the NIOS2 and Xtensa architectures, we do not have
      CONFIG_SYS_TEXT_BASE set.  This is a strict migration of the current
      values into the defconfig and removing them from the headers.
      
      I did not attempt to add more default values in and for now will leave
      that to maintainers.
      Signed-off-by: NTom Rini <trini@konsulko.com>
      278b90ce
  9. 29 12月, 2017 1 次提交
  10. 11 10月, 2017 1 次提交
    • T
      cmd: Toggle the default value of CONFIG_CMD_IMLS · ad12dc18
      Tuomas Tynkkynen 提交于
      Having this as a 'default y' is rather annoying because it doesn't
      actually compile unless other options are defined in the board header:
      
      ../cmd/bootm.c: In function 'do_imls_nor':
      ../cmd/bootm.c:330:7: error: 'CONFIG_SYS_MAX_FLASH_BANKS' undeclared (first use in this function); did you mean 'CONFIG_SYS_MAX_FLASH_SECT'?
         i < CONFIG_SYS_MAX_FLASH_BANKS; ++i, ++info) {
      
      Make it 'default n' so people who develop new boards that start from a
      blank defconfig have one less compilation failure to debug.
      Signed-off-by: NTuomas Tynkkynen <tuomas.tynkkynen@iki.fi>
      ad12dc18
  11. 04 10月, 2017 1 次提交
  12. 28 8月, 2017 1 次提交
  13. 15 8月, 2017 1 次提交
  14. 26 7月, 2017 1 次提交
    • S
      Convert CONFIG_ENV_IS_IN_MMC/NAND/UBI and NOWHERE to Kconfig · 2be29653
      Simon Glass 提交于
      This converts the following to Kconfig:
         CONFIG_ENV_IS_IN_MMC
         CONFIG_ENV_IS_IN_NAND
         CONFIG_ENV_IS_IN_UBI
         CONFIG_ENV_IS_NOWHERE
      
      In fact this already exists for sunxi as a 'choice' config. However not
      all the choices are available in Kconfig yet so we cannot use that. It
      would lead to more than one option being set.
      
      In addition, one purpose of this series is to allow the environment to be
      stored in more than one place. So the existing choice is converted to a
      normal config allowing each option to be set independently.
      
      There are not many opportunities for Kconfig updates to reduce the size of
      this patch. This was tested with
      
         ./tools/moveconfig.py -i CONFIG_ENV_IS_IN_MMC
      
      And then manual updates.  This is because for CHAIN_OF_TRUST boards they
      can only have ENV_IS_NOWHERE set, so we enforce that via Kconfig logic
      now.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      Signed-off-by: NTom Rini <trini@konsulko.com>
      2be29653
  15. 12 7月, 2017 1 次提交
  16. 30 4月, 2017 1 次提交
  17. 26 1月, 2017 1 次提交
  18. 24 1月, 2017 1 次提交
  19. 22 1月, 2017 1 次提交
  20. 27 9月, 2016 1 次提交
    • T
      dfu: Migrate to Kconfig · 6828e602
      Tom Rini 提交于
      Introduce a hidden USB_FUNCTION_DFU Kconfig option and select it for
      CMD_DFU (as we must have the DFU command enabled to do anything DFU).
      Make all of the entries in drivers/dfu/Kconfig depend on CMD_DFU and add
      options for all of the back end choices that DFU can make use of.
      
      Cc: Lukasz Majewski <l.majewski@samsung.com>
      Signed-off-by: NTom Rini <trini@konsulko.com>
      Acked-by: NLukasz Majewski <l.majewski@samsung.com>
      6828e602
  21. 10 9月, 2016 1 次提交
  22. 07 9月, 2016 1 次提交
    • F
      warp: Fix RAM size runtime detection · 693779e3
      Fabio Estevam 提交于
      Since commit a13d3757 ("warp: Use imx_ddr_size() for calculating the
      DDR size") warp board no longer boots.
      
      The reason for the breakage is that the warp board is using the DDR
      configuration from mx6slevk. A fundamental difference between warp and
      mx6slevk is that warp only uses one DDR chip select while mx6slevk uses two.
      
      The imx_ddr() function calculates the RAM size in runtime by reading the
      values of registers MDCTL and MDMISC.
      
      So in order to fix this warp boot issue, create a imximage DDR file specific
      to warp, where the MDCTL register is configured to only activates a single
      chip select.
      Reported-by: NBreno Lima <breno.lima@nxp.com>
      Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
      Tested-by: NBreno Lima <breno.lima@nxp.com>
      693779e3
  23. 17 6月, 2016 1 次提交
  24. 26 4月, 2016 3 次提交
  25. 20 4月, 2016 3 次提交
  26. 26 3月, 2016 1 次提交
  27. 15 3月, 2016 1 次提交
  28. 19 11月, 2015 1 次提交
  29. 02 9月, 2015 1 次提交
    • P
      imx: mx6 move TARGET_xx Kconfig option to mx6 specific Kconfig file · 21782828
      Peng Fan 提交于
      Move TARGET_xx Kconfig option based on mx6 to arch/arm/cpu/armv7/mx6/Kconfig.
      Add enable "CONFIG_ARCH_MX6" for boards based on mx6.
      Then we can choose target boards using "make ARCH=arm menuconfig"
      with ARCH_MX6 defined.
      
      If using original way, we have no chance to enable ARCH_MX6 when
      "make menuconfig". Even define CONFIG_ARCH_MX6=y in xx_defconfig,
      kconfig will complains "arch/../configs/platinum_titanium_defconfig:3:
      warning: override: TARGET_PLATINUM_TITANIUM changes choice state"
      Signed-off-by: NPeng Fan <Peng.Fan@freescale.com>
      Cc: Stefano Babic <sbabic@denx.de>
      Cc: Heiko Schocher <hs@denx.de>
      Cc: Tim Harvey <tharvey@gateworks.com>
      Cc: Eric Bénard <eric@eukrea.com>
      Cc: Fabio Estevam <fabio.estevam@freescale.com>
      Cc: Eric Nelson <eric.nelson@boundarydevices.com>
      Cc: Marek Vasut <marex@denx.de>
      Cc: Christian Gmeiner <christian.gmeiner@gmail.com>
      Cc: Stefan Roese <sr@denx.de>
      Cc: Soeren Moch <smoch@web.de>
      Cc: Otavio Salvador <otavio@ossystems.com.br>
      Acked-by: NStefano Babic <sbabic@denx.de>
      Acked-by: NSoeren Moch <smoch@web.de>
      Acked-by: NOtavio Salvador <otavio@ossystems.com.br>
      Acked-by: NChristian Gmeiner <christian.gmeiner@gmail.com>
      21782828
  30. 26 6月, 2015 1 次提交
  31. 13 5月, 2015 1 次提交
  32. 23 2月, 2015 1 次提交
  33. 30 7月, 2014 1 次提交
    • M
      kconfig: add board Kconfig and defconfig files · dd84058d
      Masahiro Yamada 提交于
      This commit adds:
       - arch/${ARCH}/Kconfig
          provide a menu to select target boards
       - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
          set CONFIG macros to the appropriate values for each board
       - configs/${TARGET_BOARD}_defconfig
          default setting of each board
      
      (This commit was automatically generated by a conversion script
      based on boards.cfg)
      
      In Linux Kernel, defconfig files are located under
      arch/${ARCH}/configs/ directory.
      It works in Linux Kernel since ARCH is always given from the
      command line for cross compile.
      
      But in U-Boot, ARCH is not given from the command line.
      Which means we cannot know ARCH until the board configuration is done.
      That is why all the "*_defconfig" files should be gathered into a
      single directory ./configs/.
      Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>
      Acked-by: NSimon Glass <sjg@chromium.org>
      dd84058d