From: "Swathi K S" <swathi.ks@samsung.com>
To: "'Andrew Lunn'" <andrew@lunn.ch>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<richardcochran@gmail.com>, <alexandre.torgue@foss.st.com>,
<joabreu@synopsys.com>, <mcoquelin.stm32@gmail.com>,
<alim.akhtar@samsung.com>, <linux-fsd@tesla.com>,
<pankaj.dubey@samsung.com>, <ravi.patel@samsung.com>,
<netdev@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-samsung-soc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
"'Jayati Sahu'" <jayati.sahu@samsung.com>,
"'Siddharth Vadapalli'" <s-vadapalli@ti.com>
Subject: RE: [PATCH v3 3/4] arm64: dts: fsd: Add Ethernet support for FSYS0 Block of FSD SoC
Date: Mon, 29 Jul 2024 14:19:29 +0530 [thread overview]
Message-ID: <003101dae194$3bd4c460$b37e4d20$@samsung.com> (raw)
In-Reply-To: <14887409-4c5e-4589-b188-564df42924c8@lunn.ch>
> -----Original Message-----
> From: Andrew Lunn <andrew@lunn.ch>
> Sent: 06 June 2024 18:53
> To: Swathi K S <swathi.ks@samsung.com>
> Cc: davem@davemloft.net; edumazet@google.com; kuba@kernel.org;
> pabeni@redhat.com; robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org;
> conor+dt@kernel.org; richardcochran@gmail.com;
> alexandre.torgue@foss.st.com; joabreu@synopsys.com;
> mcoquelin.stm32@gmail.com; alim.akhtar@samsung.com; linux-
> fsd@tesla.com; pankaj.dubey@samsung.com; ravi.patel@samsung.com;
> netdev@vger.kernel.org; devicetree@vger.kernel.org; linux-
> kernel@vger.kernel.org; linux-samsung-soc@vger.kernel.org; linux-arm-
> kernel@lists.infradead.org; 'Jayati Sahu' <jayati.sahu@samsung.com>;
Siddharth
> Vadapalli <s-vadapalli@ti.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
next prev parent reply other threads:[~2024-07-29 8:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230814112600epcas5p49fe29a3ef85e2b0158f5ee3426652fc8@epcas5p4.samsung.com>
2023-08-14 11:25 ` [PATCH v3 0/4] net: stmmac: dwc-qos: Add FSD EQoS support Sriranjani P
2023-08-14 11:25 ` [PATCH v3 1/4] dt-bindings: net: Add FSD EQoS device tree bindings Sriranjani P
2023-08-14 13:33 ` Rob Herring
2023-08-16 5:36 ` Sriranjani P
2023-08-16 5:40 ` Krzysztof Kozlowski
2023-08-17 14:54 ` Rob Herring
2023-08-14 19:39 ` Krzysztof Kozlowski
2023-08-16 5:58 ` Sriranjani P
2023-08-16 6:18 ` Krzysztof Kozlowski
2024-06-06 9:14 ` Swathi K S
2023-08-14 20:39 ` Andrew Lunn
2024-06-06 9:14 ` Swathi K S
2024-06-06 13:25 ` Andrew Lunn
2024-07-29 8:47 ` Swathi K S
2023-08-14 11:25 ` [PATCH v3 2/4] net: stmmac: dwc-qos: Add FSD EQoS support Sriranjani P
2023-08-14 19:50 ` Krzysztof Kozlowski
2023-08-16 6:38 ` Sriranjani P
2023-08-18 9:27 ` Krzysztof Kozlowski
2024-06-06 9:14 ` Swathi K S
2024-06-06 12:16 ` Krzysztof Kozlowski
2023-08-14 20:47 ` Andrew Lunn
2024-06-06 9:16 ` Swathi K S
2023-08-14 11:25 ` [PATCH v3 3/4] arm64: dts: fsd: Add Ethernet support for FSYS0 Block of FSD SoC Sriranjani P
2023-08-14 19:40 ` Krzysztof Kozlowski
2023-08-14 19:56 ` Krzysztof Kozlowski
2023-08-16 6:40 ` Sriranjani P
2023-08-14 20:50 ` Andrew Lunn
2024-06-06 9:14 ` Swathi K S
2024-06-06 13:22 ` Andrew Lunn
2024-07-29 8:49 ` Swathi K S [this message]
2023-08-14 20:51 ` Andrew Lunn
2023-08-14 11:25 ` [PATCH v3 4/4] arm64: dts: fsd: Add Ethernet support for PERIC " Sriranjani P
2023-08-14 19:41 ` Krzysztof Kozlowski
2023-08-14 19:41 ` Krzysztof Kozlowski
2023-08-16 6:26 ` Sriranjani P
2023-08-14 20:53 ` Andrew Lunn
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='003101dae194$3bd4c460$b37e4d20$@samsung.com' \
--to=swathi.ks@samsung.com \
--cc=alexandre.torgue@foss.st.com \
--cc=alim.akhtar@samsung.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jayati.sahu@samsung.com \
--cc=joabreu@synopsys.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsd@tesla.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pankaj.dubey@samsung.com \
--cc=ravi.patel@samsung.com \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=s-vadapalli@ti.com \
/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