From: Yijie Yang <quic_yijiyang@quicinc.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Richard Cochran <richardcochran@gmail.com>,
<netdev@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 2/4] net: stmmac: dwmac-qcom-ethqos: Mask PHY mode if configured with rgmii-id
Date: Wed, 22 Jan 2025 17:06:22 +0800 [thread overview]
Message-ID: <fad78436-8263-46af-b669-3bcd75f036a4@quicinc.com> (raw)
In-Reply-To: <Z4-Z0CKtiHWCC3TM@shell.armlinux.org.uk>
On 2025-01-21 20:57, Russell King (Oracle) wrote:
> On Tue, Jan 21, 2025 at 01:47:55PM +0100, Krzysztof Kozlowski wrote:
>> On 21/01/2025 08:54, Yijie Yang wrote:
>>> The Qualcomm board always chooses the MAC to provide the delay instead of
>>> the PHY, which is completely opposite to the suggestion of the Linux
>>> kernel.
>
> You still need to explain why it's preferable to match this in the mainline
> kernel. Does it not work when you use the phylib maintainers suggestion
> (if that is so, you need to state as much.)
Okay, I will include that explanation in the next version.
>
>> How does the Linux kernel suggest it?
>
> It's what phylib maintainers prefer, as documented in many emails from
> Andrew Lunn and in Documentation/networking/phy.rst:
>
> "Whenever possible, use the PHY side RGMII delay for these reasons:
>
> * PHY devices may offer sub-nanosecond granularity in how they allow a
> receiver/transmitter side delay (e.g: 0.5, 1.0, 1.5ns) to be specified. Such
> precision may be required to account for differences in PCB trace lengths
>
> * PHY devices are typically qualified for a large range of applications
> (industrial, medical, automotive...), and they provide a constant and
> reliable delay across temperature/pressure/voltage ranges
>
> * PHY device drivers in PHYLIB being reusable by nature, being able to
> configure correctly a specified delay enables more designs with similar delay
> requirements to be operated correctly
> "
>
>>> The usage of phy-mode in legacy DTS was also incorrect. Change the
>>> phy_mode passed from the DTS to the driver from PHY_INTERFACE_MODE_RGMII_ID
>>> to PHY_INTERFACE_MODE_RGMII to ensure correct operation and adherence to
>>> the definition.
>
> If the delays dependent on the phy-mode are going to be implemented at
> the MAC end, then changing the PHY mode indicated to phylink and phylib
> to PHY_INTERFACE_MODE_RGMII is the right thing to be doing. However,
> as mentioned in the documentation and by Andrew, this is discouraged.
>
Adding delay by the MAC side is generally discouraged, but the current
driver configuration sequence was designed to do so. We need to follow
this approach until we can rewrite it, correct?
--
Best Regards,
Yijie
next prev parent reply other threads:[~2025-01-22 9:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 7:54 [PATCH v3 0/4] Enable ethernet on qcs615 Yijie Yang
2025-01-21 7:54 ` [PATCH v3 1/4] dt-bindings: net: ethernet-controller: Correct the definition of phy-mode Yijie Yang
2025-01-21 13:08 ` Maxime Chevallier
2025-01-21 17:00 ` Andrew Lunn
2025-01-21 7:54 ` [PATCH v3 2/4] net: stmmac: dwmac-qcom-ethqos: Mask PHY mode if configured with rgmii-id Yijie Yang
2025-01-21 12:47 ` Krzysztof Kozlowski
2025-01-21 12:57 ` Russell King (Oracle)
2025-01-22 9:06 ` Yijie Yang [this message]
2025-01-22 8:56 ` Yijie Yang
2025-01-22 9:48 ` Krzysztof Kozlowski
2025-01-27 10:49 ` Konrad Dybcio
2025-02-10 3:09 ` Yijie Yang
2025-02-10 18:01 ` Konrad Dybcio
2025-02-10 21:28 ` Andrew Lunn
2025-02-11 2:14 ` Yijie Yang
2025-02-11 1:20 ` Yijie Yang
2025-01-21 13:17 ` Maxime Chevallier
2025-01-22 9:46 ` Yijie Yang
2025-01-21 17:10 ` Andrew Lunn
2025-01-22 10:04 ` Yijie Yang
2025-01-21 17:20 ` Andrew Lunn
2025-01-21 7:54 ` [PATCH v3 3/4] arm64: dts: qcom: qcs615: add ethernet node Yijie Yang
2025-02-01 15:48 ` Konrad Dybcio
2025-02-03 13:53 ` Konrad Dybcio
2025-01-21 7:54 ` [PATCH v3 4/4] arm64: dts: qcom: qcs615-ride: Enable " Yijie Yang
2025-02-03 13:52 ` Konrad Dybcio
2025-07-14 2:28 ` [PATCH v3 0/4] Enable ethernet on qcs615 Yijie Yang
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=fad78436-8263-46af-b669-3bcd75f036a4@quicinc.com \
--to=quic_yijiyang@quicinc.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andersson@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=vkoul@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