From: Santhosh Kumar K <s-k6@ti.com>
To: Andrew Davis <afd@ti.com>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/4] arm64: dts: ti: k3-am65: Include entire FSS region in ranges
Date: Fri, 30 Aug 2024 16:30:07 +0530 [thread overview]
Message-ID: <da3410c9-232a-4044-9ba1-087e8fef7549@ti.com> (raw)
In-Reply-To: <20240828172956.26630-2-afd@ti.com>
Hi, Andrew,
On 28/08/24 22:59, Andrew Davis wrote:
> Add FSS regions at 0x50000000, 0x400000000, and 0x600000000. Although
> not used currently by the Linux FSS driver, these regions belong to
> the FSS and should be included in the ranges mapping.
>
> While here, a couple of these numbers had missing zeros which was
> hidden by odd alignments, fix both these issues.
>
> Signed-off-by: Andrew Davis <afd@ti.com>
> Reviewed-by: Santhosh Kumar K <s-k6@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi | 8 ++++----
> arch/arm64/boot/dts/ti/k3-am65.dtsi | 12 +++++-------
> 2 files changed, 9 insertions(+), 11 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi b/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
> index 43c6118d2bf0f..1a251d13f80ab 100644
> --- a/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
> @@ -292,13 +292,13 @@ fss: bus@47000000 {
> ranges = <0x0 0x47000000 0x0 0x47000000 0x0 0x100>, /* FSS Control */
> <0x0 0x47040000 0x0 0x47040000 0x0 0x100>, /* OSPI0 Control */
> <0x0 0x47050000 0x0 0x47050000 0x0 0x100>, /* OSPI1 Control */
> - <0x5 0x00000000 0x5 0x00000000 0x1 0x0000000>, /* OSPI0 Memory */
> - <0x7 0x00000000 0x7 0x00000000 0x1 0x0000000>; /* OSPI1 Memory */
> + <0x0 0x50000000 0x0 0x50000000 0x0 0x10000000>, /* FSS data region 1 */
> + <0x4 0x00000000 0x4 0x00000000 0x4 0x00000000>; /* FSS data region 0/3 */
>
> ospi0: spi@47040000 {
> compatible = "ti,am654-ospi", "cdns,qspi-nor";
> reg = <0x0 0x47040000 0x0 0x100>,
> - <0x5 0x00000000 0x1 0x0000000>;
> + <0x5 0x00000000 0x1 0x00000000>;
> interrupts = <GIC_SPI 552 IRQ_TYPE_LEVEL_HIGH>;
> cdns,fifo-depth = <256>;
> cdns,fifo-width = <4>;
> @@ -316,7 +316,7 @@ ospi0: spi@47040000 {
> ospi1: spi@47050000 {
> compatible = "ti,am654-ospi", "cdns,qspi-nor";
> reg = <0x0 0x47050000 0x0 0x100>,
> - <0x7 0x00000000 0x1 0x00000000>;
> + <0x7 0x00000000 0x1 0x00000000>;
> interrupts = <GIC_SPI 553 IRQ_TYPE_LEVEL_HIGH>;
> cdns,fifo-depth = <256>;
> cdns,fifo-width = <4>;
> diff --git a/arch/arm64/boot/dts/ti/k3-am65.dtsi b/arch/arm64/boot/dts/ti/k3-am65.dtsi
> index c59baebc5a25b..c74a0a25832cb 100644
> --- a/arch/arm64/boot/dts/ti/k3-am65.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am65.dtsi
> @@ -69,11 +69,10 @@ cbass_main: bus@100000 {
> <0x00 0x45100000 0x00 0x45100000 0x00 0x00c24000>,
> <0x00 0x46000000 0x00 0x46000000 0x00 0x00200000>,
> <0x00 0x47000000 0x00 0x47000000 0x00 0x00068400>,
> - <0x00 0x50000000 0x00 0x50000000 0x00 0x8000000>,
> + <0x00 0x50000000 0x00 0x50000000 0x00 0x10000000>,
> <0x00 0x6f000000 0x00 0x6f000000 0x00 0x00310000>, /* A53 PERIPHBASE */
> - <0x00 0x70000000 0x00 0x70000000 0x00 0x200000>,
> - <0x05 0x00000000 0x05 0x00000000 0x01 0x0000000>,
> - <0x07 0x00000000 0x07 0x00000000 0x01 0x0000000>;
> + <0x00 0x70000000 0x00 0x70000000 0x00 0x00200000>,
> + <0x04 0x00000000 0x04 0x00000000 0x04 0x00000000>;
Suggested changes have been added, thanks!
Acked-by: Santhosh Kumar K <s-k6@ti.com>
>
> cbass_mcu: bus@28380000 {
> compatible = "simple-bus";
> @@ -89,9 +88,8 @@ cbass_mcu: bus@28380000 {
> <0x00 0x45100000 0x00 0x45100000 0x00 0x00c24000>, /* MMRs, remaining NAVSS */
> <0x00 0x46000000 0x00 0x46000000 0x00 0x00200000>, /* CPSW */
> <0x00 0x47000000 0x00 0x47000000 0x00 0x00068400>, /* OSPI space 1 */
> - <0x00 0x50000000 0x00 0x50000000 0x00 0x8000000>, /* FSS OSPI0 data region 1 */
> - <0x05 0x00000000 0x05 0x00000000 0x01 0x0000000>, /* FSS OSPI0 data region 3*/
> - <0x07 0x00000000 0x07 0x00000000 0x01 0x0000000>; /* FSS OSPI1 data region 3*/
> + <0x00 0x50000000 0x00 0x50000000 0x00 0x10000000>, /* FSS data region 1 */
> + <0x04 0x00000000 0x04 0x00000000 0x04 0x00000000>; /* FSS data region 0/3 */
>
> cbass_wakeup: bus@42040000 {
> compatible = "simple-bus";
next prev parent reply other threads:[~2024-08-30 11:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 17:29 [PATCH v2 0/4] K3 include " Andrew Davis
2024-08-28 17:29 ` [PATCH v2 1/4] arm64: dts: ti: k3-am65: Include " Andrew Davis
2024-08-30 11:00 ` Santhosh Kumar K [this message]
2024-08-28 17:29 ` [PATCH v2 2/4] arm64: dts: ti: k3-j721e: " Andrew Davis
2024-08-28 17:29 ` [PATCH v2 3/4] arm64: dts: ti: k3-j721s2: " Andrew Davis
2024-08-28 17:29 ` [PATCH v2 4/4] arm64: dts: ti: k3-j784s4: " Andrew Davis
2024-09-01 20:21 ` [PATCH v2 0/4] K3 include " Nishanth Menon
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=da3410c9-232a-4044-9ba1-087e8fef7549@ti.com \
--to=s-k6@ti.com \
--cc=afd@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=robh+dt@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
all inboxes | Powered by JetHome®