devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vivek Gautam <gautam.vivek@samsung.com>
To: linux-usb@vger.kernel.org
Cc: devicetree-discuss@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	gregkh@linuxfoundation.org, balbi@ti.com, kgene.kim@samsung.com,
	thomas.abraham@linaro.org, t.figa@samsung.com,
	ben-linux@fluff.org, broonie@opensource.wolfsonmicro.com,
	l.majewski@samsung.com, kyungmin.park@samsung.com,
	grant.likely@secretlab.ca, heiko@sntech.de, p.paneri@samsung.com
Subject: [PATCH] usb: phy: samsung: Add support to set pmu isolation
Date: Tue, 18 Dec 2012 11:26:06 +0530	[thread overview]
Message-ID: <1355810167-18425-1-git-send-email-gautam.vivek@samsung.com> (raw)

Based on patches for samsung-usbphy driver available at:
https://patchwork.kernel.org/patch/1794651/

In this patch we are adding support to parse device tree data for
samsung-usbphy driver and further setting pmu_isolation to
enable/disable phy as and when needed.
This further chucks out the need of platform data for samsung-usbphy on
DT enabled system and hence serves the purpose of the discussion
in the thread for:
[PATCH v8 2/2] usb: s3c-hsotg: Adding phy driver support

Vivek Gautam (1):
  usb: phy: samsung: Add support to set pmu isolation

 .../devicetree/bindings/usb/samsung-usbphy.txt     |   10 +++
 drivers/usb/phy/samsung-usbphy.c                   |   80 ++++++++++++++++++--
 2 files changed, 82 insertions(+), 8 deletions(-)

-- 
1.7.6.5

             reply	other threads:[~2012-12-18  5:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18  5:56 Vivek Gautam [this message]
     [not found] ` <1355810167-18425-1-git-send-email-gautam.vivek-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2012-12-18  5:56   ` [PATCH] usb: phy: samsung: Add support to set pmu isolation Vivek Gautam
2012-12-18 13:56     ` [PATCH v2] " Vivek Gautam
     [not found]       ` <1355838966-11269-1-git-send-email-gautam.vivek-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2012-12-18 23:19         ` Sylwester Nawrocki
     [not found]           ` <50D0F9EA.9090002-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-19  5:35             ` Vivek Gautam
2012-12-19 13:44               ` Vivek Gautam
2012-12-19 20:28                 ` Sylwester Nawrocki
  -- strict thread matches above, loose matches on Subject: below --
2013-01-11  8:08 [PATCH] " Vivek Gautam
2013-01-11  9:21 ` Sylwester Nawrocki
     [not found]   ` <50EFD9B3.7090503-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-01-11  9:55     ` Vivek Gautam
2013-01-14 22:11 ` Doug Anderson
2013-01-15  5:38   ` 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=1355810167-18425-1-git-send-email-gautam.vivek@samsung.com \
    --to=gautam.vivek@samsung.com \
    --cc=balbi@ti.com \
    --cc=ben-linux@fluff.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko@sntech.de \
    --cc=kgene.kim@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=l.majewski@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --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=t.figa@samsung.com \
    --cc=thomas.abraham@linaro.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;
as well as URLs for NNTP newsgroup(s).