On Mon, 06 Oct 2014, Guenter Roeck wrote:
Register with kernel poweroff handler instead of setting pm_power_off
directly. Register with a low priority value of 64 to reflect that
the original code only sets pm_power_off if it was not already set.
Make twl4030_power_off static as it is only
On Mon, 06 Oct 2014, Guenter Roeck wrote:
Register with kernel poweroff handler instead of setting pm_power_off
directly. Register with a low priority value of 64 to reflect that
the original code only sets pm_power_off if it was not already set.
Cc: Linus Walleij linus.wall...@linaro.org
On 07/10/2014 07:28, Guenter Roeck :
Register with kernel poweroff handler instead of setting pm_power_off
directly. Always use register_poweroff_handler_simple as there is no
indication that more than one poweroff handler is registered.
If the poweroff handler only resets the system or puts
On Tue, Oct 7, 2014 at 7:28 AM, Guenter Roeck li...@roeck-us.net wrote:
Replace mach_power_off with pm_power_off to simplify the subsequent
move of pm_power_off to generic code.
Thanks!
Cc: Geert Uytterhoeven ge...@linux-m68k.org
Cc: Greg Ungerer g...@uclinux.org
Cc: Joshua Thompson
On Tue, Oct 07, 2014 at 06:28:07AM +0100, Guenter Roeck wrote:
Devicetree bindings are supposed to be operating system independent
and should thus not describe how a specific functionality is implemented
in Linux.
Cc: Rob Herring robh...@kernel.org
Cc: Pawel Moll pawel.m...@arm.com
Cc:
On Tue, Oct 07, 2014 at 06:28:09AM +0100, Guenter Roeck wrote:
Replace reference to pm_power_off (which is an implementation detail)
and replace it with a more generic description of the driver's functionality.
Cc: Rob Herring robh...@kernel.org
Cc: Pawel Moll pawel.m...@arm.com
Cc: Mark
On Tue, Oct 07, 2014 at 06:28:08AM +0100, Guenter Roeck wrote:
pm_power_off is an implementation detail. Replace it with a more generic
description of the driver's functionality.
Cc: Rob Herring robh...@kernel.org
Cc: Pawel Moll pawel.m...@arm.com
Cc: Mark Rutland mark.rutl...@arm.com
On Mon, Oct 06, 2014 at 10:28:08PM -0700, Guenter Roeck wrote:
pm_power_off is an implementation detail. Replace it with a more generic
description of the driver's functionality.
Cc: Rob Herring robh...@kernel.org
Cc: Pawel Moll pawel.m...@arm.com
Cc: Mark Rutland mark.rutl...@arm.com
On Mon, Oct 06, 2014 at 10:28:09PM -0700, Guenter Roeck wrote:
Replace reference to pm_power_off (which is an implementation detail)
and replace it with a more generic description of the driver's functionality.
Acked-by: Andrew Lunn and...@lunn.ch
Thanks
Andrew
Cc: Rob Herring
On Tue, Oct 07, 2014 at 12:02:19PM +0100, Mark Rutland wrote:
On Tue, Oct 07, 2014 at 06:28:09AM +0100, Guenter Roeck wrote:
Replace reference to pm_power_off (which is an implementation detail)
and replace it with a more generic description of the driver's
functionality.
Cc: Rob
On Mon, Oct 06, 2014 at 10:28:23PM -0700, Guenter Roeck wrote:
Register with kernel poweroff handler instead of setting pm_power_off
directly. Register with a low priority value of 64 to reflect that
the original code only sets pm_power_off if it was not already set.
Other changes:
Drop
On Mon, Oct 06, 2014 at 10:28:25PM -0700, Guenter Roeck wrote:
Register with kernel poweroff handler instead of setting pm_power_off
directly. Register with default priority value of 128 to reflect that
the original code generates an error if another poweroff handler has
already been
On Mon, Oct 06, 2014 at 10:28:22PM -0700, Guenter Roeck wrote:
Register with kernel poweroff handler instead of seting pm_power_off
directly. Register as poweroff handler of last resort since the driver
does not really power off the system but executes a restart.
I would not say last resort,
On 10/07/14 00:28, Guenter Roeck wrote:
Devicetree bindings are supposed to be operating system independent
and should thus not describe how a specific functionality is implemented
in Linux.
So your argument is that linux/Documentation/devicetree/bindings should
not be specific to Linux.
On Mon, Oct 06, 2014 at 10:28:31PM -0700, Guenter Roeck wrote:
Register with kernel poweroff handler instead of setting pm_power_off
directly. Register with default priority value of 128 since we don't know
any better.
Cc: Julian Andres Klode j...@jak-linux.org
Cc: Marc Dietrich
On Tue, Oct 07, 2014 at 11:21:11AM -0500, Rob Landley wrote:
On 10/07/14 00:28, Guenter Roeck wrote:
Devicetree bindings are supposed to be operating system independent
and should thus not describe how a specific functionality is implemented
in Linux.
So your argument is that
On Tue, Oct 07, 2014 at 05:21:11PM +0100, Rob Landley wrote:
On 10/07/14 00:28, Guenter Roeck wrote:
Devicetree bindings are supposed to be operating system independent
and should thus not describe how a specific functionality is implemented
in Linux.
So your argument is that
On 10/07/2014 09:31 AM, Guenter Roeck wrote:
On Tue, Oct 07, 2014 at 11:21:11AM -0500, Rob Landley wrote:
On 10/07/14 00:28, Guenter Roeck wrote:
Devicetree bindings are supposed to be operating system independent
and should thus not describe how a specific functionality is implemented
in
On 10/07/14 11:59, David Daney wrote:
On 10/07/2014 09:31 AM, Guenter Roeck wrote:
On Tue, Oct 07, 2014 at 11:21:11AM -0500, Rob Landley wrote:
On 10/07/14 00:28, Guenter Roeck wrote:
Devicetree bindings are supposed to be operating system independent
and should thus not describe how a
On Monday, October 06, 2014 10:28:05 PM Guenter Roeck wrote:
Poweroff handlers may now be installed with register_poweroff_handler.
Use the new API function have_kernel_poweroff to determine if a poweroff
handler has been installed.
Cc: Rafael J. Wysocki r...@rjwysocki.net
Cc: Pavel Machek
On Monday, October 06, 2014 10:28:46 PM Guenter Roeck wrote:
No users of pm_power_off are left, so it is safe to remove the function.
Cc: Rafael J. Wysocki r...@rjwysocki.net
Cc: Pavel Machek pa...@ucw.cz
Cc: Len Brown len.br...@intel.com
Signed-off-by: Guenter Roeck li...@roeck-us.net
ACK
21 matches
Mail list logo
