From: Marek Vasut <marek.vasut@mailbox.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-arm-kernel@lists.infradead.org,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
devicetree@vger.kernel.org, linux-phy@lists.infradead.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 01/11] dt-bindings: phy: renesas: usb3-phy: add r8a77990 support
Date: Sun, 18 Jan 2026 14:53:51 +0100 [thread overview]
Message-ID: <0bd00d89-fa5c-492d-aa79-74cd6f91dfb4@mailbox.org> (raw)
In-Reply-To: <CAMuHMdWZzL7nUCv6LnDaDhpMwfrnJp3ZYPAqQtDJ3BsZyH9k6g@mail.gmail.com>
On 1/14/26 11:22 AM, Geert Uytterhoeven wrote:
Hello Geert,
> According to Section 76.1.3.5 ("PHY Register Configuration"), the
> USB3.0 PHY register block is only present on R-Car H3, M3-W, M3-W+,
> and M3-N, but not on R-Car E3?
>
> Likewise, Figure 76.1 ("Clock Distribution [R-Car H3, H3-N, M3-W,
> M3-W+, M3-N]") does not cover R-Car E3. Unfortunately there is no
> separate picture for R-Car E3.
I replaced the PHY with usb-nop-xceiv in V2, it seems there is some PHY,
but it has no configuration registers.
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-01-18 13:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-01 20:35 [PATCH 00/11] Describe PCIe/USB3.0 clock generator on R-Car Gen3 Marek Vasut
2026-01-01 20:35 ` [PATCH 01/11] dt-bindings: phy: renesas: usb3-phy: add r8a77990 support Marek Vasut
2026-01-05 8:31 ` Krzysztof Kozlowski
2026-01-05 18:13 ` Marek Vasut
2026-01-14 10:22 ` Geert Uytterhoeven
2026-01-18 13:53 ` Marek Vasut [this message]
2026-01-01 20:35 ` [PATCH 02/11] arm64: dts: renesas: r8a77990: Add USB 3.0 PHY and USB3S0 clock nodes Marek Vasut
2026-01-01 20:35 ` [PATCH 03/11] arm64: dts: renesas: ebisu: Enable USB 3.0 PHY Marek Vasut
2026-01-01 20:35 ` [PATCH 04/11] arm64: dts: renesas: r8a77951: Describe PCIe root ports Marek Vasut
2026-01-01 20:35 ` [PATCH 05/11] arm64: dts: renesas: r8a77960: " Marek Vasut
2026-01-01 20:35 ` [PATCH 06/11] arm64: dts: renesas: r8a77961: " Marek Vasut
2026-01-01 20:35 ` [PATCH 07/11] arm64: dts: renesas: r8a77965: " Marek Vasut
2026-01-01 20:35 ` [PATCH 08/11] arm64: dts: renesas: r8a77990: Describe PCIe root port Marek Vasut
2026-01-01 20:35 ` [PATCH 09/11] arm64: dts: renesas: salvator-common: Describe PCIe/USB3.0 clock generator Marek Vasut
2026-01-01 20:35 ` [PATCH 10/11] arm64: dts: renesas: ulcb: ulcb-kf: " Marek Vasut
2026-01-01 20:35 ` [PATCH 11/11] arm64: dts: renesas: ebisu: " Marek Vasut
2026-01-13 14:19 ` [PATCH 00/11] Describe PCIe/USB3.0 clock generator on R-Car Gen3 Geert Uytterhoeven
2026-01-18 13:54 ` Marek Vasut
2026-01-19 15:58 ` Geert Uytterhoeven
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=0bd00d89-fa5c-492d-aa79-74cd6f91dfb4@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=vkoul@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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