Skip to content
Snippets Groups Projects
  • Alex Deymo's avatar
    82f766d1
    Allow boards to initialize the DT at runtime. · 82f766d1
    Alex Deymo authored and Tom Rini's avatar Tom Rini committed
    
    In some boards like the Raspberry Pi the initial bootloader will pass
    a DT to the kernel. When using U-Boot as such kernel, the board code in
    U-Boot should be able to provide U-Boot with this, already assembled
    device tree blob.
    
    This patch introduces a new config option CONFIG_OF_BOARD to use instead
    of CONFIG_OF_EMBED or CONFIG_OF_SEPARATE which will initialize the DT
    from a board-specific funtion instead of bundling one with U-Boot or as
    a separated file. This allows boards like the Raspberry Pi to reuse the
    device tree passed from the bootcode.bin and start.elf firmware
    files, including the run-time selected device tree overlays.
    
    Signed-off-by: default avatarAlex Deymo <deymo@google.com>
    Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
    82f766d1
    History
    Allow boards to initialize the DT at runtime.
    Alex Deymo authored and Tom Rini's avatar Tom Rini committed
    
    In some boards like the Raspberry Pi the initial bootloader will pass
    a DT to the kernel. When using U-Boot as such kernel, the board code in
    U-Boot should be able to provide U-Boot with this, already assembled
    device tree blob.
    
    This patch introduces a new config option CONFIG_OF_BOARD to use instead
    of CONFIG_OF_EMBED or CONFIG_OF_SEPARATE which will initialize the DT
    from a board-specific funtion instead of bundling one with U-Boot or as
    a separated file. This allows boards like the Raspberry Pi to reuse the
    device tree passed from the bootcode.bin and start.elf firmware
    files, including the run-time selected device tree overlays.
    
    Signed-off-by: default avatarAlex Deymo <deymo@google.com>
    Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>