From: Laurentiu Mihalcea <laurentiumihalcea111@gmail.com>
To: 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>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] imx8mp: add support for the IMX AIPSTZ bridge
Date: Fri, 21 Feb 2025 14:19:04 -0500 [thread overview]
Message-ID: <20250221191909.31874-1-laurentiumihalcea111@gmail.com> (raw)
From: Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com>
The AIPSTZ bridge offers some security-related configurations which can
be used to restrict master access to certain peripherals on the bridge.
Normally, this could be done from a secure environment such as ATF before
Linux boots but the configuration of AIPSTZ5 is lost each time the power
domain is powered off and then powered on. Because of this, it has to be
configured each time the power domain is turned on and before any master
tries to access the peripherals (e.g: AP, CM7, DSP, on i.MX8MP).
The child-parent relationship between the bridge and its peripherals
should guarantee that the bridge is configured before the AP attempts
to access the IPs.
Other masters should use the 'access-controllers' property to enforce
a dependency between their device and the bridge device (see the DSP,
for example).
At the moment, we only want to apply a default, more relaxed
configuration, which is why the number of access controller cells
is 0.
The initial version of the series can be found at [1]. The new version
should provide better management of the device dependencies.
[1]: https://lore.kernel.org/linux-arm-kernel/20241119130726.2761726-1-daniel.baluta@nxp.com/
Laurentiu Mihalcea (5):
dt-bindings: bus: add documentation for the IMX AIPSTZ bridge
dt-bindings: dsp: fsl,dsp: document 'access-controllers' property
bus: add driver for IMX AIPSTZ bridge
arm64: dts: imx8mp: convert 'aips5' to 'aipstz5'
arm64: dts: imx8mp: make 'dsp' node depend on 'aips5'
.../bindings/bus/fsl,imx8mp-aipstz.yaml | 62 +++++++++++++
.../devicetree/bindings/dsp/fsl,dsp.yaml | 3 +
arch/arm64/boot/dts/freescale/imx8mp.dtsi | 9 +-
drivers/bus/Kconfig | 6 ++
drivers/bus/Makefile | 1 +
drivers/bus/imx-aipstz.c | 92 +++++++++++++++++++
6 files changed, 170 insertions(+), 3 deletions(-)
create mode 100644 Documentation/devicetree/bindings/bus/fsl,imx8mp-aipstz.yaml
create mode 100644 drivers/bus/imx-aipstz.c
--
2.34.1
next reply other threads:[~2025-02-21 19:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 19:19 Laurentiu Mihalcea [this message]
2025-02-21 19:19 ` [PATCH 1/5] dt-bindings: bus: add documentation for the IMX AIPSTZ bridge 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
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=20250221191909.31874-1-laurentiumihalcea111@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=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).