1. 10 Nov, 2019 2 commits
    • Kever Yang's avatar
      rockchip: rk3399: update SPL_STACK_R_ADDR · 006ab58d
      Kever Yang authored
      Use the same SPL_STACK_R_ADDR in Kconfig instead of each board config;
      default to 0x4000000(64MB) instead of 0x80000(512KB) for this address
      can support all the SoCs including those may have only 64MB memory, and
      also reserve enough space for atf, kernel(in falcon mode) loading.
      
      After the ATF entry move to 0x40000, the stack from 0x80000 may be override
      when loading ATF bl31.
      Signed-off-by: Kever Yang's avatarKever Yang <kever.yang@rock-chips.com>
      006ab58d
    • Kever Yang's avatar
      rockchip: rk3399: defconfig: no need to reserve IRAM for SPL · 5ce94c74
      Kever Yang authored
      We use to reserve IRAM to avoid the SPL text overlap with ATF M0 code,
      and when we introduce the TPL, the SPL space is in DRAM, we reserve
      space to avoid SPL text overlap with ATF bl31.
      
      Now we decide to move ATF entry point to 0x40000 instead of 0x1000,
      so that the SPL can have 0x4000 as code size and no need to reserve
      space or relocate before loading ATF.
      
      The mainline ATF has update since:
      0aad563c rockchip: Update BL31_BASE to 0x40000
      Signed-off-by: Kever Yang's avatarKever Yang <kever.yang@rock-chips.com>
      5ce94c74
  2. 07 Nov, 2019 1 commit
  3. 23 Aug, 2019 1 commit
  4. 14 Aug, 2019 1 commit
  5. 20 Jul, 2019 2 commits
  6. 08 May, 2019 3 commits
  7. 30 Apr, 2019 2 commits
  8. 25 Mar, 2019 1 commit
  9. 01 Feb, 2019 2 commits
  10. 07 Jan, 2019 1 commit
  11. 03 Sep, 2018 1 commit
  12. 16 Aug, 2018 1 commit
    • Tom Rini's avatar
      configs: Migrate CONFIG_NR_DRAM_BANKS · 86cf1c82
      Tom Rini authored
      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: Tom Rini's avatarTom Rini <trini@konsulko.com>
      86cf1c82
  13. 20 Jul, 2018 1 commit
  14. 04 Jun, 2018 1 commit
  15. 28 Apr, 2018 1 commit
  16. 25 Apr, 2018 2 commits
  17. 08 Apr, 2018 1 commit
  18. 11 Feb, 2018 1 commit
    • Tom Rini's avatar
      configs: Migrate CONFIG_SYS_TEXT_BASE · 278b90ce
      Tom Rini authored
      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: Tom Rini's avatarTom Rini <trini@konsulko.com>
      278b90ce
  19. 18 Dec, 2017 1 commit
  20. 07 Nov, 2017 1 commit
  21. 10 Oct, 2017 1 commit
    • Tuomas Tynkkynen's avatar
      cmd: Toggle the default value of CONFIG_CMD_IMLS · ad12dc18
      Tuomas Tynkkynen authored
      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: default avatarTuomas Tynkkynen <tuomas.tynkkynen@iki.fi>
      ad12dc18
  22. 08 Sep, 2017 2 commits
  23. 28 Aug, 2017 1 commit
  24. 07 Aug, 2017 1 commit
  25. 26 Jul, 2017 1 commit
    • Simon Glass's avatar
      Convert CONFIG_ENV_IS_IN_MMC/NAND/UBI and NOWHERE to Kconfig · 2be29653
      Simon Glass authored
      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: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      2be29653
  26. 19 Jun, 2017 1 commit
  27. 10 May, 2017 3 commits
  28. 01 May, 2017 1 commit
  29. 27 Apr, 2017 1 commit
  30. 15 Apr, 2017 1 commit