From: Conor Dooley <conor@kernel.org>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Nishanth Menon <nm@ti.com>,
Tero Kristo <kristo@kernel.org>,
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: Re: [PATCH 1/2] dt-bindings: soc: ti: k3-ringacc: Describe cfg reg region
Date: Wed, 9 Aug 2023 22:27:29 +0100 [thread overview]
Message-ID: <20230809-letdown-fretted-0210aee28452@spud> (raw)
In-Reply-To: <20230809175932.2553156-2-vigneshr@ti.com>
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
On Wed, Aug 09, 2023 at 11:29:31PM +0530, Vignesh Raghavendra wrote:
> RINGACC module on K3 SoCs have CFG register region which is usually
> configured by a Device Management firmware. But certain entities such as
> bootloader (like U-Boot) may have to access them directly. Describe this
> region in the binding documentation for completeness of module
> description.
>
> Keep the binding compatible with existing DTS files by requiring first
> four regions to be present at least.
>
> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-08-09 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 17:59 [PATCH 0/2] soc: ti: k3-ringacc: Add additional register regions Vignesh Raghavendra
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 [this message]
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=20230809-letdown-fretted-0210aee28452@spud \
--to=conor@kernel.org \
--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 \
--cc=vigneshr@ti.com \
/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).