summaryrefslogtreecommitdiff
path: root/scripts/gdb/vmlinux-gdb.py
diff options
context:
space:
mode:
authorApurva Nandan <a-nandan@ti.com>2023-08-12 00:50:28 +0530
committerNishanth Menon <nm@ti.com>2023-08-11 15:54:18 -0500
commit3a4086985696295577c20ae558f99d974067e316 (patch)
tree86587a3d2bc5f7e9d09e8a741525ff6fea51b8d8 /scripts/gdb/vmlinux-gdb.py
parent1f7226a5e52cb8b90771cefc29077f9ce13a3c90 (diff)
arm64: dts: ti: k3-j784s4: Add phase tags marking
bootph-all as phase tag was added to dt-schema (dtschema/schemas/bootph.yaml) to cover U-Boot challenges with DT. That's why add it also to Linux to be aligned with bootloader requirement. On TI K3 J784S4 SoC, only secure_proxy_mcu and secure_proxy_sa3 nodes are exclusively used by R5 bootloader, rest of the dts nodes with bootph-* are used by later boot stages also. And secure_proxy_mcu and secure_proxy_sa3 are disabled in kernel device tree, and will be only enabled in R5 bootloader device tree. So, bootph-pre-ram for secure_proxy_mcu and secure_proxy_sa3 will be added in R5 bootloader device tree only. Add bootph-all for all other nodes that are used in the bootloader on K3 J784S4 SoC, and bootph-pre-ram is not needed specifically for any node in kernel dts. Signed-off-by: Apurva Nandan <a-nandan@ti.com> Reviewed-by: Udit Kumar <u-kumar1@ti.com> Link: https://lore.kernel.org/r/20230811192030.3480616-2-a-nandan@ti.com Signed-off-by: Nishanth Menon <nm@ti.com>
Diffstat (limited to 'scripts/gdb/vmlinux-gdb.py')
0 files changed, 0 insertions, 0 deletions