Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@oss.nxp.com>
To: Zhiqiang Hou <Zhiqiang.Hou@nxp.com>
Cc: imx@lists.linux.dev, linux-remoteproc@vger.kernel.org,
	andersson@kernel.org, mathieu.poirier@linaro.org,
	Frank.Li@nxp.com, s.hauer@pengutronix.de, festevam@gmail.com
Subject: Re: [PATCHv2] remoteproc: imx_rproc: add missing DRAM range for i.MX93
Date: Mon, 18 May 2026 09:20:33 +0800	[thread overview]
Message-ID: <agppYVRcGLwflwCl@shlinux89> (raw)
In-Reply-To: <20260517080301.24774-1-Zhiqiang.Hou@nxp.com>

Hi Zhiqiang,

Thanks for your patch.

On Sun, May 17, 2026 at 04:03:01PM +0800, Zhiqiang Hou wrote:
>From: Hou Zhiqiang <Zhiqiang.Hou@nxp.com>
>
>The M33 DRAM view of 256MB ranges 0x[a,b]0000000 are mapped to
>0xa0000000 of A55 mapping view.

Let's add more details, as below:

The M33 DRAM address ranges 0xA0000000-0xAFFFFFFF(None Secure) and
0xB0000000-0xBFFFFFFF(Secure) are both mapped to 0xA0000000-0xAFFFFFFF
in the A55 address space.

These ranges are currently missing from the i.MX93 remoteproc address
translation table, which may lead to invalid address translation for
firmware accessing these regions.

Add the missing mappings to complete the DRAM coverage.

>

Add fix tag:
Fixes: 9222fabf0e39d ("remoteproc: imx_rproc: Support i.MX93")

Thanks
Peng.

  reply	other threads:[~2026-05-18  1:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-17  8:03 [PATCHv2] remoteproc: imx_rproc: add missing DRAM range for i.MX93 Zhiqiang Hou
2026-05-18  1:20 ` Peng Fan [this message]
2026-05-25  6:21   ` Z.Q. Hou

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=agppYVRcGLwflwCl@shlinux89 \
    --to=peng.fan@oss.nxp.com \
    --cc=Frank.Li@nxp.com \
    --cc=Zhiqiang.Hou@nxp.com \
    --cc=andersson@kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=s.hauer@pengutronix.de \
    /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