mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: "'Vivek Gautam'" <gautam.vivek@samsung.com>,
	<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<devicetree-discuss@lists.ozlabs.org>,
	<linux-samsung-soc@vger.kernel.org>, <gregkh@linuxfoundation.org>,
	<balbi@ti.com>, <grant.likely@secretlab.ca>,
	<sylvester.nawrocki@gmail.com>, <tomasz.figa@gmail.com>,
	<av.tikhomirov@samsung.com>, <dianders@chromium.org>,
	<p.paneri@samsung.com>
Subject: Re: [PATCH v4 2/2] usb: phy: samsung: Add PHY support for USB 3.0 controller
Date: Wed, 30 Jan 2013 10:20:34 +0200	[thread overview]
Message-ID: <20130130082034.GF15258@arwen.pp.htv.fi> (raw)
In-Reply-To: <077f01cdfeaf$4f7b8780$ee729680$@samsung.com>

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

On Tue, Jan 29, 2013 at 10:01:52PM -0800, Kukjin Kim wrote:
> Vivek Gautam wrote:
> > 
> > Adding PHY driver support for USB 3.0 controller for Samsung's
> > SoCs.
> > 
> > Signed-off-by: Vivek Gautam <gautam.vivek@samsung.com>
> > ---
> > 
> > Changes from v3:
> >  - Making SAMSUNG_USB3PHY dependent on SAMSUNG_USBPHY.
> >  - Adding USB_DWC3 to dependencies of SAMSUNG_USB2PHY since
> >    dwc3 controller also looks for USB2 type PHY.
> > 
> >  drivers/usb/phy/Kconfig          |   11 +-
> >  drivers/usb/phy/Makefile         |    1 +
> >  drivers/usb/phy/samsung-usb3.c   |  349
> > ++++++++++++++++++++++++++++++++++++++
> >  drivers/usb/phy/samsung-usbphy.h |   81 +++++++++
> >  4 files changed, 441 insertions(+), 1 deletions(-)
> >  create mode 100644 drivers/usb/phy/samsung-usb3.c
> > 
> > diff --git a/drivers/usb/phy/Kconfig b/drivers/usb/phy/Kconfig
> > index cc0d230..9325a95 100644
> > --- a/drivers/usb/phy/Kconfig
> > +++ b/drivers/usb/phy/Kconfig
> > @@ -52,14 +52,23 @@ config SAMSUNG_USBPHY
> >  	help
> >  	  Enable this to support Samsung USB phy controllers for Samsung
> >  	  SoCs.
> > +	  Further enable USB 2.0 type PHY or USB 3.0 type PHY as required
> > +	  for USB controllers in use.
> > 
> >  if SAMSUNG_USBPHY
> > 
> >  config SAMSUNG_USB2PHY
> >  	bool "Samsung USB 2.0 PHY controller Driver"
> > -	depends on USB_S3C_HSOTG || USB_EHCI_S5P ||
> > USB_OHCI_EXYNOS
> > +	depends on USB_S3C_HSOTG || USB_EHCI_S5P ||
> > USB_OHCI_EXYNOS || USB_DWC3
> >  	help
> >  	  Enable this to support Samsung USB 2.0 (High Speed) phy controller
> >  	  for Samsung SoCs.
> > 
> > +config SAMSUNG_USB3PHY
> > +	bool "Samsung USB 3.0 PHY controller Driver"
> > +	depends on USB_DWC3
> > +	help
> > +	  Enable this to support Samsung USB 3.0 (Super Speed) phy
> > controller
> > +	  for samsung SoCs.
> > +
> >  endif
> 
> It mean, when USB_DWC3 is selected, we can select only one USB2PHY or
> USB3PHY?

right, not sure that's a wise idea. It makes enabling USB support
trickier than it needs to be. How about just dropping all dependencies
if it compiles cleanly on all arches ?

-- 
balbi

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

  reply	other threads:[~2013-01-30  8:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 12:59 [PATCH v3 0/2] Adding USB 3.0 DRD-phy support for exynos5250 Vivek Gautam
2013-01-14 12:59 ` [PATCH v3 1/2] usb: phy: samsung: Common out the generic stuff Vivek Gautam
2013-01-28 10:24   ` [PATCH v4 " Vivek Gautam
2013-01-29  5:34     ` Vivek Gautam
2013-01-30  5:56     ` Kukjin Kim
2013-02-05  6:32       ` Vivek Gautam
2013-01-14 12:59 ` [PATCH v3 2/2] usb: phy: samsung: Add PHY support for USB 3.0 controller Vivek Gautam
2013-01-28 10:26   ` [PATCH v4 " Vivek Gautam
2013-01-29  5:35     ` Vivek Gautam
2013-01-30  6:01     ` Kukjin Kim
2013-01-30  8:20       ` Felipe Balbi [this message]
2013-02-05  6:36       ` Vivek Gautam
2013-01-21  6:45 ` [PATCH v3 0/2] Adding USB 3.0 DRD-phy support for exynos5250 Vivek Gautam
2013-01-21  8:26   ` 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=20130130082034.GF15258@arwen.pp.htv.fi \
    --to=balbi@ti.com \
    --cc=av.tikhomirov@samsung.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dianders@chromium.org \
    --cc=gautam.vivek@samsung.com \
    --cc=grant.likely@secretlab.ca \
    --cc=gregkh@linuxfoundation.org \
    --cc=kgene.kim@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=p.paneri@samsung.com \
    --cc=sylvester.nawrocki@gmail.com \
    --cc=tomasz.figa@gmail.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

Powered by JetHome