Hi!
> +/**
> + * register_poweroff_handler_simple - Register function to be called to
> power off
> + * the system
> + * @handler: Function to be called to power off the system
> + * @priority: Handler priority. For priority guidelines see
> +
On Thu, Oct 09, 2014 at 12:31:43PM +0200, Pavel Machek wrote:
> Hi!
>
> > +/**
> > + * register_poweroff_handler_simple - Register function to be called to
> > power off
> > + *the system
> > + * @handler: Function to be called to power off the system
> >
On 10/09/2014 04:31 AM, Geert Uytterhoeven wrote:
> On Tue, Oct 7, 2014 at 7:28 AM, Guenter Roeck wrote:
>> +int register_poweroff_handler_simple(void (*handler)(void), int priority)
>> +{
>> + char symname[KSYM_NAME_LEN];
>> +
>> + if (poweroff_handler_data.handler) {
>> +
On Tue, Oct 7, 2014 at 7:28 AM, Guenter Roeck wrote:
> +int register_poweroff_handler_simple(void (*handler)(void), int priority)
> +{
> + char symname[KSYM_NAME_LEN];
> +
> + if (poweroff_handler_data.handler) {
> + lookup_symbol_name((unsigned
> long)poweroff_handler_d
Various drivers implement architecture and/or device specific means to
remove power from the system. For the most part, those drivers set the
global variable pm_power_off to point to a function within the driver.
This mechanism has a number of drawbacks. Typically only one scheme
to remove power
Hello
This seems exactly what I would need on the mc13783 to handle cleanly
the poweroff,
but after reading this patchset I have the following question:
[...]
> +/*
> + * Notifier list for kernel code which wants to be called
> + * to power off the system.
> + */
> +static ATOMIC_NOTIFIER_H
