From: Nishanth Menon <nm@ti.com>
To: Andrew Davis <afd@ti.com>
Cc: Neha Malcom Francis <n-francis@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>,
Apurva Nandan <a-nandan@ti.com>, <u-boot@lists.denx.de>
Subject: Re: [PATCH RFC 0/2] Unify K3 initial memory map
Date: Thu, 23 Nov 2023 10:29:12 -0600 [thread overview]
Message-ID: <20231123162912.vobn72jiy5ntq4ha@wired> (raw)
In-Reply-To: <20231122151411.11268-1-afd@ti.com>
On 09:14-20231122, Andrew Davis wrote:
> Hello all,
>
> This is just an RFC as it probably breaks remoteproc loading.
> I wanted to post anyway as the complexity of having a dedicated
> memory map for each SoC came up in a different series.
>
> Or maybe we can take this now and that will expose the issue in
> remoteproc loading better and force someone to go fix it. :)
>
> This series depends on this[0].
>
> Thanks,
> Andrew
>
> [0] https://patchwork.ozlabs.org/project/uboot/patch/20231106165205.22066-1-afd@ti.com/
>
> Andrew Davis (2):
> arm: mach-k3: Remove non-cached memory map areas
> arm: mach-k3: Merge initial memory maps
>
> arch/arm/mach-k3/arm64-mmu.c | 253 +----------------------------------
> 1 file changed, 2 insertions(+), 251 deletions(-)
>
> --
> 2.39.2
>
Could you rebase and submit as non-RFC? Please free to add:
Reviewed-by: Nishanth Menon <nm@ti.com>
Tested-by: Nishanth Menon <nm@ti.com>
tested along with the v2 of dependency patch https://lore.kernel.org/all/20231122211218.607757-1-afd@ti.com/
on top of:
next 054222eb68f6 Merge branch '2023-11-22-TI-K3-cleanups' into next
platforms tested:
beagleplay-gp-uart
j721s2-evm
am68_sk-fs
j721e-sk
j721e-idk-gw
j7200-hsevm
j7200-evm
am64xx-hsevm
am64xx_sk-fs
am62xx_sk-fs
am62xx-sk
am62axx_sk-fs
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2023-11-23 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 15:14 [PATCH RFC 0/2] Unify K3 initial memory map Andrew Davis
2023-11-22 15:14 ` [PATCH RFC 1/2] arm: mach-k3: Remove non-cached memory map areas Andrew Davis
2023-11-22 15:14 ` [PATCH RFC 2/2] arm: mach-k3: Merge initial memory maps Andrew Davis
2023-11-23 16:29 ` 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=20231123162912.vobn72jiy5ntq4ha@wired \
--to=nm@ti.com \
--cc=a-nandan@ti.com \
--cc=afd@ti.com \
--cc=n-francis@ti.com \
--cc=sjg@chromium.org \
--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