From: Vivek Gautam <gautam.vivek@samsung.com>
To: linux-samsung-soc@vger.kernel.org
Cc: devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
kgene.kim@samsung.com, grant.likely@secretlab.ca,
dianders@chromium.org, balbi@ti.com, thomas.abraham@linaro.org,
sylvester.nawrocki@gmail.com, tomasz.figa@gmail.com,
p.paneri@samsung.com
Subject: [PATCH v2 0/2] ARM: Exynos5250: Enabling samsung usb phy
Date: Tue, 22 Jan 2013 21:01:18 +0530 [thread overview]
Message-ID: <1358868680-5757-1-git-send-email-gautam.vivek@samsung.com> (raw)
Changes from v1:
- Putting separate device nodes for usb 2.0 phy and usb 3.0 phy
based on separate driver for samsung usb 3.0 phy and
samsung usb 2.0 phy:
[PATCH v3 0/2] Adding USB 3.0 DRD-phy support for exynos5250
[PATCH v8 0/4] Adding usb2.0 host-phy support for exynos5250
- Aligning as per the patch:
usb: phy: samsung: Add support to set pmu isolation
- Replaced phy-handle approach for PHY CONTROL registers
to child nodes.
- Removing AUX data entry from exynos5250 dt file.
Vivek Gautam (2):
ARM: Exynos5250: Enabling samsung-usbphy driver
ARM: Exynos5250: Enabling samsung-usb3-phy driver
arch/arm/boot/dts/exynos5250.dtsi | 28 ++++++++++++++++++++++++++++
1 files changed, 28 insertions(+), 0 deletions(-)
--
1.7.6.5
next reply other threads:[~2013-01-22 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 15:31 Vivek Gautam [this message]
2013-01-22 15:31 ` [PATCH v2 1/2] ARM: Exynos5250: Enabling samsung-usbphy driver Vivek Gautam
2013-01-30 5:06 ` Kukjin Kim
2013-01-30 8:19 ` Vivek Gautam
2013-01-22 15:31 ` [PATCH v2 2/2] ARM: Exynos5250: Enabling samsung-usb3-phy driver Vivek Gautam
[not found] ` <1358868680-5757-3-git-send-email-gautam.vivek-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-01-30 5:12 ` Kukjin Kim
2013-01-29 12:10 ` [PATCH v2 0/2] ARM: Exynos5250: Enabling samsung usb phy 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=1358868680-5757-1-git-send-email-gautam.vivek@samsung.com \
--to=gautam.vivek@samsung.com \
--cc=balbi@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dianders@chromium.org \
--cc=grant.likely@secretlab.ca \
--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=thomas.abraham@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).