From: jason77.wang@gmail.com (jason wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] mx51/clock: add keypad clock definition and registration
Date: Wed, 2 Jun 2010 22:29:48 +0800 [thread overview]
Message-ID: <003c01cb0260$162f36a0$9b00a8c0@wuef10f27ebed8> (raw)
In-Reply-To: 20100602080054.GL2346@matterhorn.lan
<snip>
>> _REGISTER_CLOCK("fsl-usb2-udc", "usb_ahb", ahb_clk)
>> + _REGISTER_CLOCK(NULL, "kpp", kpp_clk)
>
> Should be
>
> _REGISTER_CLOCK("imx-keypad", NULL, kpp_clk)
>
> since that is the device id that will be used in your platform device.
>
Accept, will be fixed in V2.
Thanks,
Jason.
> --
> ----------------------------------------------------------------------
> Amit Kucheria, Kernel Engineer || amit.kucheria at canonical.com
> ----------------------------------------------------------------------
next prev parent reply other threads:[~2010-06-02 14:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 15:10 [PATCH 0/3]Add i.MX51 3-stack board support Jason Wang
2010-06-01 15:10 ` [PATCH 1/3] mxc: Add support for the imx51 3-stack board Jason Wang
2010-06-01 15:10 ` [PATCH 2/3] mxc/iomux: add GPIO bank offset for iomux v3 platforms Jason Wang
2010-06-01 15:10 ` [PATCH 3/3] mx51/clock: add keypad clock definition and registration Jason Wang
2010-06-01 15:56 ` Fabio Estevam
2010-06-02 13:55 ` jason wang
2010-06-02 7:43 ` Sascha Hauer
2010-06-02 14:28 ` [PATCH 3/3] mx51/clock: add keypad clock definition andregistration jason wang
2010-06-02 8:00 ` [PATCH 3/3] mx51/clock: add keypad clock definition and registration Amit Kucheria
2010-06-02 14:29 ` jason wang [this message]
2010-06-01 15:35 ` [PATCH 1/3] mxc: Add support for the imx51 3-stack board Fabio Estevam
2010-06-02 13:53 ` jason wang
2010-06-02 7:36 ` Sascha Hauer
2010-06-02 13:08 ` Rob Herring
2010-06-02 14:27 ` jason wang
2010-06-02 17:23 ` Sascha Hauer
2010-06-03 0:01 ` jason
2010-06-02 8:38 ` Amit Kucheria
2010-06-02 8:52 ` Sascha Hauer
2010-06-02 14:36 ` jason wang
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='003c01cb0260$162f36a0$9b00a8c0@wuef10f27ebed8' \
--to=jason77.wang@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).