From: Nishanth Menon <nm@ti.com>
To: Udit Kumar <u-kumar1@ti.com>
Cc: <vigneshr@ti.com>, <kristo@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<afd@ti.com>, <u-boot@lists.denx.de>, <n-francis@ti.com>
Subject: Re: [PATCH 1/1] arm64: dts: ti: k3-j721s2: Add reserved status in msmc
Date: Wed, 3 May 2023 09:51:07 -0500 [thread overview]
Message-ID: <20230503145107.e447yxvn5e6fmz4g@patronize> (raw)
In-Reply-To: <20230503144706.1265672-2-u-kumar1@ti.com>
On 20:17-20230503, Udit Kumar wrote:
> Mark atf, l3-cache and tifs node as reserved.
why? (I am not reading the cover-letter for a 1 patch)
>
> Signed-off-by: Udit Kumar <u-kumar1@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi b/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi
> index 2dd7865f7654..791993060f44 100644
> --- a/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi
> @@ -14,14 +14,17 @@ msmc_ram: sram@70000000 {
> ranges = <0x0 0x0 0x70000000 0x400000>;
>
> atf-sram@0 {
> + status = "reserved";
> reg = <0x0 0x20000>;
> };
>
> tifs-sram@1f0000 {
> + status = "reserved";
> reg = <0x1f0000 0x10000>;
> };
>
> l3cache-sram@200000 {
> + status = "reserved";
> reg = <0x200000 0x200000>;
> };
> };
> --
> 2.34.1
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2023-05-03 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 14:47 [RFC PATCH 0/1] arm64: dts: ti: k3-j721s2: handling subnode of msmc node Udit Kumar
2023-05-03 14:47 ` [PATCH 1/1] arm64: dts: ti: k3-j721s2: Add reserved status in msmc Udit Kumar
2023-05-03 14:51 ` Nishanth Menon [this message]
2023-05-03 16:30 ` Krzysztof Kozlowski
2023-05-05 4:58 ` Kumar, Udit
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=20230503145107.e447yxvn5e6fmz4g@patronize \
--to=nm@ti.com \
--cc=afd@ti.com \
--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=n-francis@ti.com \
--cc=robh+dt@kernel.org \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@ti.com \
--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).