All of lore.kernel.org
 help / color / mirror / Atom feed
From: Udit Kumar <u-kumar1@ti.com>
To: <afd@ti.com>, <n-dasan@ti.com>, <n-francis@ti.com>, <nm@ti.com>,
	<trini@konsulko.com>, <u-boot@lists.denx.de>, <vigneshr@ti.com>
Cc: Udit Kumar <u-kumar1@ti.com>
Subject: [PATCH v2] arch: arm: mach-k3: Delete tifs node in DT fixup
Date: Thu, 20 Apr 2023 13:41:28 +0530	[thread overview]
Message-ID: <20230420081128.3617214-1-u-kumar1@ti.com> (raw)
In-Reply-To: <20230419061352.3156023-1-u-kumar1@ti.com>

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>
---
Changes since v1:
https://lore.kernel.org/all/20230419061352.3156023-1-u-kumar1@ti.com/
- moved tifs check above l3 as

 arch/arm/mach-k3/common.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm/mach-k3/common.c b/arch/arm/mach-k3/common.c
index a2adb791f6..33b1f10d58 100644
--- a/arch/arm/mach-k3/common.c
+++ b/arch/arm/mach-k3/common.c
@@ -351,6 +351,7 @@ int fdt_fixup_msmc_ram(void *blob, char *parent_path, char *node_name)
 		      subnode, addr, size);
 		if (addr + size > msmc_size ||
 		    !strncmp(fdt_get_name(blob, subnode, &len), "sysfw", 5) ||
+		    !strncmp(fdt_get_name(blob, subnode, &len), "tifs", 4)  ||
 		    !strncmp(fdt_get_name(blob, subnode, &len), "l3cache", 7)) {
 			fdt_del_node(blob, subnode);
 			debug("%s: deleting subnode %d\n", __func__, subnode);
-- 
2.34.1


  parent reply	other threads:[~2023-04-20  8:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19  6:13 [PATCH] arch: arm: mach-k3: Delete tifs node in DT fixup Udit Kumar
2023-04-19 15:52 ` Nishanth Menon
2023-04-20  7:58   ` Kumar, Udit
2023-04-20  8:11 ` Udit Kumar [this message]
2023-04-26  9:26   ` [PATCH v2] " 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

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=20230420081128.3617214-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.