From: Simon Horman <horms@verge.net.au>
To: Chris Brandt <chris.brandt@renesas.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-usb@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Subject: Re: [PATCH v4 2/3] dt-bindings: usb: renesas_usbhs: Add support for RZ/A1
Date: Tue, 9 Jan 2018 10:01:02 +0100 [thread overview]
Message-ID: <20180109090101.ggn56dgrzyw5xihc@verge.net.au> (raw)
In-Reply-To: <20180108123055.64890-3-chris.brandt@renesas.com>
On Mon, Jan 08, 2018 at 07:30:54AM -0500, Chris Brandt wrote:
> Document support for RZ/A1 SoCs
>
> Signed-off-by: Chris Brandt <chris.brandt@renesas.com>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
> ---
> v4:
> * Re-added "renesas,usbhs-r7s72100"
> v3:
> * Removed "renesas,usbhs-r7s72100"
> v2:
> * Added Reviewed-by
> ---
> Documentation/devicetree/bindings/usb/renesas_usbhs.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/usb/renesas_usbhs.txt b/Documentation/devicetree/bindings/usb/renesas_usbhs.txt
> index 47394ab788e3..d060172f1529 100644
> --- a/Documentation/devicetree/bindings/usb/renesas_usbhs.txt
> +++ b/Documentation/devicetree/bindings/usb/renesas_usbhs.txt
> @@ -13,8 +13,10 @@ Required properties:
> - "renesas,usbhs-r8a7795" for r8a7795 (R-Car H3) compatible device
> - "renesas,usbhs-r8a7796" for r8a7796 (R-Car M3-W) compatible device
> - "renesas,usbhs-r8a77995" for r8a77995 (R-Car D3) compatible device
> + - "renesas,usbhs-r7s72100" for r7s72100 (RZ/A1) compatible device
> - "renesas,rcar-gen2-usbhs" for R-Car Gen2 or RZ/G1 compatible devices
> - "renesas,rcar-gen3-usbhs" for R-Car Gen3 compatible device
> + - "renesas,rza1-usbhs" for RZ/A1 compatible device
>
> When compatible with the generic version, nodes must list the
> SoC-specific version corresponding to the platform first followed
> --
> 2.15.1
>
>
next prev parent reply other threads:[~2018-01-09 9:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 12:30 [PATCH v4 0/3] usb: renesas_usbhs: Add RZ/A1 support Chris Brandt
[not found] ` <20180108123055.64890-1-chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2018-01-08 12:30 ` [PATCH v4 1/3] usb: renesas_usbhs: Add support for RZ/A1 Chris Brandt
[not found] ` <20180108123055.64890-2-chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2018-01-10 8:26 ` Yoshihiro Shimoda
[not found] ` <TY1PR06MB0992C908652672902D18D824D8110-/PRLmSCtZ16WJvbLRFYGcG0DtJ1/0DrXvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-01-10 8:31 ` Yoshihiro Shimoda
2018-01-08 12:30 ` [PATCH v4 2/3] dt-bindings: " Chris Brandt
2018-01-09 9:01 ` Simon Horman [this message]
[not found] ` <20180108123055.64890-3-chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2018-01-10 8:31 ` Yoshihiro Shimoda
2018-01-11 21:58 ` Rob Herring
2018-01-08 12:30 ` [PATCH v4 3/3] ARM: dts: r7s72100: add USB device to device tree Chris Brandt
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=20180109090101.ggn56dgrzyw5xihc@verge.net.au \
--to=horms@verge.net.au \
--cc=chris.brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sergei.shtylyov@cogentembedded.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).