From: Peng Fan <peng.fan@nxp.com>
To: Shawn Guo <shawnguo@kernel.org>, "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
dl-linux-imx <linux-imx@nxp.com>, Jacky Bai <ping.bai@nxp.com>,
Aisheng Dong <aisheng.dong@nxp.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 2/3] arm64: dts: imx8ulp: add scmi firmware node
Date: Wed, 8 Dec 2021 13:22:05 +0000 [thread overview]
Message-ID: <DU0PR04MB94179D73EA3E9585D76F2DAB886F9@DU0PR04MB9417.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20211208121000.GG4216@dragon>
Hi Shawn,
> Subject: Re: [PATCH 2/3] arm64: dts: imx8ulp: add scmi firmware node
>
> On Wed, Nov 17, 2021 at 11:27:39AM +0800, Peng Fan (OSS) wrote:
> > From: Peng Fan <peng.fan@nxp.com>
> >
> > i.MX8ULP use scmi firmware based power domain and sensor support.
> > So add the firmware node and the sram it uses.
> >
> > Signed-off-by: Peng Fan <peng.fan@nxp.com>
> > ---
> > arch/arm64/boot/dts/freescale/imx8ulp.dtsi | 35
> > ++++++++++++++++++++++
> > 1 file changed, 35 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/freescale/imx8ulp.dtsi
> > b/arch/arm64/boot/dts/freescale/imx8ulp.dtsi
> > index fb8714379026..d567ef93f8d8 100644
> > --- a/arch/arm64/boot/dts/freescale/imx8ulp.dtsi
> > +++ b/arch/arm64/boot/dts/freescale/imx8ulp.dtsi
> > @@ -6,6 +6,7 @@
> > #include <dt-bindings/clock/imx8ulp-clock.h>
> > #include <dt-bindings/gpio/gpio.h>
> > #include <dt-bindings/interrupt-controller/arm-gic.h>
> > +#include <dt-bindings/power/imx8ulp-power.h>
> >
> > #include "imx8ulp-pinfunc.h"
> >
> > @@ -102,6 +103,40 @@ sosc: clock-sosc {
> > #clock-cells = <0>;
> > };
> >
> > + sram@2201f000 {
> > + compatible = "mmio-sram";
> > + reg = <0x0 0x2201f000 0x0 0x1000>;
> > +
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + ranges = <0 0x0 0x2201f000 0x1000>;
> > +
> > + scmi_buf: scmi_buf@0 {
>
> Hyphen is more recommended than underscore for node name.
Just send out v2 to address this issue.
Or just
> follow the naming in arm,scmi.yaml example?
No need to follow its name there, it support many protocols
and need different shmem for performance and others.
Thanks,
Peng.
>
> Shawn
>
> > + compatible = "arm,scmi-shmem";
> > + reg = <0x0 0x400>;
> > + };
> > + };
> > +
> > + firmware {
> > + scmi {
> > + compatible = "arm,scmi-smc";
> > + arm,smc-id = <0xc20000fe>;
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > + shmem = <&scmi_buf>;
> > +
> > + scmi_devpd: protocol@11 {
> > + reg = <0x11>;
> > + #power-domain-cells = <1>;
> > + };
> > +
> > + scmi_sensor: protocol@15 {
> > + reg = <0x15>;
> > + #thermal-sensor-cells = <0>;
> > + };
> > + };
> > + };
> > +
> > soc@0 {
> > compatible = "simple-bus";
> > #address-cells = <1>;
> > --
> > 2.25.1
> >
next prev parent reply other threads:[~2021-12-08 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 3:27 [PATCH 0/3] add i.MX8ULP scmi power domain Peng Fan (OSS)
2021-11-17 3:27 ` [PATCH 1/3] dt-bindings: power: imx8ulp: add power domain header file Peng Fan (OSS)
2021-11-29 22:14 ` Rob Herring
2021-11-17 3:27 ` [PATCH 2/3] arm64: dts: imx8ulp: add scmi firmware node Peng Fan (OSS)
2021-12-08 12:10 ` Shawn Guo
2021-12-08 13:22 ` Peng Fan [this message]
2021-11-17 3:27 ` [PATCH 3/3] arm64: dts: imx8ulp: add power domain entry for usdhc Peng Fan (OSS)
2021-11-17 3:43 ` [PATCH 0/3] add i.MX8ULP scmi power domain Peng Fan
2021-12-07 2:34 ` Peng Fan
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=DU0PR04MB94179D73EA3E9585D76F2DAB886F9@DU0PR04MB9417.eurprd04.prod.outlook.com \
--to=peng.fan@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@oss.nxp.com \
--cc=ping.bai@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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;
as well as URLs for NNTP newsgroup(s).