> Subject: Re: [PATCHv3] remoteproc: imx_rproc: add missing DRAM
> ranges for i.MX93
>
> On Mon, May 25, 2026 at 02:20:31PM +0800, Zhiqiang Hou wrote:
> > From: Hou Zhiqiang <[email protected]>
> >
> > The M33 DRAM address ranges 0xA0000000-0xAFFFFFFF(None
> Secure)
>
> s/none/non
>
> > and 0xB0000000-0xBFFFFFFF(Secure) are both mapped to
> > 0xA0000000-0xAFFFFFFF in the A55 address space.
> >
>
> So the M33 has secure and non-secure ranges mapped at the same
> address in the A55?
Yes.
Bit28 is used to differentiate secure and non-secure from M33 view
per NXP design.
Cortex-A55 cores has same view as system view.
Are you sure it is not the other way around, i.e
> A55 has secure and non-secure address ranges that both map to the
> same address on M33?
No. only M33 use bit28 to differentiate secure/non-secure region
per NXP design.
M33
system map / A55
-----------------------------------------------------
-----------------------------
0xA0000000 - 0xAFFFFFFF (non secure) 0xA.... - 0xAF....
-----------------------------------------------------
-----------------------------
0xB0000000 - 0xBFFFFFFF (secure) M33 not accessiable
-----------------------------------------------------
-----------------------------
>
> More details are needed in this changelog.
>
> I'm also wondering how this problem hasn't been fixed before. The
> original patch (9222fabf0e39) was merged over 4 years ago...
At that time, I could only test remoteproc with what our MCU SW
team delivered to me.
For regions that I was not able to test, I not included them when I
added i.MX93 support.
Even this patch is marked as fix, I think it could be put in for-next tree.
Regards
Peng.
