1. 23 6月, 2019 1 次提交
  2. 21 6月, 2019 1 次提交
  3. 15 6月, 2019 2 次提交
  4. 11 6月, 2019 1 次提交
  5. 30 4月, 2019 1 次提交
  6. 25 4月, 2019 5 次提交
  7. 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
  8. 08 1月, 2019 1 次提交
  9. 14 11月, 2018 1 次提交
  10. 04 9月, 2018 1 次提交
  11. 18 8月, 2018 1 次提交
  12. 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
  13. 23 7月, 2018 1 次提交
  14. 09 4月, 2018 3 次提交
  15. 24 2月, 2018 1 次提交
  16. 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
  17. 08 2月, 2018 1 次提交
  18. 06 2月, 2018 1 次提交
    • T
      cmd: Make CONFIG_CMD_FPGA depend on CONFIG_FPGA · a4fa8114
      Tuomas Tynkkynen 提交于
      cmd/Makefile has:
      
      ifdef CONFIG_FPGA
      obj-$(CONFIG_CMD_FPGA) += fpga.o
      endif
      
      which means that if CONFIG_FPGA is not set, CONFIG_CMD_FPGA silently
      does nothing. Let's remove that Makefile conditional and instead express
      this equivalent dependency in Kconfig, so a lot of redundant
      
       # CONFIG_CMD_FPGA is not set
      
      can be removed from board defconfigs that don't actually have an FPGA.
      Signed-off-by: NTuomas Tynkkynen <tuomas@tuxera.com>
      a4fa8114
  19. 06 11月, 2017 1 次提交
  20. 31 10月, 2017 1 次提交
  21. 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
  22. 04 10月, 2017 1 次提交
  23. 28 8月, 2017 1 次提交
  24. 15 8月, 2017 1 次提交
  25. 08 8月, 2017 2 次提交
  26. 01 8月, 2017 1 次提交
  27. 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
  28. 19 6月, 2017 1 次提交
  29. 30 4月, 2017 1 次提交
  30. 20 3月, 2017 3 次提交