SUPERH platform development
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/3] usb: phy: Add RCAR Gen2 USB phy
Date: Thu, 10 Oct 2013 15:12:27 +0000	[thread overview]
Message-ID: <20131010151227.GB28375@radagast> (raw)
In-Reply-To: <1381188423-1867-2-git-send-email-valentine.barshak@cogentembedded.com>

[-- Attachment #1: Type: text/plain, Size: 2119 bytes --]

On Wed, Oct 09, 2013 at 10:32:12PM +0200, Laurent Pinchart wrote:
> Hi Valentine,
> 
> Thank you for the patch.
> 
> On Tuesday 08 October 2013 23:43:25 Valentine Barshak wrote:
> > This adds RCAR Gen2 USB phy support. The driver configures
> > USB channels 0/2 which are shared between PCI USB hosts and
> > USBHS/USBSS devices. It also controls internal USBHS phy.
> > 
> > Signed-off-by: Valentine Barshak <valentine.barshak@cogentembedded.com>
> > ---
> >  drivers/usb/phy/Kconfig                         |  13 ++
> >  drivers/usb/phy/Makefile                        |   1 +
> >  drivers/usb/phy/phy-rcar-gen2-usb.c             | 255 +++++++++++++++++++++
> >  include/linux/platform_data/usb-rcar-gen2-phy.h |  22 ++
> >  4 files changed, 291 insertions(+)
> >  create mode 100644 drivers/usb/phy/phy-rcar-gen2-usb.c
> >  create mode 100644 include/linux/platform_data/usb-rcar-gen2-phy.h
> > 
> > diff --git a/drivers/usb/phy/Kconfig b/drivers/usb/phy/Kconfig
> > index d5589f9..297062c 100644
> > --- a/drivers/usb/phy/Kconfig
> > +++ b/drivers/usb/phy/Kconfig
> > @@ -214,6 +214,19 @@ config USB_RCAR_PHY
> >  	  To compile this driver as a module, choose M here: the
> >  	  module will be called phy-rcar-usb.
> > 
> > +config USB_RCAR_GEN2_PHY
> > +	tristate "Renesas R-Car Gen2 USB PHY support"
> > +	depends on ARCH_R8A7790 || ARCH_R8A7791
> 
> From a development point of view it's always nice to be able to compile the 
> driver for a wider range of devices, even if the device is only found in the 
> R8A779[01]. This allows catching compilation errors, for instance caused by 
> API changes that affect all drivers using the API being modified.
> 
> I would use either
> 
> 	depends on ARM
> 
> or
> 
> 	depends on ARCH_R8A7790 || ARCH_R8A7791 || COMPILE_TEST
> 
> (assuming the driver can compile on non-ARM platforms, otherwise the above 
> line could be changed to ARCH_R8A7790 || ARCH_R8A7791 || (ARM && 
> COMPILE_TEST)).

every driver should compile on all arches. I will be enforcing
COMPILE_TEST before applying any new drivers.

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2013-10-10 15:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-07 23:27 [PATCH 1/3] usb: phy: Add RCAR Gen2 USB phy Valentine Barshak
2013-10-07 23:57 ` Valentine
2013-10-08  3:27 ` Kuninori Morimoto
2013-10-08  7:47 ` Valentine
2013-10-08 10:00 ` Kuninori Morimoto
2013-10-08 19:43 ` Valentine Barshak
2013-10-09 20:32 ` Laurent Pinchart
2013-10-09 21:21 ` Valentine
2013-10-09 21:28 ` Laurent Pinchart
2013-10-09 21:47 ` Valentine
2013-10-09 22:14 ` Valentine Barshak
2013-10-10 15:12 ` Felipe Balbi [this message]
2013-10-10 15:13 ` Felipe Balbi
2013-10-10 15:15 ` Felipe Balbi
2013-10-10 15:23 ` Felipe Balbi
2013-10-10 16:29 ` Valentine
2013-10-10 16:32 ` Felipe Balbi
2013-10-10 16:35 ` Valentine Barshak

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=20131010151227.GB28375@radagast \
    --to=balbi@ti.com \
    --cc=linux-sh@vger.kernel.org \
    /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