From: Adam Ford <aford173@gmail.com>
To: linux-usb@vger.kernel.org
Cc: aford@beaconembedded.com, Adam Ford <aford173@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: [PATCH 1/3] dt-bindings: usb: renesas,usbhs: Support external ref clock
Date: Wed, 30 Jun 2021 12:30:40 -0500 [thread overview]
Message-ID: <20210630173042.186394-1-aford173@gmail.com> (raw)
The usbhs driver expects a fixed external reference clock, but it
could be sourced from a programmable clock instead of a fixed clock.
Add support for an optional 4th reference clock.
Signed-off-by: Adam Ford <aford173@gmail.com>
diff --git a/Documentation/devicetree/bindings/usb/renesas,usbhs.yaml b/Documentation/devicetree/bindings/usb/renesas,usbhs.yaml
index e67223d90bb7..2372d8c42979 100644
--- a/Documentation/devicetree/bindings/usb/renesas,usbhs.yaml
+++ b/Documentation/devicetree/bindings/usb/renesas,usbhs.yaml
@@ -53,11 +53,12 @@ properties:
clocks:
minItems: 1
- maxItems: 3
+ maxItems: 4
items:
- description: USB 2.0 host
- description: USB 2.0 peripheral
- description: USB 2.0 clock selector
+ - description: Optional external reference clock
interrupts:
maxItems: 1
--
2.25.1
next reply other threads:[~2021-06-30 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 17:30 Adam Ford [this message]
2021-06-30 17:30 ` [PATCH 2/3] usb: renesas_usbhs: Enable support for more than two clks Adam Ford
2021-07-01 9:07 ` Geert Uytterhoeven
2021-07-01 11:34 ` Yoshihiro Shimoda
2021-08-27 18:57 ` Adam Ford
2021-08-30 5:32 ` Yoshihiro Shimoda
2021-06-30 17:30 ` [PATCH 3/3] arm64: dts: renesas: beacon: Fix HSUSB ref clock references Adam Ford
2021-07-14 21:27 ` [PATCH 1/3] dt-bindings: usb: renesas,usbhs: Support external ref clock Rob Herring
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=20210630173042.186394-1-aford173@gmail.com \
--to=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).