From: Andrew Lunn <andrew@lunn.ch>
To: Sriranjani P <sriranjani.p@samsung.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
richardcochran@gmail.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org,
Pankaj Dubey <pankaj.dubey@samsung.com>,
Jayati Sahu <jayati.sahu@samsung.com>
Subject: Re: [PATCH 4/4] arm64: dts: fsd: Add Ethernet support for PERIC Block of FSD SoC
Date: Fri, 4 Nov 2022 16:34:36 +0100 [thread overview]
Message-ID: <Y2UxDH/LdTXmm4HC@lunn.ch> (raw)
In-Reply-To: <20221104120517.77980-5-sriranjani.p@samsung.com>
> +ðernet_1 {
> + status = "okay";
> +
> + fixed-link {
> + speed=<1000>;
> + full-duplex;
> + };
That is pretty unusual. Fixed link is generally used when connected to
an Ethernet switch. Is that the case here?
Andrew
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: Sriranjani P <sriranjani.p@samsung.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
richardcochran@gmail.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org,
Pankaj Dubey <pankaj.dubey@samsung.com>,
Jayati Sahu <jayati.sahu@samsung.com>
Subject: Re: [PATCH 4/4] arm64: dts: fsd: Add Ethernet support for PERIC Block of FSD SoC
Date: Fri, 4 Nov 2022 16:34:36 +0100 [thread overview]
Message-ID: <Y2UxDH/LdTXmm4HC@lunn.ch> (raw)
In-Reply-To: <20221104120517.77980-5-sriranjani.p@samsung.com>
> +ðernet_1 {
> + status = "okay";
> +
> + fixed-link {
> + speed=<1000>;
> + full-duplex;
> + };
That is pretty unusual. Fixed link is generally used when connected to
an Ethernet switch. Is that the case here?
Andrew
next prev parent reply other threads:[~2022-11-04 15:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20221104115833epcas5p31f68ef0a192e0d6678d2e2a0b3b89c4e@epcas5p3.samsung.com>
2022-11-04 12:05 ` [PATCH 0/4] net: stmmac: dwc-qos: Add FSD EQoS support Sriranjani P
2022-11-04 12:05 ` Sriranjani P
2022-11-04 12:05 ` [PATCH 1/4] dt-bindings: net: Add EQoS compatible for FSD SoC Sriranjani P
2022-11-04 12:05 ` Sriranjani P
2022-11-04 12:48 ` Krzysztof Kozlowski
2022-11-04 12:48 ` Krzysztof Kozlowski
2022-11-16 6:21 ` Sriranjani P
2022-11-16 6:21 ` Sriranjani P
2022-11-04 12:05 ` [PATCH 2/4] net: stmmac: dwc-qos: Add FSD EQoS support Sriranjani P
2022-11-04 12:05 ` Sriranjani P
2022-11-04 15:25 ` Andrew Lunn
2022-11-04 15:25 ` Andrew Lunn
2022-11-16 6:24 ` Sriranjani P
2022-11-16 6:24 ` Sriranjani P
2022-11-04 15:32 ` Andrew Lunn
2022-11-04 15:32 ` Andrew Lunn
2022-11-04 12:05 ` [PATCH 3/4] arm64: dts: fsd: Add Ethernet support for FSYS0 Block of FSD SoC Sriranjani P
2022-11-04 12:05 ` Sriranjani P
2022-11-04 12:45 ` Krzysztof Kozlowski
2022-11-04 12:45 ` Krzysztof Kozlowski
2022-11-04 12:47 ` Krzysztof Kozlowski
2022-11-04 12:47 ` Krzysztof Kozlowski
2022-11-16 6:22 ` Sriranjani P
2022-11-16 6:22 ` Sriranjani P
2022-11-04 12:05 ` [PATCH 4/4] arm64: dts: fsd: Add Ethernet support for PERIC " Sriranjani P
2022-11-04 12:05 ` Sriranjani P
2022-11-04 12:46 ` Krzysztof Kozlowski
2022-11-04 12:46 ` Krzysztof Kozlowski
2022-11-16 6:17 ` Sriranjani P
2022-11-16 6:17 ` Sriranjani P
2022-11-04 15:34 ` Andrew Lunn [this message]
2022-11-04 15:34 ` 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=Y2UxDH/LdTXmm4HC@lunn.ch \
--to=andrew@lunn.ch \
--cc=alexandre.torgue@foss.st.com \
--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-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pankaj.dubey@samsung.com \
--cc=peppe.cavallaro@st.com \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sriranjani.p@samsung.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 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.