Ringacc on TI K3 SoCs have configuration registers region which is usually hidden from Linux and configured via Device Manager Firmware APIs. But certain early SWs like bootloader which run before Device Manager is fully up would need to directly configure these registers and thus require to be in DT description. This add bindings for the cfg region and also adds them to DT files. Backward compatibility is maintained to existing DT by only mandating existing regions to be present and this new region as optional. Nishanth: I am hoping its possible for you to take bindings and DT via k3-dts-next once reviewed. Vignesh Raghavendra (2): dt-bindings: soc: ti: k3-ringacc: Describe cfg reg region arm64: dts: ti: k3: Add cfg reg region to ringacc node Documentation/devicetree/bindings/soc/ti/k3-ringacc.yaml | 9 +++++++-- arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 5 +++-- arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi | 6 ++++-- arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 5 +++-- arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 6 ++++-- arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 5 +++-- arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 5 +++-- arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 5 +++-- arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 5 +++-- arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 5 +++-- arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 5 +++-- 11 files changed, 39 insertions(+), 22 deletions(-) -- 2.41.0
