From: Frank Li <Frank.li@nxp.com>
To: Shengjiu Wang <shengjiu.wang@nxp.com>
Cc: 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 v2] bus: imx-aipstz: set default value for opacr registers
Date: Mon, 26 Jan 2026 11:41:47 -0500 [thread overview]
Message-ID: <aXeZS/bKBb9QE+Uq@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20260126091156.951052-1-shengjiu.wang@nxp.com>
On Mon, Jan 26, 2026 at 05:11:56PM +0800, Shengjiu Wang wrote:
> The sdma script app_2_mcu needs the permission to access the peripheral
> devices:
>
> 1) SDMA2 transactions are set to user-mode in this particular case.
> 2) This type of script doesn't use the peripheral interface (connected
> directly to SPBA), but it uses the peripheral DMA interface, then the
> SDMA2-issued transactions are subjected to AIPSTZ5's security-related
> checks.
>
> 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 aips bus,
> so set default value (zero) for all opacr registers.
>
> Signed-off-by: Shengjiu Wang <shengjiu.wang@nxp.com>
> ---
Reviewed-by: Frank Li <Frank.Li@nxp.com>
> Changes in v2:
> - refine the commit message
> - remove the unneeded initialize value
>
> drivers/bus/imx-aipstz.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/drivers/bus/imx-aipstz.c b/drivers/bus/imx-aipstz.c
> index 5fdf377f5d06..83371e5b35a2 100644
> --- a/drivers/bus/imx-aipstz.c
> +++ b/drivers/bus/imx-aipstz.c
> @@ -11,9 +11,19 @@
> #include <linux/regmap.h>
>
> #define IMX_AIPSTZ_MPR0 0x0
> +#define IMX_AIPSTZ_OPACR0 0x40
> +#define IMX_AIPSTZ_OPACR1 0x44
> +#define IMX_AIPSTZ_OPACR2 0x48
> +#define IMX_AIPSTZ_OPACR3 0x4c
> +#define IMX_AIPSTZ_OPACR4 0x50
>
> struct imx_aipstz_config {
> u32 mpr0;
> + u32 opacr0;
> + u32 opacr1;
> + u32 opacr2;
> + u32 opacr3;
> + u32 opacr4;
> };
>
> struct imx_aipstz_data {
> @@ -24,6 +34,11 @@ struct imx_aipstz_data {
> static void imx_aipstz_apply_default(struct imx_aipstz_data *data)
> {
> writel(data->default_cfg->mpr0, data->base + IMX_AIPSTZ_MPR0);
> + writel(data->default_cfg->opacr0, data->base + IMX_AIPSTZ_OPACR0);
> + writel(data->default_cfg->opacr1, data->base + IMX_AIPSTZ_OPACR1);
> + writel(data->default_cfg->opacr2, data->base + IMX_AIPSTZ_OPACR2);
> + writel(data->default_cfg->opacr3, data->base + IMX_AIPSTZ_OPACR3);
> + writel(data->default_cfg->opacr4, data->base + IMX_AIPSTZ_OPACR4);
> }
>
> static const struct of_device_id imx_aipstz_match_table[] = {
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-01-26 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 9:11 Shengjiu Wang
2026-01-26 14:47 ` Daniel Baluta
2026-01-26 15:22 ` Laurentiu Mihalcea
2026-01-26 16:41 ` Frank Li [this message]
2026-02-24 19:36 ` Frank Li
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=aXeZS/bKBb9QE+Uq@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.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®