[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <86970fc1-c4c7-4a52-91e4-f9f93be5990b@gmail.com>
Date: Fri, 23 Jan 2026 02:08:28 -0800
From: Laurentiu Mihalcea <laurentiumihalcea111@...il.com>
To: Shengjiu Wang <shengjiu.wang@....com>, shawnguo@...nel.org,
s.hauer@...gutronix.de, kernel@...gutronix.de, festevam@...il.com,
laurentiu.mihalcea@....com, daniel.baluta@....com, imx@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
shengjiu.wang@...il.com
Subject: Re: [PATCH] bus: imx-aipstz: set default value for opacr registers
On 1/23/2026 12:48 AM, Shengjiu Wang wrote:
> The sdma script app_2_mcu needs the permission to access the peripheral
> devices, so need to clear the Supervisor Protect bit of SPBA2, otherwise
> the sdma script can't work.
>
> As the imx-aipstz is a common driver for all apis bus, so set default
> value for all opacr registers, that the peripheral does not require
> supervisor privilege level for accesses.
>
> Signed-off-by: Shengjiu Wang <shengjiu.wang@....com>
> ---
> drivers/bus/imx-aipstz.c | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
Hey SJ,
I'd be interested in explaining the situation a bit better in the commit message.
The 2 most important pieces of information are, in my opinion:
1) SDMA2 transactions are set to user-mode in your particular case.
2) Your script doesn't use the peripheral interface (connected directly
to SPBA), which is why the SDMA2-issued transactions are subjected to
AIPSTZ5's security-related checks.
Of course, please feel free to correct me if I got something wrong.
Thanks,
Laurentiu
Powered by blists - more mailing lists