20 Jul, 2018

1 commit


17 Jul, 2018

1 commit


23 May, 2018

2 commits


27 Apr, 2018

2 commits


23 Feb, 2018

1 commit

  • TI_SECURE_DEVICE is used by both OMAP2+ and Keystone2 family devices,
    and so when ARCH_OMAP2PLUS was used to gate off the OMAP2+ Kconfig
    Keystone2 family devices lost this config option.

    Move this option out of mach-omap2 Kconfig to a spot accessible by both
    families. We picked arch/arm/Kconfig over the TI specific board/ti/
    location as this option is not specific to our boards but rather our
    architecture.

    Plus at some point this option can be changed to just
    SECURE_DEVICE, as having secure parts is not exclusive to TI and
    so other vendors can interpret this option as needed by their device
    configurations.

    Fixes: a93fbf4a7892 ("ARM: omap2+: rename config to ARCH_OMAP2PLUS and consolidate Kconfig")
    Signed-off-by: Andrew F. Davis
    Reviewed-by: Lokesh Vutla

    Andrew F. Davis
     

15 Feb, 2018

2 commits

  • Kconfig should only 'select' features that are required for an arch.
    Standard features that can be disabled without breaking board support
    should use 'imply' instead, to allow users to disable it.

    These options are changed for mach-socfpga:
    - DM_SPI & DM_SPI_FLASH: only required with QSPI support enabled
    - SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION: the boot rom supports a
    partitionless mode also, where SPL is located at address 0
    - HW_WATCHDOG: while all mainline board defconfigs use it, U-Boot
    should still work without it.

    Signed-off-by: Simon Goldschmidt

    Simon Goldschmidt
     
  • All Socfpga boards from ./include/configs/socfpga_* define
    CONFIG_HW_WATCHDOG.
    To ease CONFIG_HW_WATCHDOG conversion to Kconfig select it in
    config ARCH_SOCFPGA (arch/arm/Kconfig) section.

    Signed-off-by: Lukasz Majewski
    Signed-off-by: Simon Goldschmidt

    Lukasz Majewski
     

14 Feb, 2018

1 commit


08 Feb, 2018

4 commits


04 Feb, 2018

1 commit


31 Jan, 2018

1 commit


30 Jan, 2018

3 commits


29 Jan, 2018

5 commits


26 Jan, 2018

1 commit


24 Jan, 2018

1 commit


20 Jan, 2018

1 commit

  • This adds support for '-machine virt' on AArch64. This is rather simple:
    we just add TARGET_QEMU_ARM_xxBIT to select a few different Kconfig
    symbols, provide the ARMv8 memory map from the board file and add a new
    defconfig based on the 32-bit defconfig.

    Signed-off-by: Tuomas Tynkkynen
    Reviewed-by: Tom Rini

    Tuomas Tynkkynen
     

16 Jan, 2018

1 commit


13 Jan, 2018

2 commits

  • Allow placing a Linux kernel image header at the start of the U-Boot
    binary. This is useful since the image header reports the amount of memory
    (BSS and similar) that U-Boot needs to use, but that isn't part of the
    binary size. This can be used by the code that loads U-Boot into memory to
    determine where to load U-Boot, based on other users of memory.

    Signed-off-by: Stephen Warren
    Signed-off-by: Tom Warren

    Stephen Warren
     
  • U-Boot typically uses a hard-coded value for the stack pointer before
    relocation. Implement option SYS_INIT_SP_BSS_OFFSET to instead calculate
    the initial SP at run-time. This is useful to avoid hard-coding addresses
    into U-Boot, so that can be loaded and executed at arbitrary addresses and
    thus avoid using arbitrary addresses at runtime. This option's value is
    the offset added to &_bss_start in order to calculate the stack pointer.
    This offset should be large enough so that the early malloc region, global
    data (gd), and early stack usage do not overlap any appended DTB.

    Signed-off-by: Stephen Warren
    Signed-off-by: Tom Warren

    Stephen Warren
     

11 Jan, 2018

1 commit

  • 855873: An eviction might overtake a cache clean operation
    Workaround: The erratum can be avoided by upgrading cache clean by
    address operations to cache clean and invalidate operations. For
    Cortex-A53 r0p3 and later release, this can be achieved by setting
    CPUACTLR.ENDCCASCI to 1.

    This patch is to implement the workaround for this erratum.

    Signed-off-by: Alison Wang
    Reviewed-by: York Sun

    Alison Wang
     

15 Dec, 2017

1 commit


13 Dec, 2017

1 commit


29 Nov, 2017

1 commit


22 Nov, 2017

1 commit

  • Rockchip SoCs bootrom design is like this:
    - First 2KB or 4KB internal memory is for bootrom stack and heap;
    - Then the first 4-byte suppose to be a TAG like 'RK33';
    - The the following memory address end with '0004' is the first
    instruction load and running by bootrom;

    Let's use the boot0 hook to reserve the first 4-byte tag for all
    the Rockchip SoCs.

    Signed-off-by: Philipp Tomsich
    [Commit message taken from an older patch by:]
    Signed-off-by: Kever Yang

    Philipp Tomsich
     

17 Nov, 2017

2 commits

  • This is required in the case where U-Boot is typically loaded and run at
    a particular address, but for some reason the RAM at that location is not
    available, e.g. due to memory fragmentation loading other boot binaries or
    firmware, splitting an SMP complex between various different OSs without
    using e.g. the EL2 second-stage page tables to hide the memory asignments,
    or due to known ECC failures.

    Signed-off-by: Stephen Warren

    Stephen Warren
     
  • Currently, pylibfdt is always compiled if swig is installed on your
    machine. It is really annoying because most of targets (excepts
    x86, sunxi, rockchip) do not use dtoc or binman.

    "checkbinman" and "checkdtoc" are wrong. It is odd that the final
    build stage checks if we have built necessary tools. If your platform
    depends on dtoc/binman, you must be able to build pylibfdt. If swig
    is not installed, it should fail immediately.

    I added PYLIBFDT, DTOC, BINMAN entries to Kconfig. They should be
    property select:ed by platforms that need them. Kbuild will descend
    into scripts/dtc/pylibfdt/ only when CONFIG_PYLIBFDT is enabled.

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Simon Glass

    Masahiro Yamada
     

16 Nov, 2017

2 commits


07 Nov, 2017

1 commit

  • The motivation for moving MX25 selection to Kconfig is to be
    able to better handle MX25 specific errata, so that an errata option
    can be selected at SoC level instead of board level.

    This selection method also aligns with the way other i.MX SoCs are
    selected in U-Boot.

    Signed-off-by: Fabio Estevam
    Acked-by: Sebastien Bourdelin
    Reviewed-by: Benoît Thébaudeau

    Fabio Estevam