From: Laurentiu Mihalcea <laurentiumihalcea111@gmail.com>
To: Shengjiu Wang <shengjiu.wang@nxp.com>,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com,
laurentiu.mihalcea@nxp.com, daniel.baluta@nxp.com,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, shengjiu.wang@gmail.com
Subject: Re: [PATCH] bus: imx-aipstz: set default value for opacr registers
Date: Fri, 23 Jan 2026 02:08:28 -0800 [thread overview]
Message-ID: <86970fc1-c4c7-4a52-91e4-f9f93be5990b@gmail.com> (raw)
In-Reply-To: <20260123084844.4051570-1-shengjiu.wang@nxp.com>
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@nxp.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
next prev parent reply other threads:[~2026-01-23 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 8:48 Shengjiu Wang
2026-01-23 9:14 ` Daniel Baluta
2026-01-23 9:59 ` Shengjiu Wang
2026-01-23 10:08 ` Laurentiu Mihalcea [this message]
2026-01-26 2:40 ` Shengjiu Wang
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=86970fc1-c4c7-4a52-91e4-f9f93be5990b@gmail.com \
--to=laurentiumihalcea111@gmail.com \
--cc=daniel.baluta@nxp.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=laurentiu.mihalcea@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shengjiu.wang@gmail.com \
--cc=shengjiu.wang@nxp.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
all inboxes | Powered by JetHome®