From: Udit Kumar <u-kumar1@ti.com>
To: <afd@ti.com>, <nm@ti.com>, <vigneshr@ti.com>,
<trini@konsulko.com>, <u-boot@lists.denx.de>, <n-francis@ti.com>,
<n-dasan@ti.com>
Cc: Udit Kumar <u-kumar1@ti.com>
Subject: [PATCH] arch: arm: mach-k3: Delete tifs node in DT fixup
Date: Wed, 19 Apr 2023 11:43:52 +0530 [thread overview]
Message-ID: <20230419061352.3156023-1-u-kumar1@ti.com> (raw)
This patch deletes tifs DT node as part of fixup.
TISCI API reported msmc_size, does not include
64KB reserved size for tifs aka MSMC comms memory.
As part of fixup, original code uses TISCI API
reported msmc_size as size for sram DT node.
tifs node is similar to l3-cache, which should
hold address above msms_size, and should be deleted
before passing control to OS.
Documentation
https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/general/core.html?highlight=msmc#tisci-msg-query-msmc
Signed-off-by: Udit Kumar <u-kumar1@ti.com>
---
arch/arm/mach-k3/common.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-k3/common.c b/arch/arm/mach-k3/common.c
index a2adb791f6..4651744821 100644
--- a/arch/arm/mach-k3/common.c
+++ b/arch/arm/mach-k3/common.c
@@ -349,9 +349,11 @@ int fdt_fixup_msmc_ram(void *blob, char *parent_path, char *node_name)
size = fdt_read_number(sub_reg, 1);
debug("%s: subnode = %d, addr = 0x%x. size = 0x%x\n", __func__,
subnode, addr, size);
+
if (addr + size > msmc_size ||
!strncmp(fdt_get_name(blob, subnode, &len), "sysfw", 5) ||
- !strncmp(fdt_get_name(blob, subnode, &len), "l3cache", 7)) {
+ !strncmp(fdt_get_name(blob, subnode, &len), "l3cache", 7) ||
+ !strncmp(fdt_get_name(blob, subnode, &len), "tifs", 4)) {
fdt_del_node(blob, subnode);
debug("%s: deleting subnode %d\n", __func__, subnode);
if (!prev_node)
--
2.34.1
next reply other threads:[~2023-04-19 7:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 6:13 Udit Kumar [this message]
2023-04-19 15:52 ` [PATCH] arch: arm: mach-k3: Delete tifs node in DT fixup Nishanth Menon
2023-04-20 7:58 ` Kumar, Udit
2023-04-20 8:11 ` [PATCH v2] " Udit Kumar
2023-04-26 9:26 ` Neha Malcom Francis
2023-04-26 10:05 ` Kumar, Udit
2023-04-26 10:31 ` Neha Malcom Francis
2023-04-26 10:39 ` Kumar, Udit
2023-04-26 12:01 ` Neha Malcom Francis
2023-04-26 13:37 ` Nishanth Menon
2023-04-26 14:13 ` Kumar, Udit
2023-05-01 14:46 ` Andrew Davis
2023-05-02 7:04 ` Neha Malcom Francis
2023-05-02 7:27 ` Kumar, Udit
2023-05-02 23:00 ` Nishanth Menon
2023-05-03 9:30 ` Kumar, Udit
-- strict thread matches above, loose matches on Subject: below --
2025-01-13 4:25 [PATCH] " Udit Kumar
2025-01-20 18:07 ` Tom Rini
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=20230419061352.3156023-1-u-kumar1@ti.com \
--to=u-kumar1@ti.com \
--cc=afd@ti.com \
--cc=n-dasan@ti.com \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=trini@konsulko.com \
--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