devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
	linux-sh@vger.kernel.org
Subject: Re: [PATCH v3 2/3] usb: renesas_usbhs: add fallback compatibility strings
Date: Tue, 15 Dec 2015 14:33:48 +0300	[thread overview]
Message-ID: <566FFA9C.6010900@cogentembedded.com> (raw)
In-Reply-To: <20151215064134.GA29842@verge.net.au>

Hello.

On 12/15/2015 9:41 AM, Simon Horman wrote:

>>> Add fallback compatibility strings for R-Car Gen2 and Gen3.
>>> This is in keeping with the fallback scheme being adopted wherever
>>> appropriate for drivers for Renesas SoCs.
>>>
>>> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
>>> ---
>>> v3
>>> * Moved documentation of SoC names to a separate patch
>>> * Use correct fallback compatibility string in example
>>>
>>> v2
>>> * Add R-Car Gen2 and Gen3 fallback compatibility strings rather than
>>>    a single compatibility string for all of R-Car.
>>> ---
>>>   Documentation/devicetree/bindings/usb/renesas_usbhs.txt | 10 +++++++++-
>>>   drivers/usb/renesas_usbhs/common.c                      |  9 +++++++++
>>>   2 files changed, 18 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/Documentation/devicetree/bindings/usb/renesas_usbhs.txt b/Documentation/devicetree/bindings/usb/renesas_usbhs.txt
>>> index a14c0bb561d5..c55cf77006d0 100644
>>> --- a/Documentation/devicetree/bindings/usb/renesas_usbhs.txt
>>> +++ b/Documentation/devicetree/bindings/usb/renesas_usbhs.txt
>>> @@ -2,10 +2,18 @@ Renesas Electronics USBHS driver
>>>
>>>   Required properties:
>>>     - compatible: Must contain one of the following:
>>
>>     Really?
>
> Would "...one or more of the following" help?

    It would, of course.

>>> +
>>>   	- "renesas,usbhs-r8a7790" for r8a7790 (R-Car H2) compatible device
>>>   	- "renesas,usbhs-r8a7791" for r8a7791 (R-Car M2-W) compatible device
>>>   	- "renesas,usbhs-r8a7794" for r8a7794 (R-Car E2) compatible device
>>>   	- "renesas,usbhs-r8a7795" for r8a7795 (R-Car H3) compatible device
>>> +	- "renesas,rcar-gen2-usbhs" for R-Car Gen2 compatible device
>>> +	- "renesas,rcar-gen3-usbhs" for R-Car Gen3 compatible device
>>> +
>>> +	When compatible with the generic version, nodes must list the
>>> +	SoC-specific version corresponding to the platform first followed
>>> +	by the generic version.
>>> +
>>
>>     This kinda contradicts the above claim.
>>
>> [...]

MBR, Sergei


  parent reply	other threads:[~2015-12-15 11:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11  2:12 [PATCH v3 0/3] usb: renesas_usbhs: More compat strings Simon Horman
2015-12-11  2:12 ` [PATCH v3 1/3] usb: renesas_usbhs: add SoC names to compatibility string documentation Simon Horman
2015-12-11  3:54   ` Rob Herring
     [not found] ` <1449799947-19866-1-git-send-email-horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2015-12-11  2:12   ` [PATCH v3 2/3] usb: renesas_usbhs: add fallback compatibility strings Simon Horman
2015-12-11  3:56     ` Rob Herring
2015-12-11  4:02       ` Simon Horman
2015-12-11 12:24     ` Sergei Shtylyov
     [not found]       ` <566AC07B.6060201-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2015-12-15  6:41         ` Simon Horman
     [not found]           ` <20151215064134.GA29842-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2015-12-15 11:00             ` Geert Uytterhoeven
2015-12-15 11:33           ` Sergei Shtylyov [this message]
2015-12-11  2:12   ` [PATCH v3 3/3] usb: renesas_usbhs: add device tree support for r8a779[23] Simon Horman
2015-12-11  2:58 ` [PATCH v3 0/3] usb: renesas_usbhs: More compat strings Kuninori Morimoto
2015-12-16 16:23 ` Felipe Balbi

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=566FFA9C.6010900@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=magnus.damm@gmail.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).