Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Anton Tikhomirov <av.tikhomirov@samsung.com>
To: 'Vivek Gautam' <gautam.vivek@samsung.com>,
	linux-usb@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, gregkh@linuxfoundation.org,
	stern@rowland.harvard.edu, balbi@ti.com, kgene.kim@samsung.com
Subject: RE: [PATCH 3/3] usb: dwc3-exynos: Make provision for vdd regulators
Date: Wed, 23 Apr 2014 18:26:51 +0900	[thread overview]
Message-ID: <00bf01cf5ed6$28de18d0$7a9a4a70$%tikhomirov@samsung.com> (raw)
In-Reply-To: <1398082604-3013-3-git-send-email-gautam.vivek@samsung.com>

Hello,

> -----Original Message-----
> From: Vivek Gautam [mailto:gautamvivek1987@gmail.com] On Behalf Of
> Vivek Gautam
> Sent: Monday, April 21, 2014 9:17 PM
> To: linux-usb@vger.kernel.org; linux-samsung-soc@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org; linux-omap@vger.kernel.org; linux-
> arm-kernel@lists.infradead.org; gregkh@linuxfoundation.org;
> stern@rowland.harvard.edu; balbi@ti.com; kgene.kim@samsung.com; Vivek
> Gautam; Anton Tikhomirov
> Subject: [PATCH 3/3] usb: dwc3-exynos: Make provision for vdd
> regulators
> 
> Facilitate getting required 3.3V and 1.0V VDD supply for
> DWC3 controller on Exynos.
> 
> With patches for regulators' nodes merged in 3.15:
> c8c253f ARM: dts: Add regulator entries to smdk5420
> 275dcd2 ARM: dts: add max77686 pmic node for smdk5250,
> 
> certain perripherals will now need to ensure that,
> they request VDD regulators in their drivers, and enable
> them so as to make them working.
> 
> Signed-off-by: Vivek Gautam <gautam.vivek@samsung.com>
> Cc: Anton Tikhomirov <av.tikhomirov@samsung.com>
> ---
> 
> Based on 'usb-next' branch of Greg's USB tree.
> Also cleanly applies on 'next' branch of Balbi's USB tree.
> 
>  drivers/usb/dwc3/dwc3-exynos.c |   51
> ++++++++++++++++++++++++++++++++++++++--
>  1 file changed, 49 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/usb/dwc3/dwc3-exynos.c b/drivers/usb/dwc3/dwc3-
> exynos.c
> index 28c8ad7..c9d9102 100644
> --- a/drivers/usb/dwc3/dwc3-exynos.c
> +++ b/drivers/usb/dwc3/dwc3-exynos.c
> @@ -27,6 +27,7 @@
>  #include <linux/usb/usb_phy_gen_xceiv.h>
>  #include <linux/of.h>
>  #include <linux/of_platform.h>
> +#include <linux/regulator/consumer.h>
> 
>  struct dwc3_exynos {
>  	struct platform_device	*usb2_phy;
> @@ -34,6 +35,8 @@ struct dwc3_exynos {
>  	struct device		*dev;
> 
>  	struct clk		*clk;
> +	struct regulator	*vdd33;
> +	struct regulator	*vdd10;
>  };
> 
>  static int dwc3_exynos_register_phys(struct dwc3_exynos *exynos)
> @@ -144,20 +147,46 @@ static int dwc3_exynos_probe(struct
> platform_device *pdev)
> 
>  	clk_prepare_enable(exynos->clk);
> 
> +	exynos->vdd33 = devm_regulator_get(dev, "vdd33");
> +	if (IS_ERR(exynos->vdd33)) {
> +		ret = PTR_ERR(exynos->vdd33);
> +		goto err2;

Is regulator property mandatory for dwc3-exynos? If it is not
and device tree doesn't provide it, dwc3-exynos driver probe shouldn't
fail here.

> +	}
> +	ret = regulator_enable(exynos->vdd33);
> +	if (ret) {
> +		dev_err(dev, "Failed to enable VDD33 supply\n");
> +		goto err2;
> +	}
> +

Thanks


  reply	other threads:[~2014-04-23  9:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-21 12:16 [PATCH 1/3] usb: ohci-exynos: Make provision for vdd regulators Vivek Gautam
2014-04-21 12:16 ` [PATCH 2/3] usb: ehci-exynos: " Vivek Gautam
2014-04-23 12:44   ` Jingoo Han
2014-04-21 12:16 ` [PATCH 3/3] usb: dwc3-exynos: " Vivek Gautam
2014-04-23  9:26   ` Anton Tikhomirov [this message]
2014-04-23  9:51     ` Vivek Gautam
2014-04-23 10:57       ` Anton Tikhomirov
2014-04-23 11:06         ` Vivek Gautam
2014-04-23 12:31           ` Jingoo Han
2014-04-23 12:43 ` [PATCH 1/3] usb: ohci-exynos: " Jingoo Han
2014-04-24  0:18 ` Anton Tikhomirov
2014-04-24  0:32   ` Jingoo Han
2014-04-24  1:26     ` Jingoo Han
2014-04-24  6:40       ` Vivek Gautam
2014-04-24  6:57         ` Jingoo Han
2014-04-24  0:38   ` Anton Tikhomirov
2014-04-24  6:32     ` Vivek Gautam

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='00bf01cf5ed6$28de18d0$7a9a4a70$%tikhomirov@samsung.com' \
    --to=av.tikhomirov@samsung.com \
    --cc=balbi@ti.com \
    --cc=gautam.vivek@samsung.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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