From: festevam@gmail.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: mxs: Register USB clocks for mx23
Date: Sun, 5 Aug 2012 14:08:07 -0300 [thread overview]
Message-ID: <CAOMZO5AaLKN9bhuPRLJkA8ytiwVi_yrpwzL0mJAzf6VS4PSRLQ@mail.gmail.com> (raw)
In-Reply-To: <20120620143830.GF2253@S2101-09.ap.freescale.net>
On Wed, Jun 20, 2012 at 11:38 AM, Shawn Guo <shawn.guo@linaro.org> wrote:
...
>> + clk_register_clkdev(clks[usb_pwr], NULL, "8007c000.usbphy");
>> + clk_register_clkdev(clks[usb], NULL, "80080000.usb");
>
> It depends on the node name in device tree. I would defer this
> a little bit to have the node name in dts settled down first.
Now that the mxs usb driver is in mainline, could this patch be applied?
Regards,
Fabio Estevam
next prev parent reply other threads:[~2012-08-05 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 23:26 [PATCH] clk: mxs: Register USB clocks for mx23 Fabio Estevam
2012-06-20 14:38 ` Shawn Guo
2012-08-05 17:08 ` Fabio Estevam [this message]
2012-08-06 3:00 ` Shawn Guo
2012-08-13 3:06 ` Fabio Estevam
2012-08-30 14:09 ` Fabio Estevam
2012-08-30 21:01 ` Shawn Guo
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=CAOMZO5AaLKN9bhuPRLJkA8ytiwVi_yrpwzL0mJAzf6VS4PSRLQ@mail.gmail.com \
--to=festevam@gmail.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).