[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <003101dae194$3bd4c460$b37e4d20$@samsung.com>
Date: Mon, 29 Jul 2024 14:19:29 +0530
From: "Swathi K S" <swathi.ks@...sung.com>
To: "'Andrew Lunn'" <andrew@...n.ch>
Cc: <davem@...emloft.net>, <edumazet@...gle.com>, <kuba@...nel.org>,
<pabeni@...hat.com>, <robh+dt@...nel.org>,
<krzysztof.kozlowski+dt@...aro.org>, <conor+dt@...nel.org>,
<richardcochran@...il.com>, <alexandre.torgue@...s.st.com>,
<joabreu@...opsys.com>, <mcoquelin.stm32@...il.com>,
<alim.akhtar@...sung.com>, <linux-fsd@...la.com>,
<pankaj.dubey@...sung.com>, <ravi.patel@...sung.com>,
<netdev@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-samsung-soc@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, "'Jayati Sahu'"
<jayati.sahu@...sung.com>, "'Siddharth Vadapalli'" <s-vadapalli@...com>
Subject: RE: [PATCH v3 3/4] arm64: dts: fsd: Add Ethernet support for FSYS0
Block of FSD SoC
> -----Original Message-----
> From: Andrew Lunn <andrew@...n.ch>
> Sent: 06 June 2024 18:53
> To: Swathi K S <swathi.ks@...sung.com>
> Cc: davem@...emloft.net; edumazet@...gle.com; kuba@...nel.org;
> pabeni@...hat.com; robh+dt@...nel.org; krzysztof.kozlowski+dt@...aro.org;
> conor+dt@...nel.org; richardcochran@...il.com;
> alexandre.torgue@...s.st.com; joabreu@...opsys.com;
> mcoquelin.stm32@...il.com; alim.akhtar@...sung.com; linux-
> fsd@...la.com; pankaj.dubey@...sung.com; ravi.patel@...sung.com;
> netdev@...r.kernel.org; devicetree@...r.kernel.org; linux-
> kernel@...r.kernel.org; linux-samsung-soc@...r.kernel.org; linux-arm-
> kernel@...ts.infradead.org; 'Jayati Sahu' <jayati.sahu@...sung.com>;
Siddharth
> Vadapalli <s-vadapalli@...com>
> Subject: Re: [PATCH v3 3/4] arm64: dts: fsd: Add Ethernet support for
FSYS0
> Block of FSD SoC
>
> > > > +ðernet_0 {
> > > > + status = "okay";
> > > > +
> > > > + fixed-link {
> > > > + speed = <1000>;
> > > > + full-duplex;
> > > > + };
> > > > +};
> > >
> > > A fixed link on its own is pretty unusual. Normally it is combined
> > > with an Ethernet switch. What is the link peer here?
> >
> > It is a direct connection to the Ethernet switch managed by an
> > external management unit.
>
> Ah, interesting. This is the third example of this in about a month. Take
a look at
> the Realtek and TI work in this area.
>
> So, i will ask the same questions i put to Realtek and TI. Does Linux know
about
> the switch in any way? Can it manage the switch, other than SNMP, HTTP
from
> user space? Does it know about the state of the ports, etc?
>
> If you say this is just a colocated management switch, which Linux is not
> managing in any way, that is O.K. If you have Linux involved in some way,
please
> join the discussion with TI about adding a new model for semi-autonomous
> switches.
Thanks for letting us know about the ongoing discussion.
But in this case, the switch is not managed by Linux.
>
> Andrew
Thanks,
Swathi
Powered by blists - more mailing lists