From: Peter Chen <peter.chen-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
pawel.moll-5wv7dgnIgG8@public.gmane.org,
Peter Chen <peter.chen-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Subject: [RESEND PATCH v3 0/5] usb: change clock information for chipidea
Date: Wed, 30 Sep 2015 10:25:20 +0800 [thread overview]
Message-ID: <1443579925-1330-1-git-send-email-peter.chen@freescale.com> (raw)
This patch set changes usb clock information for legacy i.mx platforms.
At these platforms, they needs three clocks to let controller work.
Hi Shawn,
Fabio has tested for both imx27 and imx25 platforms.
I have queued 1/5 and 5/5, would you please help to queue others,
thanks.
Changes for v3:
- Delete property "needs-three-clocks", and using of_device_id->data
to differentiate platforms
- change <stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> #v3.19+ to <stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> #v4.1+
Changes for v2:
- Add imx25 & imx27 dts change
- Add Fabio's tested-by and Cc: <stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> #v3.19+
- Some typo and commit description
Peter Chen (5):
doc: dt-binding: ci-hdrc-usb2: split vendor specific properties
ARM: dts: imx27.dtsi: change the clock information for usb
ARM: dts: imx25.dtsi: change the clock information for usb
ARM: dts: imx35.dtsi: change the clock information for usb
usb: chipidea: imx: refine clock operations to adapt for all platforms
.../devicetree/bindings/usb/ci-hdrc-usb2.txt | 10 +-
arch/arm/boot/dts/imx25.dtsi | 8 +-
arch/arm/boot/dts/imx27.dtsi | 16 ++-
arch/arm/boot/dts/imx35.dtsi | 8 +-
drivers/usb/chipidea/ci_hdrc_imx.c | 156 ++++++++++++++++++---
5 files changed, 164 insertions(+), 34 deletions(-)
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2015-09-30 2:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 2:25 Peter Chen [this message]
[not found] ` <1443579925-1330-1-git-send-email-peter.chen-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-09-30 2:25 ` [RESEND PATCH v3 1/5] doc: dt-binding: ci-hdrc-usb2: split vendor specific properties Peter Chen
2015-09-30 2:25 ` [RESEND PATCH v3 2/5] ARM: dts: imx27.dtsi: change the clock information for usb Peter Chen
2015-09-30 2:25 ` [RESEND PATCH v3 3/5] ARM: dts: imx25.dtsi: " Peter Chen
2015-09-30 2:25 ` [RESEND PATCH v3 4/5] ARM: dts: imx35.dtsi: " Peter Chen
2015-09-30 5:28 ` [RESEND PATCH v3 0/5] usb: change clock information for chipidea Shawn Guo
2015-09-30 6:24 ` Peter Chen
2015-09-30 6:48 ` Shawn Guo
2015-09-30 2:25 ` [RESEND PATCH v3 5/5] usb: chipidea: imx: refine clock operations to adapt for all platforms Peter Chen
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=1443579925-1330-1-git-send-email-peter.chen@freescale.com \
--to=peter.chen-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).