From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ARM: IMX5: cpuidle driver
Date: Thu, 17 Feb 2011 11:54:15 +0100 [thread overview]
Message-ID: <20110217105415.GB24426@pengutronix.de> (raw)
In-Reply-To: <AANLkTim_7HiWutTyTuWvAR5sx1Nd7HdSyhfwRjS2CfYg@mail.gmail.com>
On Thu, Feb 17, 2011 at 09:18:11AM +0100, Yong Shen wrote:
> >
> >
> > > + return 0;
> > > +}
> > > +
> > > +late_initcall(imx_cpuidle_init);
> >
> > We have a late_initcall here which needs to be protected from other
> > cpus. On the other hand we depend on board code calling
> > imx_cpuidle_board_params() before this initcall. I think the board code
> > should call a imx_cpuidle_init(struct imx_cpuidle_params
> > *cpuidle_params) instead which makes the flow of execution more clear.
> >
> > imx_cpuidle_init can not be called directly in board code, since it is too
> early to register cpuidle driver and device which depend on some other
> system resource.
I see. Maybe we should make this a platform driver then like for example
davinci does.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2011-02-17 10:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 9:36 [PATCH v2 0/2] ARM: IMX5: cpuidle driver yong.shen at linaro.org
2011-02-11 9:36 ` [PATCH v2 1/2] " yong.shen at linaro.org
2011-02-15 18:27 ` Sascha Hauer
2011-02-16 8:02 ` Yong Shen
2011-02-17 8:18 ` Yong Shen
2011-02-17 10:54 ` Sascha Hauer [this message]
2011-02-20 14:58 ` Yong Shen
2011-02-23 15:41 ` [PATCH v3 " Yong Shen
2011-02-16 8:11 ` [PATCH v2 " Sascha Hauer
2011-02-16 8:37 ` Yong Shen
2011-02-16 9:13 ` Sascha Hauer
2011-02-16 9:25 ` Yong Shen
2011-02-11 9:36 ` [PATCH v2 2/2] ARM: IMX5 bbg: add cpuidle parameters yong.shen at linaro.org
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=20110217105415.GB24426@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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).