From: <Claudiu.Beznea@microchip.com> To: <michael@walle.cc>, <Kavyasree.Kotagiri@microchip.com>, <Nicolas.Ferre@microchip.com> Cc: <arnd@arndb.de>, <olof@lixom.net>, <soc@kernel.org>, <linux-arm-kernel@lists.infradead.org>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <robh+dt@kernel.org>, <krzysztof.kozlowski@canonical.com>, <alexandre.belloni@bootlin.com> Subject: Re: [PATCH v1 2/6] ARM: dts: lan966x: add sgpio node Date: Fri, 4 Mar 2022 08:24:11 +0000 [thread overview] Message-ID: <c1462fbe-1619-7a13-4b3d-bb4ffcf24f1b@microchip.com> (raw) In-Reply-To: <20220303160323.3316317-3-michael@walle.cc> On 03.03.2022 18:03, Michael Walle wrote: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe > > Add the device tree node for the SGPIO IP block reused from the > SparX-5. Keep the node disabled by default. > > Signed-off-by: Michael Walle <michael@walle.cc> > --- > arch/arm/boot/dts/lan966x.dtsi | 26 ++++++++++++++++++++++++++ > 1 file changed, 26 insertions(+) > > diff --git a/arch/arm/boot/dts/lan966x.dtsi b/arch/arm/boot/dts/lan966x.dtsi > index 5e9cbc8cdcbc..a7d46a2ca058 100644 > --- a/arch/arm/boot/dts/lan966x.dtsi > +++ b/arch/arm/boot/dts/lan966x.dtsi > @@ -223,6 +223,32 @@ gpio: pinctrl@e2004064 { > #interrupt-cells = <2>; > }; > > + sgpio: gpio@e2004190 { > + #address-cells = <1>; > + #size-cells = <0>; > + compatible = "microchip,sparx5-sgpio"; > + clocks = <&sys_clk>; > + reg = <0xe2004190 0x118>; > + status = "disabled"; > + > + sgpio_in: gpio@0 { > + reg = <0>; > + compatible = "microchip,sparx5-sgpio-bank"; > + gpio-controller; > + #gpio-cells = <3>; > + interrupts = <GIC_SPI 18 IRQ_TYPE_LEVEL_HIGH>; > + interrupt-controller; > + #interrupt-cells = <3>; Can you preserve the order or properties for this node > + }; > + > + sgpio_out: gpio@1 { > + compatible = "microchip,sparx5-sgpio-bank"; > + reg = <1>; > + gpio-controller; > + #gpio-cells = <3>; and this node. It would be easier to follow it. As a note I see most of the nodes in this DT follows the order: - compatible - reg For consistency with the rest of the nodes it would be good to keep the same order here. > + }; > + }; > + > gic: interrupt-controller@e8c11000 { > compatible = "arm,gic-400", "arm,cortex-a7-gic"; > #interrupt-cells = <3>; > -- > 2.30.2 >
WARNING: multiple messages have this Message-ID (diff)
From: <Claudiu.Beznea@microchip.com> To: <michael@walle.cc>, <Kavyasree.Kotagiri@microchip.com>, <Nicolas.Ferre@microchip.com> Cc: <arnd@arndb.de>, <olof@lixom.net>, <soc@kernel.org>, <linux-arm-kernel@lists.infradead.org>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <robh+dt@kernel.org>, <krzysztof.kozlowski@canonical.com>, <alexandre.belloni@bootlin.com> Subject: Re: [PATCH v1 2/6] ARM: dts: lan966x: add sgpio node Date: Fri, 4 Mar 2022 08:24:11 +0000 [thread overview] Message-ID: <c1462fbe-1619-7a13-4b3d-bb4ffcf24f1b@microchip.com> (raw) In-Reply-To: <20220303160323.3316317-3-michael@walle.cc> On 03.03.2022 18:03, Michael Walle wrote: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe > > Add the device tree node for the SGPIO IP block reused from the > SparX-5. Keep the node disabled by default. > > Signed-off-by: Michael Walle <michael@walle.cc> > --- > arch/arm/boot/dts/lan966x.dtsi | 26 ++++++++++++++++++++++++++ > 1 file changed, 26 insertions(+) > > diff --git a/arch/arm/boot/dts/lan966x.dtsi b/arch/arm/boot/dts/lan966x.dtsi > index 5e9cbc8cdcbc..a7d46a2ca058 100644 > --- a/arch/arm/boot/dts/lan966x.dtsi > +++ b/arch/arm/boot/dts/lan966x.dtsi > @@ -223,6 +223,32 @@ gpio: pinctrl@e2004064 { > #interrupt-cells = <2>; > }; > > + sgpio: gpio@e2004190 { > + #address-cells = <1>; > + #size-cells = <0>; > + compatible = "microchip,sparx5-sgpio"; > + clocks = <&sys_clk>; > + reg = <0xe2004190 0x118>; > + status = "disabled"; > + > + sgpio_in: gpio@0 { > + reg = <0>; > + compatible = "microchip,sparx5-sgpio-bank"; > + gpio-controller; > + #gpio-cells = <3>; > + interrupts = <GIC_SPI 18 IRQ_TYPE_LEVEL_HIGH>; > + interrupt-controller; > + #interrupt-cells = <3>; Can you preserve the order or properties for this node > + }; > + > + sgpio_out: gpio@1 { > + compatible = "microchip,sparx5-sgpio-bank"; > + reg = <1>; > + gpio-controller; > + #gpio-cells = <3>; and this node. It would be easier to follow it. As a note I see most of the nodes in this DT follows the order: - compatible - reg For consistency with the rest of the nodes it would be good to keep the same order here. > + }; > + }; > + > gic: interrupt-controller@e8c11000 { > compatible = "arm,gic-400", "arm,cortex-a7-gic"; > #interrupt-cells = <3>; > -- > 2.30.2 > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-04 8:24 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-03 16:03 [PATCH v1 0/6] ARM: dts: lan966x: dtsi improvements and KSwitch D10 support Michael Walle 2022-03-03 16:03 ` Michael Walle 2022-03-03 16:03 ` [PATCH v1 1/6] ARM: dts: lan966x: swap dma channels for crypto node Michael Walle 2022-03-03 16:03 ` Michael Walle 2022-03-04 8:21 ` Claudiu.Beznea 2022-03-04 8:21 ` Claudiu.Beznea 2022-03-03 16:03 ` [PATCH v1 2/6] ARM: dts: lan966x: add sgpio node Michael Walle 2022-03-03 16:03 ` Michael Walle 2022-03-04 8:24 ` Claudiu.Beznea [this message] 2022-03-04 8:24 ` Claudiu.Beznea 2022-03-03 16:03 ` [PATCH v1 3/6] ARM: dts: lan966x: add all flexcom usart nodes Michael Walle 2022-03-03 16:03 ` Michael Walle 2022-03-04 8:30 ` Claudiu.Beznea 2022-03-04 8:30 ` Claudiu.Beznea 2022-03-04 11:01 ` Michael Walle 2022-03-04 11:01 ` Michael Walle 2022-03-07 11:53 ` Claudiu.Beznea 2022-03-07 11:53 ` Claudiu.Beznea 2022-03-07 12:04 ` Michael Walle 2022-03-07 12:04 ` Michael Walle 2022-03-18 12:17 ` Claudiu.Beznea 2022-03-18 12:17 ` Claudiu.Beznea 2022-03-22 21:39 ` Michael Walle 2022-03-22 21:39 ` Michael Walle 2022-03-24 16:32 ` Claudiu.Beznea 2022-03-24 16:32 ` Claudiu.Beznea 2022-03-03 16:03 ` [PATCH v1 4/6] ARM: dts: lan966x: add flexcom SPI nodes Michael Walle 2022-03-03 16:03 ` Michael Walle 2022-03-04 8:30 ` Claudiu.Beznea 2022-03-04 8:30 ` Claudiu.Beznea 2022-03-03 16:03 ` [PATCH v1 5/6] ARM: dts: lan966x: add flexcom I2C nodes Michael Walle 2022-03-03 16:03 ` Michael Walle 2022-03-03 16:03 ` [PATCH v1 6/6] ARM: dts: lan966x: add basic Kontron KSwitch D10 support Michael Walle 2022-03-03 16:03 ` Michael Walle 2022-03-04 8:31 ` Claudiu.Beznea 2022-03-04 8:31 ` Claudiu.Beznea 2022-03-04 11:15 ` Michael Walle 2022-03-04 11:15 ` Michael Walle 2022-03-07 12:07 ` Claudiu.Beznea 2022-03-07 12:07 ` Claudiu.Beznea 2022-03-07 12:17 ` Michael Walle 2022-03-07 12:17 ` Michael Walle 2022-03-18 12:26 ` Claudiu.Beznea 2022-03-18 12:26 ` Claudiu.Beznea 2022-03-23 8:06 ` Tudor.Ambarus 2022-03-23 8:06 ` Tudor.Ambarus
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=c1462fbe-1619-7a13-4b3d-bb4ffcf24f1b@microchip.com \ --to=claudiu.beznea@microchip.com \ --cc=Kavyasree.Kotagiri@microchip.com \ --cc=Nicolas.Ferre@microchip.com \ --cc=alexandre.belloni@bootlin.com \ --cc=arnd@arndb.de \ --cc=devicetree@vger.kernel.org \ --cc=krzysztof.kozlowski@canonical.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=michael@walle.cc \ --cc=olof@lixom.net \ --cc=robh+dt@kernel.org \ --cc=soc@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.