From: Andrew Lunn <andrew@lunn.ch>
To: Yijie Yang <quic_yijiyang@quicinc.com>
Cc: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Richard Cochran <richardcochran@gmail.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: qcs615-ride: Enable ethernet node
Date: Fri, 29 Nov 2024 16:15:36 +0100 [thread overview]
Message-ID: <e1c192ff-4fe9-4473-92ba-4c3a40ab99da@lunn.ch> (raw)
In-Reply-To: <2556b02c-f884-40c2-a0d4-0c87da6e5332@quicinc.com>
> > The usual setting here is 'rgmmii-id', which means something needs to
> > insert a 2ns delay on the clock lines. This is not always true, a very
> > small number of boards use extra long clock likes on the PCB to add
> > the needed 2ns delay.
> >
> > Now, if 'rgmii' does work, it means something else is broken
> > somewhere. I will let you find out what.
>
> The 'rgmii' does function correctly, but it does not necessarily mean that a
> time delay is required at the board level. The EPHY can also compensate for
> the time skew.
Basic definitions for phy-mode:
rgmii: Indicates the board provides the delays, normally via extra
long clock lines.
rgmii-id: The board does not provide the delay, the software need to
arrange that either the MAC or the PHY adds the delays.
We then have the values passed between the MAC and the PHY driver:
PHY_INTERFACE_MODE_RGMII: The PHY should not add delays
PHY_INTERFACE_MODE_RGMII_ID: The PHY should add delays.
A typical MAC/PHY combination, phy-mode is passed to the PHY, and the
PHY adds the delays, if needed.
This is why i said there are probably two bugs:
1) phy-mode rgmii should probably be rgmii-id
2) The PHY is adding delays when it should not be, because it is being
passed PHY_INTERFACE_MODE_RGMII not PHY_INTERFACE_MODE_RGMII_ID.
Andrew
prev parent reply other threads:[~2024-11-29 15:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 6:44 [PATCH v2 0/2] Enable ethernet on qcs615 Yijie Yang
2024-11-18 6:44 ` [PATCH v2 1/2] arm64: dts: qcom: qcs615: add ethernet node Yijie Yang
2024-11-18 6:44 ` [PATCH v2 2/2] arm64: dts: qcom: qcs615-ride: Enable " Yijie Yang
2024-11-19 1:27 ` Andrew Lunn
2024-11-19 10:09 ` Yijie Yang
2024-11-22 12:27 ` Konrad Dybcio
2024-11-22 13:19 ` Andrew Lunn
2024-11-27 6:17 ` Yijie Yang
2024-11-27 7:00 ` Yijie Yang
2024-11-29 15:29 ` Andrew Lunn
2024-12-09 2:11 ` Yijie Yang
2024-12-09 3:13 ` Andrew Lunn
2024-12-10 3:29 ` Yijie Yang
2024-12-10 4:09 ` Andrew Lunn
2024-12-16 6:56 ` Yijie Yang
2024-12-16 9:18 ` Andrew Lunn
2024-12-17 2:26 ` Yijie Yang
2024-12-17 10:18 ` Andrew Lunn
2024-12-18 7:25 ` Yijie Yang
2024-12-18 16:57 ` Andrew Lunn
2024-11-29 15:15 ` Andrew Lunn [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=e1c192ff-4fe9-4473-92ba-4c3a40ab99da@lunn.ch \
--to=andrew@lunn.ch \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=quic_yijiyang@quicinc.com \
--cc=richardcochran@gmail.com \
--cc=robh@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
all inboxes | Powered by JetHome®