[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091123110236.GB24326@rakim.wolfsonmicro.main>
Date: Mon, 23 Nov 2009 11:02:36 +0000
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Pavel Machek <pavel@....cz>
Cc: Linux-pm mailing list <linux-pm@...ts.osdl.org>,
kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [linux-pm] Null suspend/resume functions
On Sun, Nov 22, 2009 at 12:45:10AM +0100, Pavel Machek wrote:
> So you place a comment there; it should be there anyway. Having nop
> during suspend/resume *is* unusual, and it should raise red flags.
This isn't a good assumption here. Remember that this is for runtime PM
so if we're getting as far as these calls then the driver has already
told the core that it is idle, which probably means that the hardware is
already quieseced. For a lot of hardware that will mean that the only
thing left to do in order to suspend is to (possibly) remove power and
in many cases (as with SH) that's going to be done by the bus rather
than the device. It's a bit more likely that some activity will be
needed on resume but in many cases the device gets fully reprogrammed on
when it becomes active anyway.
Looking at it another way a key goal of runtime PM is to get the bus
involved in the process - if we can do things at device level to reduce
power consumption then there's no need to go through runtime PM to do
them.
> Plus, if we allowed NULLs there, we'd not know if the driver does not
> implement it because it is not neccessary, or because they don't care.
Again, in order to use runtime PM the driver must already be doing
explicit calls so it should be fairly clear that the driver is trying to
support suspend.
--
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