From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: renesas: white-hawk: ethernet: Define AVB1 and AVB2 PHY
Date: Tue, 25 Jun 2024 19:14:45 +0200 [thread overview]
Message-ID: <20240625171445.GF3655345@ragnatech.se> (raw)
In-Reply-To: <CAMuHMdVXGP_x1aoTqCfYo=axnEqGCncJ-HRckqzwNjX1+wxf9w@mail.gmail.com>
Hi Geert,
On 2024-06-25 16:54:38 +0200, Geert Uytterhoeven wrote:
> Hi Niklas,
>
> On Tue, Jun 25, 2024 at 3:31 PM Niklas Söderlund
> <niklas.soderlund+renesas@ragnatech.se> wrote:
> > Align with other Renesas SoCs and use the specific compatible for the
> > PHYs connected to AVB1 and AVB2, Marvell 88Q2110/QFN40. This allows
> > software to identify the PHY model at any time, regardless of the state
> > of the PHY reset line.
> >
> > Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
>
> Thanks for your patch!
>
> > --- a/arch/arm64/boot/dts/renesas/white-hawk-ethernet.dtsi
> > +++ b/arch/arm64/boot/dts/renesas/white-hawk-ethernet.dtsi
> > @@ -27,7 +27,8 @@ mdio {
> > reset-post-delay-us = <4000>;
> >
> > avb1_phy: ethernet-phy@0 {
> > - compatible = "ethernet-phy-ieee802.3-c45";
> > + compatible = "ethernet-phy-id002b.0980",
> > + "ethernet-phy-ieee802.3-c22";
> > reg = <0>;
> > interrupt-parent = <&gpio6>;
> > interrupts = <3 IRQ_TYPE_LEVEL_LOW>;
> > @@ -49,7 +50,8 @@ mdio {
> > reset-post-delay-us = <4000>;
> >
> > avb2_phy: ethernet-phy@0 {
> > - compatible = "ethernet-phy-ieee802.3-c45";
> > + compatible = "ethernet-phy-id002b.0980",
> > + "ethernet-phy-ieee802.3-c22";
> > reg = <0>;
> > interrupt-parent = <&gpio5>;
> > interrupts = <4 IRQ_TYPE_LEVEL_LOW>;
>
> Originally, I added explicit ethernet-phy-id* compatible values because
> Linux does not deassert the reset line before trying to read the PHY
> ID, hence failing. Have you checked if this is still the case after
> introducing the mdio subnode? I'd rather not add the explicit IDs,
> as board manufacturers may change the PHY revision or even the PHY
> model without notice.
>
> You can find my original test procedure, using kexec or bind/rebind, at
> https://lore.kernel.org/cover.1631174218.git.geert+renesas@glider.be/.
Indeed the mdio subnode reset do the trick without needing to hardcode
the PHY compatible. At lest for RAVB, for the RTSN we still need to
hardcode it as RTSN cant talk C45 when probing the PHY.
Anyhow this patch can be dropped.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
--
Kind Regards,
Niklas Söderlund
prev parent reply other threads:[~2024-06-25 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 13:30 [PATCH] arm64: dts: renesas: white-hawk: ethernet: Define AVB1 and AVB2 PHY Niklas Söderlund
2024-06-25 14:54 ` Geert Uytterhoeven
2024-06-25 17:14 ` Niklas Söderlund [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=20240625171445.GF3655345@ragnatech.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).