From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv1] ARM: imx: Add support for low power suspend on MX51.
Date: Thu, 3 Mar 2011 21:15:13 +0100 [thread overview]
Message-ID: <20110303201513.GU22310@pengutronix.de> (raw)
In-Reply-To: <20110303134551.GC25891@n2100.arm.linux.org.uk>
On Thu, Mar 03, 2011 at 01:45:51PM +0000, Russell King - ARM Linux wrote:
> On Thu, Mar 03, 2011 at 01:46:58PM +0100, Uwe Kleine-K?nig wrote:
> > On Thu, Mar 03, 2011 at 11:52:42AM +0000, Russell King - ARM Linux wrote:
> > > On Wed, Mar 02, 2011 at 10:52:38PM +0100, Uwe Kleine-K?nig wrote:
> > > > > +static int __init mx5_pm_init(void)
> > > > > +{
> > > > > + if (cpu_is_mx51())
> > > > > + suspend_set_ops(&mx5_suspend_ops);
> > > > I'd prefer to have that called by imx51_init_early.
> > >
> > > This function name looks fine. As we now have an init_early in the
> > > arch hooks, let's keep things called foo_init_early() to that use
> > > and not start using 'early' for stuff used from initcalls.
> > >
> > > Renaming this is a recipe for causing confusion and having grep hit
> > > false positives. Please leave it as is.
> > It seems you and Thomas both didn't notice the "by" in my sentence.
> > Or maybe it's not proper English? The thing I wanted to express is that
> > instead of introducing another initcall I prefer that imx51_init_early
> > calls mx5_pm_init instead. The name mx5_pm_init is fine for me, though
> > imx51_pm_init would still be better.
>
> Is there a reason to set this really really early? What's that reason
> exactly?
No there is no reason. If there were a imx51_init this would be the
right place. Maybe it's time to implement it.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2011-03-03 20:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 17:17 [PATCHv1] ARM: imx: Add support for low power suspend on MX51 Dinh.Nguyen at freescale.com
2011-03-02 19:35 ` Arnaud Patard (Rtp)
2011-03-02 19:41 ` Nguyen Dinh-R00091
2011-03-02 21:52 ` Uwe Kleine-König
2011-03-02 23:51 ` Thomas Gleixner
2011-03-03 9:35 ` Uwe Kleine-König
2011-03-03 11:02 ` Thomas Gleixner
2011-03-03 11:49 ` Uwe Kleine-König
2011-03-03 11:52 ` Russell King - ARM Linux
2011-03-03 12:46 ` Uwe Kleine-König
2011-03-03 13:45 ` Russell King - ARM Linux
2011-03-03 20:15 ` Uwe Kleine-König [this message]
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=20110303201513.GU22310@pengutronix.de \
--to=u.kleine-koenig@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).