From: Mihalcea Laurentiu <laurentiumihalcea111@gmail.com>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
Shengjiu Wang <shengjiu.wang@nxp.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Pengutronix Kernel Team <kernel@pengutronix.de>,
imx@lists.linux.dev
Subject: Re: [PATCH 3/5] bus: add driver for IMX AIPSTZ bridge
Date: Mon, 24 Feb 2025 12:07:40 +0200 [thread overview]
Message-ID: <a62ab860-5e0e-4ebc-af1f-6fb7ac621e2b@gmail.com> (raw)
In-Reply-To: <20250224075538.7oetjzllqqr2mlnt@pengutronix.de>
On 24.02.2025 09:55, Marco Felsch wrote:
> Hi Laurentiu,
>
> thanks for your patch.
>
> On 25-02-21, Laurentiu Mihalcea wrote:
>> From: Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com>
>>
>> The secure AHB to IP Slave (AIPSTZ) bus bridge provides access control
>> configurations meant to restrict access to certain peripherals.
>> Some of the configurations include:
>>
>> 1) Marking masters as trusted for R/W. Based on this
>> (and the configuration of the accessed peripheral), the bridge
>> may choose to abort the R/W transactions issued by certain
>> masters.
> Setting these bits requires very often that the core is running at EL3
> (e.g. secure-monitor) which is not the case for Linux. Can you please
> provide more information how Linux can set these bits?
>
> Regards,
> Marco
In this particular case, as far as I was able to understand, NS EL1 has enough
privilege to program this IP. This is why Linux can do it.
next prev parent reply other threads:[~2025-02-24 9:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 19:19 [PATCH 0/5] imx8mp: add support for the IMX AIPSTZ bridge Laurentiu Mihalcea
2025-02-21 19:19 ` [PATCH 1/5] dt-bindings: bus: add documentation " Laurentiu Mihalcea
2025-02-21 19:35 ` Frank Li
2025-02-23 11:50 ` Krzysztof Kozlowski
2025-02-21 19:19 ` [PATCH 2/5] dt-bindings: dsp: fsl,dsp: document 'access-controllers' property Laurentiu Mihalcea
2025-02-21 19:37 ` Frank Li
2025-02-24 17:35 ` Rob Herring (Arm)
2025-02-21 19:19 ` [PATCH 3/5] bus: add driver for IMX AIPSTZ bridge Laurentiu Mihalcea
2025-02-21 19:44 ` Frank Li
2025-02-24 7:55 ` Marco Felsch
2025-02-24 10:07 ` Mihalcea Laurentiu [this message]
2025-02-21 19:19 ` [PATCH 4/5] arm64: dts: imx8mp: convert 'aips5' to 'aipstz5' Laurentiu Mihalcea
2025-02-21 19:56 ` Frank Li
2025-02-25 14:14 ` Mihalcea Laurentiu
2025-02-25 16:16 ` Frank Li
2025-02-27 10:57 ` Marc Kleine-Budde
2025-02-27 16:45 ` Frank Li
2025-02-28 8:11 ` Marc Kleine-Budde
2025-02-28 10:19 ` Marco Felsch
2025-03-04 16:11 ` Laurentiu Mihalcea
2025-03-07 15:22 ` Marco Felsch
2025-03-10 20:24 ` Laurentiu Mihalcea
2025-03-11 12:05 ` Marco Felsch
2025-02-21 19:19 ` [PATCH 5/5] arm64: dts: imx8mp: make 'dsp' node depend on 'aips5' Laurentiu Mihalcea
2025-02-21 19:59 ` 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=a62ab860-5e0e-4ebc-af1f-6fb7ac621e2b@gmail.com \
--to=laurentiumihalcea111@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).