1. 26 8月, 2019 1 次提交
  2. 20 8月, 2019 1 次提交
    • S
      arm: omap2: am43xx: Enable CONFIG_BLK · e171dc29
      Suniel Mahesh 提交于
      With DM_MMC enabled, enable CONFIG_BLK to remove this
      compile warning for am43xx based targets:
      
      ===================== WARNING ======================
      This board does not use CONFIG_DM_MMC. Please update
      the board to use CONFIG_DM_MMC before the v2019.04 release.
      Failure to update by the deadline may result in board removal.
      See doc/driver-model/MIGRATION.txt for more info.
      ====================================================
      
      Targets were compile tested, build was clean.
      Signed-off-by: NSuniel Mahesh <sunil.m@techveda.org>
      e171dc29
  3. 09 7月, 2019 1 次提交
    • M
      at91, omap2plus: configs: migrate CONFIG_ENV_ to defconfigs · a9221f3e
      Markus Klotzbuecher 提交于
      Enable the extended ENV options for AT91 and OMAP2PLUS in order to be
      able to use CONFIG_ENV_UBI_* on these architectures.
      
      As this change also makes the configs ENV_SIZE, ENV_SECT_SIZE,
      ENV_OFFSET visible to AT91 and OMAP2PLUS, migrate users of these to
      KConfig.
      
      This migration was run using an extended moveconfig.py which evaluates
      expressions such as "(512 << 10)". See patch ("moveconfig: expand
      simple expressions").
      
      All modified boards were built with SOURCE_DATE_EPOCH=0 before and
      after the change and successfully confirmed that the identical binary
      is generated (the only exception was igep00x0, which does not define
      CONFIG_ENV_IS_IN_UBI in the original board header. Once that is
      defined, the test passes too).
      
      hs: rebased patch to:
        68b90e57: "configs: tinker-rk3288 disable CONFIG_SPL_I2C_SUPPORT"
      Signed-off-by: NMarkus Klotzbuecher <markus.klotzbuecher@kistler.com>
      Cc: Heiko Schocher <hs@denx.de>
      Cc: Eugen Hristev <eugen.hristev@microchip.com>
      Cc: Tom Rini <trini@konsulko.com>
      a9221f3e
  4. 26 3月, 2019 1 次提交
  5. 08 1月, 2019 1 次提交
  6. 14 11月, 2018 1 次提交
  7. 04 9月, 2018 1 次提交
  8. 18 8月, 2018 2 次提交
  9. 28 4月, 2018 1 次提交
    • A
      Convert CONFIG_SPI to Kconfig · f1b1f770
      Adam Ford 提交于
      This converts the following to Kconfig:
         CONFIG_SPI
      
      This partly involves updating code that assumes that CONFIG_SPI implies
      things that are specific to the MPC8xx SPI driver.  For now, just update
      the CONFIG tests.  This also involves reworking the default for
      CONFIG_SYS_DEF_EEPROM_ADDR so that we don't set it when we cannot make a
      reasonable default, as it does not cause any compile failures.
      Signed-off-by: NAdam Ford <aford173@gmail.com>
      Signed-off-by: NTom Rini <trini@konsulko.com>
      f1b1f770
  10. 14 4月, 2018 1 次提交
    • T
      configs: Fixup some CPSW-related items · d291d823
      Tom Rini 提交于
      - For am335x_pdu001 we do not want the CPSW driver, drop it
      - Re-sync the defconfig for am43xx_evm_rtconly as it came in after the
        patch that converted CPSW to Kconfig was posted but before it was
        applied.
      - Drop empty section / comments from pengwyn
      - Drop empty section / comments from baltos and drop unused
        CONFIG_SPL_NET_VCI_STRING (it does not enable CONFIG_SPL_NET_SUPPORT
        currently and SPL_NET_VCI_STRING has been migrated already).
      
      Cc: Felix Brack <fb@ltec.ch>
      Cc: Lokesh Vutla <lokeshvutla@ti.com>
      Cc: Yegor Yefremov <yegorslists@googlemail.com>
      Cc: Lothar Felten <lothar.felten@gmail.com>
      Fixes: f02b8d17 ("Migrate CONFIG_DRIVER_TI_CPSW to Kconfig")
      Signed-off-by: NTom Rini <trini@konsulko.com>
      Reviewed-by: NFelix Brack <fb@ltec.ch>
      Tested-by: NFelix Brack <fb@ltec.ch>
      d291d823
  11. 09 4月, 2018 1 次提交
  12. 08 4月, 2018 1 次提交
  13. 07 4月, 2018 1 次提交
    • T
      ARM: AM43xx: Add support for RTC only + DDR in self-refresh mode · 7619badb
      Tero Kristo 提交于
      Kernel stores information to the RTC_SCRATCH0 and RTC_SCRATCH1 registers
      for wakeup from RTC-only mode with DDR in self-refresh. Parse these
      registers during SPL boot and jump to the kernel resume vector if the
      device is waking up from RTC-only modewith DDR in Self-refresh.
      
      The RTC scratch register layout used is:
      
      SCRATCH0 : bits00-31 : kernel resume address
      SCRATCH1 : bits00-15 : RTC magic value used to detect valid config
      SCRATCH1 : bits16-31 : board type information populated by bootloader
      
      During the normal boot path the SCRATCH1 : bits16-31 are updated with
      the eeprom read board type data. In the rtc_only boot path the rtc
      scratchpad register is read and the board type is determined and
      correspondingly ddr dpll parameters are set. This is done so as to avoid
      costly i2c read to eeprom.
      
      RTC-only +DRR in self-refresh mode support is currently only enabled for
      am43xx_evm_rtconly_config.
      This is not to be used with epos evm builds.
      Signed-off-by: NTero Kristo <t-kristo@ti.com>
      [j-keerthy@ti.com Rebased to latest u-boot master branch]
      Signed-off-by: NKeerthy <j-keerthy@ti.com>
      Reviewed-by: NTom Rini <trini@konsulko.com>
      7619badb
  14. 23 2月, 2018 1 次提交
  15. 23 1月, 2018 1 次提交
  16. 06 11月, 2017 1 次提交
  17. 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
  18. 04 10月, 2017 1 次提交
  19. 30 9月, 2017 1 次提交
  20. 12 8月, 2017 4 次提交
  21. 09 8月, 2017 1 次提交
  22. 08 8月, 2017 1 次提交
  23. 01 8月, 2017 2 次提交
  24. 26 7月, 2017 1 次提交
  25. 25 7月, 2017 1 次提交
  26. 19 6月, 2017 1 次提交
  27. 09 5月, 2017 1 次提交
  28. 28 4月, 2017 2 次提交
  29. 21 3月, 2017 1 次提交
  30. 14 3月, 2017 1 次提交
  31. 28 1月, 2017 3 次提交
  32. 24 1月, 2017 1 次提交