10 Nov, 2019

1 commit

  • Since we move the ATF bl31 entry for 64bit CPUs to 0x40000, we need to
    limit the SPL size in 0x40000(start from 0) so that we don't need to do
    the relocate for ATF loading.
    Note that there will be separate BSS, STACK and MALLOC heap, so the size
    0x40000(256KB) should be enough for SPL text.

    Signed-off-by: Kever Yang

    Kever Yang
     

23 Aug, 2019

1 commit


26 Jul, 2019

2 commits


20 Jul, 2019

1 commit


08 May, 2019

1 commit


01 May, 2019

1 commit


30 Apr, 2019

1 commit


19 Jan, 2019

1 commit

  • 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: Tom Rini
    Signed-off-by: Philipp Tomsich
    Reviewed-by: Otavio Salvador [dw_mmc portion]
    Reviewed-by: Fabio Estevam [mxsmmc portion]
    Reviewed-by: Simon Glass [tegra portion]

    Philipp Tomsich
     

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
     

07 May, 2018

1 commit

  • When U-Boot started using SPDX tags we were among the early adopters and
    there weren't a lot of other examples to borrow from. So we picked the
    area of the file that usually had a full license text and replaced it
    with an appropriate SPDX-License-Identifier: entry. Since then, the
    Linux Kernel has adopted SPDX tags and they place it as the very first
    line in a file (except where shebangs are used, then it's second line)
    and with slightly different comment styles than us.

    In part due to community overlap, in part due to better tag visibility
    and in part for other minor reasons, switch over to that style.

    This commit changes all instances where we have a single declared
    license in the tag as both the before and after are identical in tag
    contents. There's also a few places where I found we did not have a tag
    and have introduced one.

    Signed-off-by: Tom Rini

    Tom Rini
     

15 Feb, 2018

1 commit

  • Migrate the option CONFIG_SPL_FRAMEWORK and make this gate most of the
    current set of options we have in Kconfig. We will need to have some
    options available for SPL and !SPL_FRAMEWORK so this is important. In a
    few cases we re-order existing options so that we have less escapes from
    the SPL_FRAMEWORK guard.

    Signed-off-by: Tom Rini

    Tom Rini
     

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
     

01 Nov, 2017

1 commit


19 Sep, 2017

1 commit


04 Sep, 2017

1 commit


13 Aug, 2017

5 commits

  • We can finally drop TPL_STACK, TPL_TEXT_BASE and TPL_MAX_SIZE off the
    whitelist (this time it's really happening!) and migrate the setting
    (only used on the RK3368-uQ7 so far) into Kconfig.

    Signed-off-by: Philipp Tomsich
    Reviewed-by: Simon Glass

    Philipp Tomsich
     
  • Set TPL_LDSCRIPT in Kconfig, so we don't have to pollute our
    header file.

    Signed-off-by: Philipp Tomsich

    Philipp Tomsich
     
  • To build TPL and SPL stages for the RK3368, we will also need to
    enable the SPL_FRAMEWORK.

    Signed-off-by: Philipp Tomsich
    Reviewed-by: Simon Glass

    Philipp Tomsich
     
  • For the RK3368, we use a multi-stage boot-process consisting of the
    following:
    1. TPL: initalises DRAM, returns to boot-ROM (which then loads
    the next stage and transfers control to it)
    2. SPL: a full-features SPL stage including OF_CONTROL and FIT
    image loading, which fetches the ATF, DTB and full U-Boot
    and then transfers control to the ATF (using the BL31
    parameter block to indicate the location of BL33/U-Boot)
    3. ATF: sets up the secure world and exits to BL33 (i.e. a full
    U-Boot) in the normal world
    4. full U-Boot

    TPL/SPL and the full U-Boot are built from this tree and need to
    run from distinct text addresses and with distinct initial stack
    pointer addresses.

    This commit sets up the configuration to run:
    - TPL from the SRAM at 0xff8c0000 (note that the first 0x1000
    are reserved for use by the boot-ROM and contain the SP
    when the TPL is entered)
    - SPL from DRAM at 0x0
    - U-Boot from DRAM at 0x200000

    Signed-off-by: Philipp Tomsich
    Reviewed-by: Simon Glass

    Philipp Tomsich
     
  • The BootROM of the RK3368 Boot ROM does not initialise cntfrq_el0.
    This change defines COUNTER_FREQUENCY, which is used by the AArch64 init
    code in arch/arm/cpu/armv8/start.S to set up cntfrq_el0.

    If the counter-frequency is not correctly set up, the calculation of
    delays using the ARMv8 generic timer can not work correctly.

    Signed-off-by: Philipp Tomsich
    Reviewed-by: Simon Glass

    Philipp Tomsich
     

11 Jul, 2017

1 commit

  • There are some functions like sdram_size_mb can be re-used for
    different rockchip SoCs, just put them into common file.
    Add board_get_usable_ram_top() for ram_top init base on
    SDRAM_MAX_SIZE.

    Signed-off-by: Kever Yang
    Reviewed-by: Philipp Tomsich
    Added SDRAM_MAX_SIZE definition for RK3036:
    Signed-off-by: Philipp Tomsich

    fixup: 3036 fix for sdram_common

    Kever Yang
     

07 Jun, 2017

1 commit