From: Vivek Gautam <gautam.vivek@samsung.com>
To: linux-usb@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
gregkh@linuxfoundation.org, balbi@ti.com,
rob.herring@calxeda.com, kgene.kim@samsung.com,
thomas.abraham@linaro.org, dianders@chromium.org
Subject: [PATCH 0/2] dwc3: exynos: Device tree fixes
Date: Thu, 14 Mar 2013 16:14:56 +0530 [thread overview]
Message-ID: <1363257898-17504-1-git-send-email-gautam.vivek@samsung.com> (raw)
This patch-set modifies dwc3-exynos as per latest bindings
available for dwc3. Now the dwc3 core also has device support,
there's no need to add platform device for core in glue layers.
This change has come as a result of discussion happened in:
[PATCH RFC] usb: dwc3: Get PHY from platform specific dwc3 dt node.
Additionally, now that Samsung exynos series has moved to common
clock framework, we use clock_prepare_enable() and clock_disable_unprepare()
APIs.
Some cleanup is also done here.
Based on 'usb-next' plus Felipe's 'testing' branch patches;
(some 194 patches in fact ;-), on top of 3.9rc2 tag).
Also based on: "usb: dwc3: set dma_mask for dwc3_omap device" by Kishon
in which DMA mask for dwc3-core is being set from its parent.
Vivek Gautam (2):
usb: dwc3: exynos: Use of_platform API to create dwc3 core pdev
usb: dwc3: exynos: use clk_prepare_enable and clk_disable_unprepare
drivers/usb/dwc3/dwc3-exynos.c | 54 ++++++++++++++--------------------------
1 files changed, 19 insertions(+), 35 deletions(-)
--
1.7.6.5
next reply other threads:[~2013-03-14 10:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 10:44 Vivek Gautam [this message]
2013-03-14 10:44 ` [PATCH 1/2] usb: dwc3: exynos: Use of_platform API to create dwc3 core pdev Vivek Gautam
2013-03-14 10:51 ` Felipe Balbi
2013-03-14 12:10 ` Vivek Gautam
2013-03-14 12:39 ` [PATCH v2 " Vivek Gautam
2013-03-14 10:44 ` [PATCH 2/2] usb: dwc3: exynos: use clk_prepare_enable and clk_disable_unprepare Vivek Gautam
2013-03-14 10:53 ` Felipe Balbi
2013-03-15 6:06 ` Vivek Gautam
2013-03-15 7:42 ` Felipe Balbi
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=1363257898-17504-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=gregkh@linuxfoundation.org \
--cc=kgene.kim@samsung.com \
--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=rob.herring@calxeda.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
all inboxes | Powered by JetHome®