From: Yijie Yang <quic_yijiyang@quicinc.com>
To: Andrew Lunn <andrew@lunn.ch>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: 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 v4 2/2] arm64: dts: qcom: qcs8300-ride: enable ethernet0
Date: Fri, 6 Dec 2024 08:58:33 +0800 [thread overview]
Message-ID: <323eee41-70f2-48f5-8705-a0d30666c1d3@quicinc.com> (raw)
In-Reply-To: <4ecd23e2-0975-47cb-a1ea-ef0be25c93c6@lunn.ch>
On 2024-12-06 07:39, Andrew Lunn wrote:
>>>> +ðernet0 {
>>>> + phy-mode = "2500base-x";
>>>> + phy-handle = <&sgmii_phy0>;
>>>
>>> Nit picking, but your PHY clearly is not an SGMII PHY if it is using
>>> 2500base-x. I would call it just phy0, so avoiding using SGMII
>>> wrongly, which most vendors do use the name SGMII wrongly.
>>
>> Andrew, does that mean the rest of the patch looks ok?
>>
>> If so, I don't have any concerns either.
>
> Yes, this is a minor problem, the rest looks O.K, so once this is
> fixed it can be merged.
>
> Andrew
I will update the PHY name and pad the register in the next version.
--
Best Regards,
Yijie
prev parent reply other threads:[~2024-12-06 0:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 8:51 [PATCH v4 0/2] Enable ethernet for qcs8300 Yijie Yang
2024-11-23 8:51 ` [PATCH v4 1/2] arm64: dts: qcom: qcs8300: add the first 2.5G ethernet Yijie Yang
2024-11-23 19:36 ` Andrew Lunn
2024-11-25 3:22 ` Yijie Yang
2024-12-05 21:30 ` Konrad Dybcio
2024-11-23 8:51 ` [PATCH v4 2/2] arm64: dts: qcom: qcs8300-ride: enable ethernet0 Yijie Yang
2024-11-23 19:41 ` Andrew Lunn
2024-11-25 3:39 ` Yijie Yang
2024-12-05 21:29 ` Konrad Dybcio
2024-12-05 23:39 ` Andrew Lunn
2024-12-06 0:58 ` Yijie Yang [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=323eee41-70f2-48f5-8705-a0d30666c1d3@quicinc.com \
--to=quic_yijiyang@quicinc.com \
--cc=andersson@kernel.org \
--cc=andrew@lunn.ch \
--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=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®