From: Udit Kumar <u-kumar1@ti.com>
To: <nm@ti.com>, <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>
Cc: Udit Kumar <u-kumar1@ti.com>
Subject: [RFC PATCH 0/1] arm64: dts: ti: k3-j721s2: handling subnode of msmc node
Date: Wed, 3 May 2023 20:17:05 +0530 [thread overview]
Message-ID: <20230503144706.1265672-1-u-kumar1@ti.com> (raw)
TI K3 SOCs have msmc sram, part of it can be configured as L3 cache
depending upon system firmware configuration file.
This could be possible to have no L3 cache or variable size of
L3 cache.
In either case top of 64KB of SRAM has to be reserved for system
firmware called tifs.
https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/general/core.html?highlight=msmc
Section: TISCI_MSG_QUERY_MSMC.
But u-boot as part of fix up is deleting sysfw and l3cache node
before passing DT to OS
https://github.com/u-boot/u-boot/blob/master/arch/arm/mach-k3/common.c#L412
In my view we can handle in two ways
1) delete tifs node as well
In this case, only accessible sram will be visible to OS
https://lore.kernel.org/all/20230420081128.3617214-1-u-kumar1@ti.com/
2) make these nodes (tifs, atf and l3cache) as reserved,
so that OS has complete view of memory.
This is patch for option 2.
Nishanth suggested to discuss in k.org group
https://lore.kernel.org/all/20230502230022.5pjywy6h7oqrkmwh@elusive/
So sending this patch for suggestion for selection right option.
Also other options are welcome.
Udit Kumar (1):
arm64: dts: ti: k3-j721s2: Add reserved status in msmc node.
arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 3 +++
1 file changed, 3 insertions(+)
--
2.34.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-05-03 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 14:47 Udit Kumar [this message]
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
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=20230503144706.1265672-1-u-kumar1@ti.com \
--to=u-kumar1@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=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=u-boot@lists.denx.de \
--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