[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110209115837.GA12333@opensource.wolfsonmicro.com>
Date: Wed, 9 Feb 2011 11:58:37 +0000
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Frank Rowand <frank.rowand@...sony.com>
Cc: Ingo Molnar <mingo@...e.hu>, "Rafael J. Wysocki" <rjw@...k.pl>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Len Brown <len.brown@...el.com>,
Alan Stern <stern@...land.harvard.edu>,
linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
linux-embedded@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] Remove CONFIG_PM altogether, enable power management
all the time
On Wed, Feb 09, 2011 at 11:41:37AM +0000, Mark Brown wrote:
> Hrm, that's pretty surprising. It'd be interesting to know how much of
> that is due to the PM core itself and how much of that is from drivers.
> For the drivers CONFIG_PM isn't really the option they should be using
> in the first place - they mostly want some combination of PM_SLEEP and
> PM_RUNTIME for the specific functionality. I'm running some checks now.
OK, on ARM with slightly more than an allnoconfig (allnoconfig itself
wouldn't build) I see:
text data bss dec hex filename
1361476 71360 167320 1600156 186a9c vmlinux.nopm
1364228 71520 167480 1603228 18769c vmlinux
2752 160 160 3072
so 3K from CONFIG_PM there, mostly from the ARM VIC management code
which I suspect really wants to be under one of the more specific PM
options, though obviously this comes back to the issue with bitrotted
ifdefs for PM whcih pervades the kernel.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists