From: Horatiu Vultur - M31836 <Horatiu.Vultur@microchip.com>
To: Claudiu Beznea - M18063 <Claudiu.Beznea@microchip.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
Nicolas Ferre - M43238 <Nicolas.Ferre@microchip.com>,
UNGLinuxDriver <UNGLinuxDriver@microchip.com>,
"maxime.chevallier@bootlin.com" <maxime.chevallier@bootlin.com>
Subject: Re: [PATCH 3/3] ARM: dts: lan966x: Enable network driver on pcb8291
Date: Tue, 19 Jul 2022 22:03:45 +0200 [thread overview]
Message-ID: <20220719200345.pr3gkljjae52vnqw@soft-dev3-1.localhost> (raw)
In-Reply-To: <cfbe269b-998d-018a-2de9-824ef309301e@microchip.com>
The 07/19/2022 07:58, Claudiu Beznea - M18063 wrote:
> On 19.07.2022 00:29, Horatiu Vultur wrote:
> > The pcb8291 has 2 ports that are connected to the internal ports of the
> > switch. Enable them in DT.
> >
> > Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> > ---
> > arch/arm/boot/dts/lan966x-pcb8291.dts | 35 +++++++++++++++++++++++++++
> > 1 file changed, 35 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/lan966x-pcb8291.dts b/arch/arm/boot/dts/lan966x-pcb8291.dts
> > index 2cb532aa33f0..d890e6fcdbae 100644
> > --- a/arch/arm/boot/dts/lan966x-pcb8291.dts
> > +++ b/arch/arm/boot/dts/lan966x-pcb8291.dts
> > @@ -4,6 +4,7 @@
> > */
> > /dts-v1/;
> > #include "lan966x.dtsi"
> > +#include "dt-bindings/phy/phy-lan966x-serdes.h"
> >
> > / {
> > model = "Microchip EVB - LAN9662";
> > @@ -32,6 +33,40 @@ fc3_b_pins: fc3-b-pins {
> > };
> > };
> >
> > +&mdio1 {
> > + status = "okay";
> > +};
> > +
> > +&phy0 {
> > + status = "okay";
> > +};
> > +
> > +&phy1 {
> > + status = "okay";
> > +};
> > +
> > +&switch {
> > + status = "okay";
> > +};
> > +
> > +&serdes {
> > + status = "okay";
> > +};
> > +
> > +&port0 {
> > + status = "okay";
> > + phy-handle = <&phy0>;
> > + phy-mode = "gmii";
> > + phys = <&serdes 0 CU(0)>;
> > +};
> > +
> > +&port1 {
> > + status = "okay";
> > + phy-handle = <&phy1>;
> > + phy-mode = "gmii";
> > + phys = <&serdes 1 CU(1)>;
> > +};
> > +
>
> Although gpio node is not places where it should be we tend to keep all the
> nodes sorted alphabetically. Could you place follow this rule for these new
> nodes?
Yes, I will update in the next version.
>
> Thank you,
> Claudiu Beznea
>
> > &flx3 {
> > atmel,flexcom-mode = <ATMEL_FLEXCOM_MODE_USART>;
> > status = "okay";
>
--
/Horatiu
prev parent reply other threads:[~2022-07-19 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 21:29 [PATCH 0/3] ARM: dts: lan966x: Extend pcb8291 Horatiu Vultur
2022-07-18 21:29 ` [PATCH 1/3] ARM: dts: lan966x: Add gpio-restart Horatiu Vultur
2022-07-19 7:52 ` Claudiu.Beznea
2022-07-19 20:02 ` Horatiu Vultur - M31836
2022-07-18 21:29 ` [PATCH 2/3] ARM: dts: lan966x: Disable can0 on pcb8291 Horatiu Vultur
2022-07-19 7:55 ` Claudiu.Beznea
2022-07-19 20:03 ` Horatiu Vultur - M31836
2022-07-18 21:29 ` [PATCH 3/3] ARM: dts: lan966x: Enable network driver " Horatiu Vultur
2022-07-19 7:58 ` Claudiu.Beznea
2022-07-19 20:03 ` Horatiu Vultur - M31836 [this message]
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=20220719200345.pr3gkljjae52vnqw@soft-dev3-1.localhost \
--to=horatiu.vultur@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=robh+dt@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).