From: Vignesh Raghavendra <vigneshr@ti.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>
Cc: Peter Ujfalusi <peter.ujfalusi@gmail.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 0/2] soc: ti: k3-ringacc: Add additional register regions
Date: Wed, 9 Aug 2023 23:29:30 +0530 [thread overview]
Message-ID: <20230809175932.2553156-1-vigneshr@ti.com> (raw)
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
next reply other threads:[~2023-08-09 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 17:59 Vignesh Raghavendra [this message]
2023-08-09 17:59 ` [PATCH 1/2] dt-bindings: soc: ti: k3-ringacc: Describe cfg reg region Vignesh Raghavendra
2023-08-09 21:27 ` Conor Dooley
2023-08-09 17:59 ` [PATCH 2/2] arm64: dts: ti: k3: Add cfg reg region to ringacc node Vignesh Raghavendra
2023-08-10 5:18 ` [PATCH 0/2] soc: ti: k3-ringacc: Add additional register regions Nishanth Menon
2023-08-11 15:20 ` Péter Ujfalusi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230809175932.2553156-1-vigneshr@ti.com \
--to=vigneshr@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=peter.ujfalusi@gmail.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).