summaryrefslogtreecommitdiff
path: root/scripts/checker-valid.sh
diff options
context:
space:
mode:
authorSerge Semin <fancer.lancer@gmail.com>2020-10-10 16:11:36 +0300
committerSerge Semin <fancer.lancer@gmail.com>2026-08-13 01:21:23 +0300
commit676412c0e863d3f4ae0c394e4bc6184659452734 (patch)
treed5fb84c0a49f390be27bd663a5466128a8a78539 /scripts/checker-valid.sh
parent2f1b58de051761c333ca3771d7db986dd2aa5e4f (diff)
downloadlinux-boot/bt1.tar.gz
linux-boot/bt1.zip
dt-bindings: sram: Add Baikal-T1 Boot SRAM bindingboot/bt1
Baikal-T1 is equipped with embedded SRAM of 64KB being accessed over the AXI interconnect. It's normally used at the SoC startup procedure to execute the system bootloader before the normal memory is initialized. Alternatively the internal SRAM can be used to automatically pre-load a bootloader code from external SPI-flash if corresponding Baikal-T1 Boot mode is enabled, But functionally the later feature isn't that useful, since SRAM is too small while the initial software can be XIP-ed right from the SPI-flash and then download the system software from any place it wants. Baikal-T1 SRAM is clocked with a dedicated AXI-clock source and can be reset by toggling the corresponding reset line. Due to the ability to serve as a target of the system startup code pre-loading SRAM is connected to the Baikal-T1 Boot Controller, which needs to be tuned in order to get a direct access to the memory. The later is implemented in the framework of the mux-controller functionality. Signed-off-by: Serge Semin <fancer.lancer@gmail.com>
Diffstat (limited to 'scripts/checker-valid.sh')
0 files changed, 0 insertions, 0 deletions