On Sat, Aug 1, 2015 at 3:17 AM, Gregory Fong <gregory.0...@gmail.com> wrote:
> For wake from S5, we need to: > - register a reboot handler > - set wakeup capability before requesting IRQ so wakeup count is > incremented > - mask all GPIO IRQs and clear any pending interrupts during driver > probe to since no driver will yet be registered to handle any IRQs > carried over from boot at that time, and it's possible that the > booted kernel does not request the same IRQ anyway. > > This means that /sys/.../power/wakeup_count is valid at boot time, and > we can properly account for S5 wakeup stats. e.g.: > > ### After waking from S5 from a GPIO key > # cat /sys/bus/platform/drivers/brcmstb-gpio/f04172c0.gpio/power/wakeup > enabled > # cat > /sys/bus/platform/drivers/brcmstb-gpio/f04172c0.gpio/power/wakeup_count > 1 > > Signed-off-by: Gregory Fong <gregory.0...@gmail.com> > --- > v4: rename __brcmstb_gpio_irq_set_wake() to brcmstb_gpio_priv_set_wake(). Patch applied. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
