On Mon, Jul 13, 2015 at 6:03 AM, Linus Walleij wrote:
> On Thu, Jun 18, 2015 at 3:00 AM, Gregory Fong 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
On Thu, Jun 18, 2015 at 3:00 AM, Gregory Fong 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
On Thu, Jun 18, 2015 at 3:00 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
On Mon, Jul 13, 2015 at 6:03 AM, Linus Walleij linus.wall...@linaro.org wrote:
On Thu, Jun 18, 2015 at 3:00 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
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
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
6 matches
Mail list logo