From: Neha Malcom Francis <n-francis@ti.com>
To: "Kumar, Udit" <u-kumar1@ti.com>, "Davis, Andrew" <afd@ti.com>,
"Dasan, Nikhil" <n-dasan@ti.com>, "Menon, Nishanth" <nm@ti.com>,
"trini@konsulko.com" <trini@konsulko.com>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
"Raghavendra, Vignesh" <vigneshr@ti.com>
Subject: Re: [PATCH v2] arch: arm: mach-k3: Delete tifs node in DT fixup
Date: Wed, 26 Apr 2023 17:31:10 +0530 [thread overview]
Message-ID: <4b016f2b-678a-43ff-bca0-9c2aee50eb02@ti.com> (raw)
In-Reply-To: <89918e21335c4fa18ae0d2447bea192b@ti.com>
Hi Udit
On 26/04/23 16:09, Kumar, Udit wrote:
> Hi Neha,
>
>> Hi Udit,
>
> [..]
>
>>>>
>>>> I do have a general doubt; why do we have only atf-sram sub-node in
>>>> msmc_sram in all other devices (j721e, j7200 and am65) except j721s2?
>>>
>>> let me know, which source code you are referring to
>>>
>>
>> In U-Boot, for j721e, j7200 and am65; they *only* contain atf-sram?
>
> For u-boot please see
>
> https://elixir.bootlin.com/u-boot/latest/source/arch/arm/dts/k3-j721s2-main.dtsi#L16
>
>>> I could see for j721s2 as well, in uboot[0] and Linux[1]
> [..]
>
What I mean to ask is, why aren't there tifs or l3cache subnodes in
j721e, j7200 and am65?
>> Thanking You
>> Neha Malcom Francis
--
Thanking You
Neha Malcom Francis
next prev parent reply other threads:[~2023-04-26 12:01 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 ` [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 [this message]
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=4b016f2b-678a-43ff-bca0-9c2aee50eb02@ti.com \
--to=n-francis@ti.com \
--cc=afd@ti.com \
--cc=n-dasan@ti.com \
--cc=nm@ti.com \
--cc=trini@konsulko.com \
--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