Hi,

On Mon, Jul 16, 2012 at 11:27:39AM +0530, Vivek Gautam wrote:
> This patch retrieves and configures the vbus control gpio via
> the device tree. The suspend/resume callbacks will be later
> modified for vbus control.
> 
> Signed-off-by: Abhilash Kesavan <a.kesa...@samsung.com>
> Signed-off-by: Vivek Gautam <gautam.vi...@samsung.com>
> ---
>  drivers/usb/dwc3/dwc3-exynos.c |   25 +++++++++++++++++++++++++
>  1 files changed, 25 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/usb/dwc3/dwc3-exynos.c b/drivers/usb/dwc3/dwc3-exynos.c
> index a293c69..9b0238f 100644
> --- a/drivers/usb/dwc3/dwc3-exynos.c
> +++ b/drivers/usb/dwc3/dwc3-exynos.c
> @@ -20,6 +20,7 @@
>  #include <linux/dma-mapping.h>
>  #include <linux/clk.h>
>  #include <linux/of.h>
> +#include <linux/of_gpio.h>
>  
>  #include "core.h"
>  
> @@ -30,6 +31,28 @@ struct dwc3_exynos {
>       struct clk              *clk;
>  };
>  
> +static int dwc3_setup_vbus_gpio(struct platform_device *pdev)
> +{
> +     int err;
> +     int gpio;
> +
> +     if (!pdev->dev.of_node)
> +             return 0;
> +
> +     gpio = of_get_named_gpio(pdev->dev.of_node,
> +                             "samsung,vbus-gpio", 0);
> +     if (!gpio_is_valid(gpio))
> +             return 0;
> +
> +     err = gpio_request_one(gpio, GPIOF_OUT_INIT_HIGH, "dwc3_vbus_gpio");
> +     if (err) {
> +             dev_err(&pdev->dev, "can't request dwc3 vbus gpio %d", gpio);
> +             return err;
> +     }
> +
> +     return err;
> +}
> +
>  static u64 dwc3_exynos_dma_mask = DMA_BIT_MASK(32);
>  
>  static int __devinit dwc3_exynos_probe(struct platform_device *pdev)
> @@ -58,6 +81,8 @@ static int __devinit dwc3_exynos_probe(struct 
> platform_device *pdev)
>       if (!pdev->dev.coherent_dma_mask)
>               pdev->dev.coherent_dma_mask = DMA_BIT_MASK(32);
>  
> +     dwc3_setup_vbus_gpio(pdev);

I think this should be handled by the gpio-vbus transceiver. No ?

-- 
balbi

Attachment: signature.asc
Description: Digital signature

_______________________________________________
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss

Reply via email to