From: peter.chen@freescale.com (Peter Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/2] usb: change clock information for chipidea
Date: Tue, 20 Oct 2015 14:58:37 +0800 [thread overview]
Message-ID: <1445324319-19063-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.
Fabio, would you please help to test again, I am sorry to let you
test again.
Changes for v5:
- Using one line code for two devm_clk_get error message
- disable clocks should be inverse with enable clocks
Changes for v4:
- Following Rob Herring suggestion, if the platforms can get
clock using their dev_id, then, they are legacy platforms which
need three clocks to let controller work. If the dev_id is NULL,
then it only needs one clock.
- Only includes bug fix patches in this set, for new changes, will
through the next-tree.
Changes for v3:
- Delete property "needs-three-clocks", and using of_device_id->data
to differentiate platforms
- change <stable@vger.kernel.org> #v3.19+ to <stable@vger.kernel.org> #v4.1+
Changes for v2:
- Add imx25 & imx27 dts change
- Add Fabio's tested-by and Cc: <stable@vger.kernel.org> #v3.19+
- Some typo and commit description
Peter Chen (2):
ARM: dts: imx27.dtsi: change the clock information for usb
usb: chipidea: imx: refine clock operations to adapt for all platforms
arch/arm/boot/dts/imx27.dtsi | 16 +++--
drivers/usb/chipidea/ci_hdrc_imx.c | 131 ++++++++++++++++++++++++++++++++-----
2 files changed, 125 insertions(+), 22 deletions(-)
--
1.9.1
next reply other threads:[~2015-10-20 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 6:58 Peter Chen [this message]
2015-10-20 6:58 ` [PATCH v5 1/2] ARM: dts: imx27.dtsi: change the clock information for usb Peter Chen
2015-10-20 6:58 ` [PATCH v5 2/2] 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=1445324319-19063-1-git-send-email-peter.chen@freescale.com \
--to=peter.chen@freescale.com \
--cc=linux-arm-kernel@lists.infradead.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).