From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 3/4] dt-bindings: arm: fsl: add scu binding doc
Date: Wed, 20 Jun 2018 13:44:39 -0600 [thread overview]
Message-ID: <20180620194438.GA3494@rob-hp-laptop> (raw)
In-Reply-To: <1529239789-26849-4-git-send-email-aisheng.dong@nxp.com>
On Sun, Jun 17, 2018 at 08:49:48PM +0800, Dong Aisheng wrote:
> The System Controller Firmware (SCFW) is a low-level system function
> which runs on a dedicated Cortex-M core to provide power, clock, and
> resource management. It exists on some i.MX8 processors. e.g. i.MX8QM
> (QM, QP), and i.MX8QX (QXP, DX).
>
> Cc: Shawn Guo <shawnguo@kernel.org>
> Cc: Sascha Hauer <kernel@pengutronix.de>
> Cc: Fabio Estevam <fabio.estevam@nxp.com>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: devicetree at vger.kernel.org
> Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com>
> ---
> v1->v2:
> * remove status
> * changed to mu1
> ---
> .../devicetree/bindings/arm/freescale/fsl,scu.txt | 38 ++++++++++++++++++++++
> 1 file changed, 38 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,scu.txt
>
> diff --git a/Documentation/devicetree/bindings/arm/freescale/fsl,scu.txt b/Documentation/devicetree/bindings/arm/freescale/fsl,scu.txt
> new file mode 100644
> index 0000000..9b7c9fe
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/freescale/fsl,scu.txt
> @@ -0,0 +1,38 @@
> +NXP i.MX System Controller Firmware (SCFW)
> +--------------------------------------------------------------------
> +
> +The System Controller Firmware (SCFW) is a low-level system function
> +which runs on a dedicated Cortex-M core to provide power, clock, and
> +resource management. It exists on some i.MX8 processors. e.g. i.MX8QM
> +(QM, QP), and i.MX8QX (QXP, DX).
> +
> +The AP communicates with the SC using a multi-ported MU module found
> +in the LSIO subsystem. The current definition of this MU module provides
> +5 remote AP connections to the SC to support up to 5 execution environments
> +(TZ, HV, standard Linux, etc.). The SC side of this MU module interfaces
> +with the LSIO DSC IP bus. The SC firmware will communicate with this MU
> +using the MSI bus.
> +
> +System Controller Device Node:
> +=============================
> +
> +Required properties:
> +-------------------
> +- compatible: should be "fsl,imx8qxp-scu" or "fsl,imx8qm-scu"
> +- fsl,mu: a phandle to the Message Unit used by SCU. Should be
> + one of LSIO MU0~M4 for imx8qxp and imx8qm. Users need
> + to make sure not use the one which is conflict with
> + other execution environments. e.g. ATF.
Use the mailbox binding even if you don't use the mailbox subsystem.
> +
> +Examples:
> +--------
> +lsio_mu1: mu at 5d1c0000 {
> + compatible = "fsl,imx8qxp-mu";
> + reg = <0x0 0x5d1c0000 0x0 0x10000>;
> + interrupts = <GIC_SPI 176 IRQ_TYPE_LEVEL_HIGH>;
> +};
> +
> +scu {
> + compatible = "fsl,imx8qxp-scu";
> + fsl,mu = <&lsio_mu1>;
> +};
> --
> 2.7.4
>
next prev parent reply other threads:[~2018-06-20 19:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 12:49 [PATCH V2 0/4] soc: imx: add scu firmware api support Dong Aisheng
2018-06-17 12:49 ` [PATCH V2 1/4] soc: imx: add mu library functions support Dong Aisheng
2018-06-17 12:49 ` [PATCH V2 2/4] dt-bindings: arm: fsl: add mu binding doc Dong Aisheng
2018-06-20 19:43 ` Rob Herring
2018-06-21 7:46 ` Sascha Hauer
2018-06-21 17:11 ` A.s. Dong
2018-06-21 18:08 ` Oleksij Rempel
2018-06-22 3:31 ` A.s. Dong
2018-06-22 4:59 ` Oleksij Rempel
2018-06-22 5:59 ` A.s. Dong
2018-06-22 6:48 ` Oleksij Rempel
2018-06-22 8:16 ` A.s. Dong
2018-06-22 5:49 ` Sascha Hauer
2018-06-22 6:04 ` A.s. Dong
2018-06-17 12:49 ` [PATCH V2 3/4] dt-bindings: arm: fsl: add scu " Dong Aisheng
2018-06-20 19:44 ` Rob Herring [this message]
2018-06-21 3:38 ` A.s. Dong
2018-06-21 7:37 ` Sascha Hauer
2018-06-21 12:05 ` A.s. Dong
[not found] ` <1529239789-26849-5-git-send-email-aisheng.dong@nxp.com>
2018-06-18 8:58 ` [PATCH V2 4/4] soc: imx: add SC firmware IPC and APIs Leonard Crestez
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=20180620194438.GA3494@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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