From: Rob Herring <robh@kernel.org>
To: Vincent Shih <vincent.sunplus@gmail.com>
Cc: gregkh@linuxfoundation.org, stern@rowland.harvard.edu,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, wells.lu@sunplus.com
Subject: Re: [PATCH v1 2/2] dt-bindings: usb: Add bindings doc for Sunplus EHCI driver
Date: Tue, 22 Feb 2022 15:37:39 -0600 [thread overview]
Message-ID: <YhVXo1K/asHgGVda@robh.at.kernel.org> (raw)
In-Reply-To: <1644827562-17244-3-git-send-email-vincent.sunplus@gmail.com>
On Mon, Feb 14, 2022 at 04:32:42PM +0800, Vincent Shih wrote:
> Add bindings doc for Sunplus EHCI driver
>
> Signed-off-by: Vincent Shih <vincent.sunplus@gmail.com>
> ---
> .../bindings/usb/sunplus,sp7021-usb-ehci.yaml | 69 ++++++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 70 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/usb/sunplus,sp7021-usb-ehci.yaml
>
> diff --git a/Documentation/devicetree/bindings/usb/sunplus,sp7021-usb-ehci.yaml b/Documentation/devicetree/bindings/usb/sunplus,sp7021-usb-ehci.yaml
> new file mode 100644
> index 0000000..299f7b7
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/sunplus,sp7021-usb-ehci.yaml
> @@ -0,0 +1,69 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +# Copyright (C) Sunplus Co., Ltd. 2021
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/usb/sunplus,sp7021-usb-ehci.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Sunplus SP7021 EHCI Device Tree bindings for ehci0/ehci1
> +
> +maintainers:
> + - Vincent Shih <vincent.sunplus@gmail.com>
> +
> +allOf:
> + - $ref: usb-hcd.yaml#
> +
> +properties:
> + compatible:
> + enum:
> + - sunplus,sp7021-usb-ehci0
> + - sunplus,sp7021-usb-ehci1
> +
> + clocks:
> + maxItems: 2
> +
> + clock-names:
> + items:
> + - const: USB2_USBC0
> + - const: USB2_UPHY0
This doesn't match what the driver looks for, though the 0 or 1 on the
end is wrong. You obviously have not tested this against your actual dts
file(s).
The 'USB2_' part is redundant. You only need enough information to
distinguish clocks within a h/w block.
> +
> + reg:
> + maxItems: 4
You have to define each entry.
> +
> + interrupts:
> + maxItems: 1
> +
> + nvmem-cell-names:
> + description: names corresponding to the nvmem cells of disconnect voltage
> + const: disc_vol
> +
> + nvmem-cells:
> + description: nvmem cell address of disconnect voltage
> + maxItems: 1
> +
> +required:
> + - compatible
> + - clocks
> + - reg
> + - interrupts
> + - nvmem-cell-names
> + - nvmem-cells
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> +
> + sp_ehci0: usb@9c102100 {
> + compatible = "sunplus,sp7021-usb-ehci0";
> + clocks = <&clkc 0x3a>, <&clkc 0x3d>;
> + clock-names = "USB2_USBC0", "USB2_UPHY0";
> + reg = <0x9c102100 0x68>, <0x9c004a80 0x80>,
> + <0x9c000000 0x80>, <0x9c000200 0x80>;
> + interrupt-parent = <&intc>;
> + interrupts = <14 IRQ_TYPE_LEVEL_HIGH>;
> + nvmem-cell-names = "disc_vol";
> + nvmem-cells = <&disc_vol>;
> + };
> +...
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 6c2faf3..49702c4 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17951,6 +17951,7 @@ SUNPLUS USB EHCI DRIVER
> M: Vincent Shih <vincent.sunplus@gmail.com>
> L: linux-usb@vger.kernel.org
> S: Maintained
> +F: Documentation/devicetree/bindings/nvmem/sunplus,sp7021-ocotp.yaml
> F: drivers/usb/host/ehci-sunplus.c
>
> SUPERH
> --
> 2.7.4
>
>
prev parent reply other threads:[~2022-02-22 21:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 8:32 [PATCH v1 0/2] Add driver for ehci in Sunplus SP7021 Vincent Shih
2022-02-14 8:32 ` [PATCH v1 1/2] usb: host: ehci-sunplus: " Vincent Shih
2022-02-14 8:38 ` Greg KH
2022-02-14 9:03 ` 施錕鴻
2022-02-14 9:14 ` Greg KH
2022-02-14 9:48 ` 施錕鴻
2022-02-14 11:33 ` Greg KH
2022-02-16 10:41 ` 施錕鴻
2022-02-22 21:32 ` Rob Herring
2022-02-14 8:32 ` [PATCH v1 2/2] dt-bindings: usb: Add bindings doc for Sunplus EHCI driver Vincent Shih
2022-02-22 21:37 ` Rob Herring [this message]
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=YhVXo1K/asHgGVda@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=vincent.sunplus@gmail.com \
--cc=wells.lu@sunplus.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.