From: Rob Herring <robh+dt@kernel.org>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Linux USB List <linux-usb@vger.kernel.org>,
"open list:MEDIA DRIVERS FOR RENESAS - FCP"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v3] dt-bindings: usb: renesas_usbhs: convert bindings to json-schema
Date: Thu, 7 Nov 2019 09:06:26 -0600 [thread overview]
Message-ID: <CAL_JsqJT-k98xtsxAK+jZ1Jhwz=SmpGDR3hUiN9tcOQZBACXTw@mail.gmail.com> (raw)
In-Reply-To: <1573102944-11095-1-git-send-email-yoshihiro.shimoda.uh@renesas.com>
On Wed, Nov 6, 2019 at 11:02 PM Yoshihiro Shimoda
<yoshihiro.shimoda.uh@renesas.com> wrote:
>
> Convert Renesas USBHS (HS-USB) controller bindings documentation
> to json-schema.
>
> Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
> ---
> Changes from v2:
> - Fix dma-names and dr_mode.
> https://patchwork.kernel.org/patch/11229977/
>
> Changes from v1:
> - Remove enum from RZ/A[12] compatibles.
> - Remove comments from reg and clocks.
> - Change maxItems from 2 to 3 on clocks for USB 2.0 clock selector.
> - Add items on clocks.
> - Remove $ref from a gpio property.
> - Add maxItems on phys, phy-names and resets.
> - Remove generic.txt file reference.
> - Remove the last blank line.
> https://patchwork.kernel.org/patch/11205919/
>
> .../devicetree/bindings/usb/renesas,usbhs.txt | 58 ----------
> .../devicetree/bindings/usb/renesas,usbhs.yaml | 126 +++++++++++++++++++++
> 2 files changed, 126 insertions(+), 58 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/usb/renesas,usbhs.txt
> create mode 100644 Documentation/devicetree/bindings/usb/renesas,usbhs.yaml
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2019-11-07 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 5:02 [PATCH v3] dt-bindings: usb: renesas_usbhs: convert bindings to json-schema Yoshihiro Shimoda
2019-11-07 15:06 ` 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='CAL_JsqJT-k98xtsxAK+jZ1Jhwz=SmpGDR3hUiN9tcOQZBACXTw@mail.gmail.com' \
--to=robh+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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).