From: Simon Horman <horms@verge.net.au>
To: Rob Herring <robh@kernel.org>
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: Fri, 11 Dec 2015 13:02:34 +0900 [thread overview]
Message-ID: <20151211040233.GA13336@verge.net.au> (raw)
In-Reply-To: <20151211035624.GA12611@rob-hp-laptop>
On Thu, Dec 10, 2015 at 09:56:24PM -0600, Rob Herring wrote:
> On Fri, Dec 11, 2015 at 11:12:26AM +0900, 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>
>
> Binding looks okay, but one possible typo.
>
> Acked-by: Rob Herring <robh@kernel.org>
>
> > --- a/drivers/usb/renesas_usbhs/common.c
> > +++ b/drivers/usb/renesas_usbhs/common.c
> > @@ -481,6 +481,15 @@ static const struct of_device_id usbhs_of_match[] = {
> > .compatible = "renesas,usbhs-r8a7795",
> > .data = (void *)USBHS_TYPE_RCAR_GEN2,
> > },
> > + {
> > + .compatible = "renesas,rcar-gen2-usbhs",
> > + .data = (void *)USBHS_TYPE_RCAR_GEN2,
> > + },
> > + {
> > + /* Gen3 is compatible with Gen2 */
> > + .compatible = "renesas,rcar-gen3-usbhs",
> > + .data = (void *)USBHS_TYPE_RCAR_GEN2,
>
> This supposed to be GEN3?
Confusingly the symbol is called GEN2 as it was there for Gen 2
before Gen 3 came along and (so far) Gen 3 is compatible with Gen 2.
I'd be happy to change the name but I think that would be best
as an incremental change on top of this one.
next prev parent reply other threads:[~2015-12-11 4:02 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 [this message]
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
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=20151211040233.GA13336@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-sh@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--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).