From: Kevin Hilman <khilman@deeprootsystems.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.arm.linux.org.uk, linux-omap@vger.kernel.org
Subject: Re: [PATCH 02/13] OMAP2/3: PM: push core PM code from linux-omap
Date: Thu, 28 May 2009 09:51:18 -0700 [thread overview]
Message-ID: <87y6shp3w9.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20090528154823.GD20736@n2100.arm.linux.org.uk> (Russell King's message of "Thu\, 28 May 2009 16\:48\:23 +0100")
Russell King - ARM Linux <linux@arm.linux.org.uk> writes:
> On Wed, May 20, 2009 at 04:19:25PM -0700, Kevin Hilman wrote:
>> This patch is to sync the core linux-omap PM code with mainline. This
>> code has evolved and been used for a while the linux-omap tree, but
>> the attempt here is to finally get this into mainline.
>
> Hmm..
>
>> +static int __init omap_pm_init(void)
>> {
>> - return 0;
>> + int error = -1;
>> +
>> + if (cpu_is_omap24xx())
>> + error = omap2_pm_init();
>> + if (cpu_is_omap34xx())
>> + error = omap3_pm_init();
>
> Experience with PXA has shown that this tends to be the wrong way up
> of doing things. It seems to be much better to have the SoC specific
> code call the SoC generic code instead.
OK.
> So, eg, omap2_pm_init() becomes:
>
> static int omap2_pm_init(void)
> {
> if (!cpu_is_omap24xx())
> return -ENODEV;
>
> ... omap24xx initialisation ...
>
> return omap_pm_init();
> }
> late_initcall(omap2_pm_init);
>
> (and, since this is always built-in, there's no point doing cleanup if
> omap_pm_init() fails - you're not going to be able to re-run that
> initialization again.)
Sounds good, I'll make this change and upate the pm-upstream branch
for Tony.
This will leave the common omap_pm_init() and pm.c basically empty, so
I'll just remove them.
Kevin
next prev parent reply other threads:[~2009-05-28 16:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 23:19 [PATCH v2 00/13] OMAP2/3: PM sync-up Kevin Hilman
2009-05-20 23:19 ` [PATCH 01/13] Revert "ARM: OMAP: Mask interrupts when disabling interrupts, v2" Kevin Hilman
2009-05-20 23:19 ` [PATCH 02/13] OMAP2/3: PM: push core PM code from linux-omap Kevin Hilman
2009-05-20 23:19 ` [PATCH 03/13] OMAP: Add new function to check wether there is irq pending Kevin Hilman
2009-05-20 23:19 ` [PATCH 04/13] OMAP3: PM: Force IVA2 into idle during bootup Kevin Hilman
2009-05-20 23:19 ` [PATCH 05/13] OMAP3: PM: Add wake-up bit defintiions for CONTROL_PADCONF_X Kevin Hilman
2009-05-20 23:19 ` [PATCH 06/13] OMAP3: PM: UART: disable clocks when idle and off-mode support Kevin Hilman
2009-05-20 23:19 ` [PATCH 07/13] OMAP: UART: Add sysfs interface for adjusting UART sleep timeout Kevin Hilman
2009-05-20 23:19 ` [PATCH 08/13] OMAP3: PM: Add D2D clocks and auto-idle setup to PRCM init Kevin Hilman
2009-05-20 23:19 ` [PATCH 09/13] OMAP3: PM: D2D clockdomain supports SW supervised transitions Kevin Hilman
2009-05-20 23:19 ` [PATCH 10/13] OMAP3: PM: Ensure MUSB block can idle when driver not loaded Kevin Hilman
2009-05-20 23:19 ` [PATCH 11/13] OMAP3: PM: Ensure PRCM interrupts are cleared at boot Kevin Hilman
2009-05-20 23:19 ` [PATCH 12/13] OMAP3: PM: Clear pending PRCM reset flags on init Kevin Hilman
2009-05-20 23:19 ` [PATCH 13/13] OMAP3: PM: prevent module wakeups from waking IVA2 Kevin Hilman
2009-05-28 15:48 ` [PATCH 02/13] OMAP2/3: PM: push core PM code from linux-omap Russell King - ARM Linux
2009-05-28 16:51 ` Kevin Hilman [this message]
2009-05-28 18:22 ` Kevin Hilman
2009-05-21 23:38 ` [PATCH 01/13] Revert "ARM: OMAP: Mask interrupts when disabling interrupts, v2" Kim Kyuwon
2009-05-22 14:54 ` Kevin Hilman
2009-05-22 15:51 ` Kim Kyuwon
2009-05-22 18:16 ` Kevin Hilman
2009-05-22 22:59 ` Kim Kyuwon
2009-05-25 5:33 ` Kim Kyuwon
2009-05-22 23:22 ` Russell King - ARM Linux
2009-05-23 0:47 ` Kim Kyuwon
2009-05-26 23:12 ` [PATCH v2 00/13] OMAP2/3: PM sync-up Tony Lindgren
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=87y6shp3w9.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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