From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: renesas: white-hawk: ethernet: Describe avb1 and avb2
Date: Wed, 20 Mar 2024 15:23:21 +0100 [thread overview]
Message-ID: <CAMuHMdVTps9L8AY0AgA5YCdxC83_A-FuLXP9X4gy2fNfgiRx8w@mail.gmail.com> (raw)
In-Reply-To: <20240309155608.1312784-1-niklas.soderlund+renesas@ragnatech.se>
Hi Niklas,
Thanks for your patch!
On Sat, Mar 9, 2024 at 4:56 PM Niklas Söderlund
<niklas.soderlund+renesas@ragnatech.se> wrote:
> Describe the two Marvel 88Q2110/QFN40 PHYs available on the R-Car V4H
Marvell (apparently the schematics author spent too much time with
Spiderman and friends ;-)
> White Hawk RAVB/Ethernet(1000Base-T1) sub-board. The two PHYs are wired
> up on the board by default, there is no need to move any resistors which
> are needed to access other PHYs available on this sub-board.
>
> Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> --- a/arch/arm64/boot/dts/renesas/r8a779g0-white-hawk-ethernet.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a779g0-white-hawk-ethernet.dtsi
That is arch/arm64/boot/dts/renesas/white-hawk-ethernet.dtsi, as of
commit 1b940d036d5a2235 ("arm64: dts: renesas: white-hawk: Drop SoC
parts from sub boards").
> @@ -6,6 +6,50 @@
> * Copyright (C) 2022 Glider bv
> */
>
> +&avb1 {
> + pinctrl-0 = <&avb1_pins>;
> + pinctrl-names = "default";
> + phy-handle = <&phy1>;
> + status = "okay";
> +
> + mdio {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + reset-gpios = <&gpio6 1 GPIO_ACTIVE_LOW>;
> + reset-post-delay-us = <4000>;
> +
> + phy1: ethernet-phy@0 {
Given the large number of PHYs on the White-Hawk board stack, I think
a more specific name would be more suitable, e.g. "avb1-phy"?
Same for AVB2 below.
> + compatible = "ethernet-phy-ieee802.3-c45";
> + reg = <0>;
> + interrupt-parent = <&gpio6>;
> + interrupts = <3 IRQ_TYPE_LEVEL_LOW>;
> + };
> + };
> +};
Probably we also want "ethernet1" and "ethernet2" aliases, so U-Boot
can fill in the corresponding MAC addresses?
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
next prev parent reply other threads:[~2024-03-20 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 15:56 [PATCH v2] arm64: dts: renesas: white-hawk: ethernet: Describe avb1 and avb2 Niklas Söderlund
2024-03-20 14:23 ` Geert Uytterhoeven [this message]
2024-03-26 15:54 ` Geert Uytterhoeven
2024-03-26 17:50 ` Niklas Söderlund
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=CAMuHMdVTps9L8AY0AgA5YCdxC83_A-FuLXP9X4gy2fNfgiRx8w@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=robh+dt@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).