Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Tushar Behera <trblinux@gmail.com>
To: Sachin Kamat <sachin.kamat@samsung.com>, linux-usb@vger.kernel.org
Cc: linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com,
	balbi@ti.com, gregkh@linuxfoundation.org, dianders@chromium.org,
	gautam.vivek@samsung.com, spk.linux@gmail.com,
	Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: [PATCH 1/2] usb: host: Kconfig: Select PHY drivers for Exynos EHCI/OHCI
Date: Thu, 26 Jun 2014 11:25:07 +0530	[thread overview]
Message-ID: <53ABB5BB.4090301@gmail.com> (raw)
In-Reply-To: <1403761178-5371-1-git-send-email-sachin.kamat@samsung.com>

On 06/26/2014 11:09 AM, Sachin Kamat wrote:
> EHCI and OHCI drivers on Exynos platforms do not work without their
> corresponding SoC specific phy drivers. Hence it makes no sense to
> keep these phy drivers as user selectable. Instead select them from
> the respective USB configs to make things easier for the end user.
> While at it enable 5250 phy for Exynos 5420 SoC too.
> 
> Signed-off-by: Sachin Kamat <sachin.kamat@samsung.com>
> Cc: Kishon Vijay Abraham I <kishon@ti.com>
> ---

Reviewed-by: Tushar Behera <tushar.b@samsung.com>

>  drivers/phy/Kconfig      |   37 +++++++------------------------------
>  drivers/usb/host/Kconfig |   10 ++++++----
>  2 files changed, 13 insertions(+), 34 deletions(-)
> 
> diff --git a/drivers/phy/Kconfig b/drivers/phy/Kconfig
> index 16a2f067c242..7fe7ef5f1322 100644
> --- a/drivers/phy/Kconfig
> +++ b/drivers/phy/Kconfig
> @@ -121,44 +121,21 @@ config PHY_SUN4I_USB
>  	  parts, as well as the 2 regular USB 2 host PHYs.
>  
>  config PHY_SAMSUNG_USB2
> -	tristate "Samsung USB 2.0 PHY driver"
> +	tristate
>  	select GENERIC_PHY
>  	select MFD_SYSCON
> -	help
> -	  Enable this to support the Samsung USB 2.0 PHY driver for Samsung
> -	  SoCs. This driver provides the interface for USB 2.0 PHY. Support for
> -	  particular SoCs has to be enabled in addition to this driver. Number
> -	  and type of supported phys depends on the SoC.
> +	select PHY_EXYNOS4210_USB2 if CPU_EXYNOS4210
> +	select PHY_EXYNOS4X12_USB2 if (SOC_EXYNOS4212 || SOC_EXYNOS4412)
> +	select PHY_EXYNOS5250_USB2 if (SOC_EXYNOS5250 || SOC_EXYNOS5420)
>  
>  config PHY_EXYNOS4210_USB2
> -	bool "Support for Exynos 4210"
> -	depends on PHY_SAMSUNG_USB2
> -	depends on CPU_EXYNOS4210
> -	help
> -	  Enable USB PHY support for Exynos 4210. This option requires that
> -	  Samsung USB 2.0 PHY driver is enabled and means that support for this
> -	  particular SoC is compiled in the driver. In case of Exynos 4210 four
> -	  phys are available - device, host, HSIC0 and HSIC1.
> +	bool
>  
>  config PHY_EXYNOS4X12_USB2
> -	bool "Support for Exynos 4x12"
> -	depends on PHY_SAMSUNG_USB2
> -	depends on (SOC_EXYNOS4212 || SOC_EXYNOS4412)
> -	help
> -	  Enable USB PHY support for Exynos 4x12. This option requires that
> -	  Samsung USB 2.0 PHY driver is enabled and means that support for this
> -	  particular SoC is compiled in the driver. In case of Exynos 4x12 four
> -	  phys are available - device, host, HSIC0 and HSIC1.
> +	bool
>  
>  config PHY_EXYNOS5250_USB2
> -	bool "Support for Exynos 5250"
> -	depends on PHY_SAMSUNG_USB2
> -	depends on SOC_EXYNOS5250
> -	help
> -	  Enable USB PHY support for Exynos 5250. This option requires that
> -	  Samsung USB 2.0 PHY driver is enabled and means that support for this
> -	  particular SoC is compiled in the driver. In case of Exynos 5250 four
> -	  phys are available - device, host, HSIC0 and HSIC.
> +	bool
>  
>  config PHY_EXYNOS5_USBDRD
>  	tristate "Exynos5 SoC series USB DRD PHY driver"
> diff --git a/drivers/usb/host/Kconfig b/drivers/usb/host/Kconfig
> index 61b7817bd66b..2938807331de 100644
> --- a/drivers/usb/host/Kconfig
> +++ b/drivers/usb/host/Kconfig
> @@ -211,10 +211,11 @@ config USB_EHCI_SH
>  	  If you use the PCI EHCI controller, this option is not necessary.
>  
>  config USB_EHCI_EXYNOS
> -       tristate "EHCI support for Samsung S5P/EXYNOS SoC Series"
> -       depends on PLAT_S5P || ARCH_EXYNOS
> -       help
> -	Enable support for the Samsung Exynos SOC's on-chip EHCI controller.
> +	tristate "EHCI support for Samsung S5P/EXYNOS SoC Series"
> +	depends on PLAT_S5P || ARCH_EXYNOS
> +	select PHY_SAMSUNG_USB2 if ARCH_EXYNOS
> +	help
> +	  Enable support for the Samsung Exynos SOC's on-chip EHCI controller.
>  
>  config USB_EHCI_MV
>  	bool "EHCI support for Marvell PXA/MMP USB controller"
> @@ -520,6 +521,7 @@ config USB_OHCI_SH
>  config USB_OHCI_EXYNOS
>  	tristate "OHCI support for Samsung S5P/EXYNOS SoC Series"
>  	depends on PLAT_S5P || ARCH_EXYNOS
> +	select PHY_SAMSUNG_USB2 if ARCH_EXYNOS
>  	help
>  	 Enable support for the Samsung Exynos SOC's on-chip OHCI controller.
>  
> 


-- 
Tushar Behera

  reply	other threads:[~2014-06-26  5:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26  5:39 [PATCH 1/2] usb: host: Kconfig: Select PHY drivers for Exynos EHCI/OHCI Sachin Kamat
2014-06-26  5:55 ` Tushar Behera [this message]
2014-06-26  8:09 ` Vivek Gautam
2014-06-26  8:25   ` Sachin Kamat
     [not found]     ` <CAK5sBcHL0f+UVFoyQT3O8m+NAv3rNjiq=aEH4xh9BV3tFbYcSg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-26  8:53       ` Sachin Kamat
2014-06-26  9:07         ` Vivek Gautam
     [not found] ` <1403761178-5371-1-git-send-email-sachin.kamat-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-06-26  5:39   ` [PATCH 2/2] usb: dwc3: Kconfig: Select PHY drivers for Exynos DWC3 Sachin Kamat
2014-06-26  5:56     ` Tushar Behera
2014-06-26  8:49   ` [PATCH 1/2] usb: host: Kconfig: Select PHY drivers for Exynos EHCI/OHCI Kishon Vijay Abraham I
2014-06-26  9:02     ` Sachin Kamat
2014-06-27 15:46 ` Felipe Balbi
2014-06-27 15:55   ` Doug Anderson
2014-06-27 15:59     ` Felipe Balbi
     [not found]       ` <20140627155900.GN8069-HgARHv6XitL9zxVx7UNMDg@public.gmane.org>
2014-06-27 16:32         ` Doug Anderson
2014-06-27 16:53           ` Olof Johansson
2014-06-30  8:32             ` Sachin Kamat

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=53ABB5BB.4090301@gmail.com \
    --to=trblinux@gmail.com \
    --cc=balbi@ti.com \
    --cc=dianders@chromium.org \
    --cc=gautam.vivek@samsung.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kgene.kim@samsung.com \
    --cc=kishon@ti.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sachin.kamat@samsung.com \
    --cc=spk.linux@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