20 Feb, 2020

1 commit


30 Jan, 2020

2 commits


23 Jan, 2020

1 commit


21 Nov, 2019

2 commits

  • - In ARMv8 NXP Layerscape platforms we also need to make use of
    CONFIG_SYS_RELOC_GD_ENV_ADDR now, do so.
    - On ENV_IS_IN_REMOTE, CONFIG_ENV_OFFSET is never used, drop the define
    to 0.
    - Add Kconfig entry for ENV_ADDR.
    - Make ENV_ADDR / ENV_OFFSET depend on the env locations that use it.
    - Add ENV_xxx_REDUND options that depend on their primary option and
    SYS_REDUNDAND_ENVIRONMENT
    - On a number of PowerPC platforms, use SPL_ENV_ADDR not CONFIG_ENV_ADDR
    for the pre-main-U-Boot environment location.
    - On ENV_IS_IN_SPI_FLASH, check not for CONFIG_ENV_ADDR being set but
    rather it being non-zero, as it will now be zero by default.
    - Rework the env_offset absolute in env/embedded.o to not use
    CONFIG_ENV_OFFSET as it was the only use of ENV_OFFSET within
    ENV_IS_IN_FLASH.
    - Migrate all platforms.

    Cc: Wolfgang Denk
    Cc: Joe Hershberger
    Cc: Patrick Delaunay
    Cc: uboot-stm32@st-md-mailman.stormreply.com
    Signed-off-by: Tom Rini
    Acked-by: Joe Hershberger
    Reviewed-by: Simon Goldschmidt

    Tom Rini
     
  • Today in initr_reloc_global_data() we use some non-obvious tests to
    determine if we need to relocate the env_addr within gd or not. In
    order to facilitate migration of other symbols to Kconfig we need to
    introduce a new symbol for this particular use case.

    Cc: Wolfgang Denk
    Cc: Joe Hershberger
    Signed-off-by: Tom Rini

    Tom Rini
     

12 Nov, 2019

1 commit


10 Nov, 2019

2 commits

  • 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

    Kever Yang
     
  • 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

    Kever Yang
     

08 Nov, 2019

1 commit


23 Aug, 2019

1 commit


14 Aug, 2019

1 commit


20 Jul, 2019

2 commits


08 May, 2019

3 commits

  • Few SPL and U-Boot proper configs are common to all rk3399 target
    defconfigs, move them and select it from platform kconfig.

    Moved configs:
    - SPL_ATF
    - SPL_ATF_NO_PLATFORM_PARAM if SPL_ATF
    - SPL_LOAD_FIT
    - SPL_CLK if SPL
    - SPL_PINCTRL if SPL
    - SPL_RAM if SPL
    - SPL_REGMAP if SPL
    - SPL_SYSCON if SPL
    - CLK
    - FIT
    - PINCTRL
    - RAM
    - REGMAP
    - SYSCON
    - DM_PMIC
    - DM_REGULATOR_FIXED

    Signed-off-by: Jagan Teki
    Reviewed-by: Kever Yang

    Jagan Teki
     
  • Add default SPL_FIT_GENERATOR py script for rockchip platforms if
    specific target enabled SPL_LOAD_FIT.

    So, this would help get rid of explicitly mentioning the default
    SPL FIT generator in defconfigs. however some targets, like puma_rk3399
    still require their own FIT generator so in those cases the default will
    override with defconfig defined generator.

    Reviewed-by: Paul Kocialkowski
    Signed-off-by: Jagan Teki
    Reviewed-by: Kever Yang

    Jagan Teki
     
  • The SPL is now running at SDRAM, and 0x10000 is used by BL31,
    and the ARM SPL do not support relocate now, we need reserved
    0x50000 so that it won't overwrite the code when we load the
    bl31 to target space.
    We should remove this after we enable the relocate feature.

    The SPL need malloc 0x9000 for MMC as buffer used for transfer
    data to IRAM(The EMMC DMA can not transfer data to IRAM directly).

    Signed-off-by: Kever Yang

    Kever Yang
     

30 Apr, 2019

2 commits


26 Mar, 2019

1 commit

  • This converts the following to Kconfig:
    CONFIG_SF_DEFAULT_BUS
    CONFIG_SF_DEFAULT_CS
    CONFIG_SF_DEFAULT_MODE
    CONFIG_SF_DEFAULT_SPEED

    I use moveconfig script and then manual check on generated u-boot.cfg
    to solve the remaining issue.

    Signed-off-by: Patrick Delaunay

    Patrick Delaunay
     

01 Feb, 2019

1 commit


08 Jan, 2019

1 commit


04 Sep, 2018

1 commit


17 Aug, 2018

1 commit

  • 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

    Tom Rini
     

21 Jul, 2018

1 commit

  • Currently the fdtfile environment variable is set to
    CONFIG_DEFAULT_DEVICE_TREE which is іnternally used as U-Boot devicetree
    source. The OS can use a different filename and Kconfig gives us the
    ability to select a default devicetree via CONFIG_DEFAULT_FDT_FILE.
    This also gives user configuring U-Boot via menuconfig the behaviour
    someone would expect.

    Signed-off-by: Klaus Goger
    Tested-By: Vagrant Cascadian
    Reviewed-by: Philipp Tomsich
    Acked-by: Philipp Tomsich

    Klaus Goger
     

04 Jun, 2018

1 commit


26 Apr, 2018

1 commit


09 Apr, 2018

1 commit


11 Feb, 2018

1 commit

  • 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

    Tom Rini
     

03 Jan, 2018

1 commit

  • The Rockchip-released ATF for the Firefly apparently (i.e. Kever
    reported this) does not tolerate a FDT being passed as the platform
    parameter and will run into a hard stop.

    To work around this limitation in the ATF parameter handling, we
    enable SPL_ATF_NO_PLATFORM_PARAM (which will force passing NULL for
    the platform parameters).

    Note that this only affects this platform, as the ATF releases for the
    RK3368 and RK3399 have always either ignored the platform parameter
    (i.e. before the FDT-based parameters were supported) or support
    receiving a pointer to a FDT.

    Signed-off-by: Philipp Tomsich
    Reviewed-by: Kever Yang

    Philipp Tomsich
     

19 Dec, 2017

1 commit

  • Enable SPL_FIT_GENERATOR with path for it.
    With this patch you can get u-boot.itb for rk3399-firefly with:
    > make u-boot.itb

    Signed-off-by: Kever Yang
    Reviewed-by: Mark Kettenis
    Tested-by: Mark Kettenis
    Acked-by: Philipp Tomsich
    Reviewed-by: Philipp Tomsich

    Kever Yang
     

18 Dec, 2017

1 commit


26 Nov, 2017

1 commit


07 Nov, 2017

1 commit


11 Oct, 2017

1 commit

  • 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: Tuomas Tynkkynen

    Tuomas Tynkkynen
     

08 Sep, 2017

2 commits


05 Sep, 2017

1 commit


28 Aug, 2017

1 commit


26 Jul, 2017

1 commit

  • 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
    Signed-off-by: Tom Rini

    Simon Glass