[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANLsYky+FPNi82kDwgJBzdoxS5=SBXBqiRRFNCvt4ihUpJS+9w@mail.gmail.com>
Date: Wed, 2 Nov 2022 11:40:23 -0600
From: Mathieu Poirier <mathieu.poirier@...aro.org>
To: "Peng Fan (OSS)" <peng.fan@....nxp.com>
Cc: andersson@...nel.org, shawnguo@...nel.org, s.hauer@...gutronix.de,
kernel@...gutronix.de, festevam@...il.com, linux-imx@....com,
linux-remoteproc@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Peng Fan <peng.fan@....com>
Subject: Re: [PATCH] remoteproc: imx_rproc: correct i.MX93 DRAM mapping
On Wed, 2 Nov 2022 at 05:12, Peng Fan (OSS) <peng.fan@....nxp.com> wrote:
>
> From: Peng Fan <peng.fan@....com>
>
> According to updated reference mannual, the M33 DRAM view of
> 0x[C,D]0000000 maps to A55 0xC0000000, so correct it.
>
> Fixes: 9222fabf0e39 ("remoteproc: imx_rproc: Support i.MX93")
> Signed-off-by: Peng Fan <peng.fan@....com>
> ---
> drivers/remoteproc/imx_rproc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/remoteproc/imx_rproc.c b/drivers/remoteproc/imx_rproc.c
> index 2c471e46f4ca..9fc978e0393c 100644
> --- a/drivers/remoteproc/imx_rproc.c
> +++ b/drivers/remoteproc/imx_rproc.c
> @@ -134,8 +134,8 @@ static const struct imx_rproc_att imx_rproc_att_imx93[] = {
> { 0x80000000, 0x80000000, 0x10000000, 0 },
> { 0x90000000, 0x80000000, 0x10000000, 0 },
>
> - { 0xC0000000, 0xa0000000, 0x10000000, 0 },
> - { 0xD0000000, 0xa0000000, 0x10000000, 0 },
> + { 0xC0000000, 0xC0000000, 0x10000000, 0 },
> + { 0xD0000000, 0xC0000000, 0x10000000, 0 },
But how did this work before? Were some SoC released with the old mapping?
> };
>
> static const struct imx_rproc_att imx_rproc_att_imx8qm[] = {
> --
> 2.37.1
>
Powered by blists - more mailing lists