From: Rob Herring <robh+dt@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Biju Das <biju.das.jz@bp.renesas.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Linux USB List <linux-usb@vger.kernel.org>,
devicetree@vger.kernel.org,
"open list:MEDIA DRIVERS FOR RENESAS - FCP"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: usb: ehci: Increase the number of PHYs
Date: Wed, 15 Jun 2022 11:24:00 -0600 [thread overview]
Message-ID: <CAL_JsqJbmdJd6+D9zog6NwF_LPO5QC_HsODg4FHLJOnMmPP-mg@mail.gmail.com> (raw)
In-Reply-To: <c5d19e2f9714f43effd90208798fc1936098078f.1655301043.git.geert+renesas@glider.be>
On Wed, Jun 15, 2022 at 7:53 AM Geert Uytterhoeven
<geert+renesas@glider.be> wrote:
>
> "make dtbs_check":
>
> arch/arm/boot/dts/r8a77470-iwg23s-sbc.dtb: usb@ee080100: phys: [[17, 0], [31]] is too long
> From schema: Documentation/devicetree/bindings/usb/generic-ehci.yaml
> arch/arm/boot/dts/r8a77470-iwg23s-sbc.dtb: usb@ee0c0100: phys: [[17, 1], [33], [21, 0]] is too long
> From schema: Documentation/devicetree/bindings/usb/generic-ehci.yaml
>
> Some USB EHCI controllers (e.g. on the Renesas RZ/G1C SoC) have multiple
> PHYs. Increase the maximum number of PHYs to 3, which is sufficient for
> now.
Maybe not so 'generic'. Why are there 3? I understand USB3 HCI having
2 for SS and HS. Is it for multiple ports? There's a thread about that
currently (Mediatek IIRC) and how to handle multiple phys.
Rob
next prev parent reply other threads:[~2022-06-15 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 13:53 [PATCH] dt-bindings: usb: ehci: Increase the number of PHYs Geert Uytterhoeven
2022-06-15 17:24 ` Rob Herring [this message]
2022-06-16 7:52 ` Geert Uytterhoeven
2022-06-17 7:13 ` Biju Das
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=CAL_JsqJbmdJd6+D9zog6NwF_LPO5QC_HsODg4FHLJOnMmPP-mg@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.