From: Rob Herring <robh@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCHv1 1/3] dt-bindings: usb: Add RK3588 OHCI
Date: Tue, 11 Apr 2023 08:12:37 -0500 [thread overview]
Message-ID: <20230411131237.GA2837061-robh@kernel.org> (raw)
In-Reply-To: <20230406135552.23980-2-sebastian.reichel@collabora.com>
On Thu, Apr 06, 2023 at 03:55:50PM +0200, Sebastian Reichel wrote:
> Add compatible for RK3588 OHCI. As far as I know it's fully
> compatible with generic-ohci.
>
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
> ---
> .../devicetree/bindings/usb/generic-ohci.yaml | 18 +++++++++++++++++-
> 1 file changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/usb/generic-ohci.yaml b/Documentation/devicetree/bindings/usb/generic-ohci.yaml
> index a9ba7257b884..e116ed90471e 100644
> --- a/Documentation/devicetree/bindings/usb/generic-ohci.yaml
> +++ b/Documentation/devicetree/bindings/usb/generic-ohci.yaml
> @@ -44,6 +44,7 @@ properties:
> - hpe,gxp-ohci
> - ibm,476gtr-ohci
> - ingenic,jz4740-ohci
> + - rockchip,rk3588-ohci
> - snps,hsdk-v1.0-ohci
> - const: generic-ohci
> - enum:
> @@ -69,7 +70,7 @@ properties:
>
> clocks:
> minItems: 1
> - maxItems: 3
> + maxItems: 4
> description: |
> In case the Renesas R-Car Gen3 SoCs:
> - if a host only channel: first clock should be host.
> @@ -147,6 +148,21 @@ allOf:
> then:
> properties:
> transceiver: false
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: rockchip,rk3588-ohci
> + then:
> + properties:
> + clocks:
> + minItems: 4
> + maxItems: 4
Only need minItems here.
> + else:
> + properties:
> + clocks:
> + minItems: 1
> + maxItems: 3
Only need maxItems here.
With that,
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2023-04-11 13:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 13:55 [PATCHv1 0/3] generic-ohci/ehci: add RK3588 support Sebastian Reichel
2023-04-06 13:55 ` [PATCHv1 1/3] dt-bindings: usb: Add RK3588 OHCI Sebastian Reichel
2023-04-11 13:12 ` Rob Herring [this message]
2023-04-06 13:55 ` [PATCHv1 2/3] dt-bindings: usb: Add RK3588 EHCI Sebastian Reichel
2023-04-11 13:12 ` Rob Herring
2023-04-06 13:55 ` [PATCHv1 3/3] usb: host: ohci-platform: increase max clock number to 4 Sebastian Reichel
2023-04-06 14:09 ` [PATCHv1 0/3] generic-ohci/ehci: add RK3588 support Sebastian Reichel
-- strict thread matches above, loose matches on Subject: below --
2023-04-04 14:53 Sebastian Reichel
2023-04-04 14:53 ` [PATCHv1 1/3] dt-bindings: usb: Add RK3588 OHCI Sebastian Reichel
2023-04-06 7:45 ` Krzysztof Kozlowski
2023-04-06 10:51 ` Sebastian Reichel
2023-04-06 11:02 ` Krzysztof Kozlowski
2023-04-06 12:33 ` Sebastian Reichel
2023-04-06 12:47 ` Krzysztof Kozlowski
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=20230411131237.GA2837061-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=stern@rowland.harvard.edu \
/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