From: Nishanth Menon <nm@ti.com>
To: Suman Anna <s-anna@ti.com>
Cc: Lokesh Vutla <lokeshvutla@ti.com>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 4/4] arm64: dts: ti: k3-am642-evm/sk: Reserve some on-chip SRAM for R5Fs
Date: Tue, 15 Jun 2021 14:42:07 -0500 [thread overview]
Message-ID: <20210615194207.ww3ed7hmibfw6tnd@swiftness> (raw)
In-Reply-To: <209c545d-c012-9ee8-34ca-bc4f48dbfbcb@ti.com>
On 13:05-20210614, Suman Anna wrote:
> >> +&oc_sram {
> >> + main_r5fss0_core0_sram: r5f-sram@40000 {
> >> + reg = <0x40000 0x40000>;
> >> + };
> >> +
> >> + main_r5fss0_core1_sram: r5f-sram@80000 {
> >> + reg = <0x80000 0x40000>;
> >> + };
> >> +
> >> + main_r5fss1_core0_sram: r5f-sram@c0000 {
> >> + reg = <0xc0000 0x40000>;
> >> + };
> >> +
> >> + main_r5fss1_core1_sram: r5f-sram@100000 {
> >> + reg = <0x100000 0x40000>;
> >> + };
> >> +};
> >
>
> These addresses are currently in sync with the corresponding firmware linker map
> files. Any changes needed here should also be aligned and updated with all the
> firmwares then.
>
> Nishanth,
> How about dropping this patch until we conclude the discussion and picking up
> the rest?
Lets skip this patch for this merge cycle - aka stay compatible with the
previous reference binaries that do not use OCSRAM (aka not pick up
4x latency improvement), till we figure out a future looking and
relatively stable memory map that considers:
a) R5s IPC RAM
+ future usage:
b) M4F IPC RAM
c) ICSSG buffer RAMs
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2021-06-15 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 14:47 [PATCH 0/4] Add R5F nodes on TI K3 AM64x SoCs Suman Anna
2021-05-28 14:47 ` [PATCH 1/4] arm64: dts: ti: k3-am64-main: Add MAIN domain R5F cluster nodes Suman Anna
2021-05-28 14:47 ` [PATCH 2/4] arm64: dts: ti: k3-am642-evm/sk: Add mailboxes to R5Fs Suman Anna
2021-05-28 14:47 ` [PATCH 3/4] arm64: dts: ti: k3-am642-evm/sk: Add DDR carveout memory nodes for R5Fs Suman Anna
2021-05-28 14:47 ` [PATCH 4/4] arm64: dts: ti: k3-am642-evm/sk: Reserve some on-chip SRAM " Suman Anna
2021-06-09 14:01 ` Vignesh Raghavendra
2021-06-11 19:13 ` Nishanth Menon
2021-06-14 18:05 ` Suman Anna
2021-06-15 19:42 ` Nishanth Menon [this message]
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=20210615194207.ww3ed7hmibfw6tnd@swiftness \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lokeshvutla@ti.com \
--cc=s-anna@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).