From: Rob Herring <robh@kernel.org>
To: Maxime Ripard <maxime@cerno.tech>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org,
Maxime Ripard <maxime@cerno.tech>
Subject: Re: [PATCH v2] dt-bindings: usb: Convert Allwinner USB PHY controller to a schema
Date: Tue, 17 Dec 2019 19:39:05 -0600 [thread overview]
Message-ID: <20191218013905.GA25729@bogus> (raw)
In-Reply-To: <20191209093340.50552-1-maxime@cerno.tech>
On Mon, 9 Dec 2019 10:33:40 +0100, Maxime Ripard wrote:
> The Allwinner SoCs have a USB PHY controller that is supported in Linux,
> with a matching Device Tree binding.
>
> Now that we have the DT validation in place, let's convert the device tree
> bindings for that controller over to a YAML schemas.
>
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
>
> ---
>
> Changes from v1:
> - Split the schemas into files of their own to make it more readable
> ---
> .../phy/allwinner,sun4i-a10-usb-phy.yaml | 105 ++++++++++++++
> .../phy/allwinner,sun50i-a64-usb-phy.yaml | 106 ++++++++++++++
> .../phy/allwinner,sun50i-h6-usb-phy.yaml | 105 ++++++++++++++
> .../phy/allwinner,sun5i-a13-usb-phy.yaml | 93 ++++++++++++
> .../phy/allwinner,sun6i-a31-usb-phy.yaml | 119 +++++++++++++++
> .../phy/allwinner,sun8i-a23-usb-phy.yaml | 102 +++++++++++++
> .../phy/allwinner,sun8i-a83t-usb-phy.yaml | 122 ++++++++++++++++
> .../phy/allwinner,sun8i-h3-usb-phy.yaml | 137 ++++++++++++++++++
> .../phy/allwinner,sun8i-r40-usb-phy.yaml | 119 +++++++++++++++
> .../phy/allwinner,sun8i-v3s-usb-phy.yaml | 86 +++++++++++
> .../devicetree/bindings/phy/sun4i-usb-phy.txt | 68 ---------
> 11 files changed, 1094 insertions(+), 68 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun4i-a10-usb-phy.yaml
> create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun50i-a64-usb-phy.yaml
> create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun50i-h6-usb-phy.yaml
> create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun5i-a13-usb-phy.yaml
> create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun6i-a31-usb-phy.yaml
> create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun8i-a23-usb-phy.yaml
> create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun8i-a83t-usb-phy.yaml
> create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun8i-h3-usb-phy.yaml
> create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun8i-r40-usb-phy.yaml
> create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun8i-v3s-usb-phy.yaml
> delete mode 100644 Documentation/devicetree/bindings/phy/sun4i-usb-phy.txt
>
Applied, thanks.
Rob
prev parent reply other threads:[~2019-12-18 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 9:33 [PATCH v2] dt-bindings: usb: Convert Allwinner USB PHY controller to a schema Maxime Ripard
2019-12-18 1:39 ` 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=20191218013905.GA25729@bogus \
--to=robh@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime@cerno.tech \
/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).