On Thursday, August 28, 2014 11:23:11 AM Thomas Gleixner wrote:
> On Thu, 28 Aug 2014, Rafael J. Wysocki wrote:
> > On Wednesday, August 27, 2014 10:32:23 PM Thomas Gleixner wrote:
> > > void suspend_device_irqs(void)
> > > {
> > > for_each_irq_desc(irq, desc) {
> > > /* Disable the
On Thu, 28 Aug 2014, Rafael J. Wysocki wrote:
> On Wednesday, August 27, 2014 10:32:23 PM Thomas Gleixner wrote:
> > void suspend_device_irqs(void)
> > {
> > for_each_irq_desc(irq, desc) {
> > /* Disable the interrupt unconditionally */
> > disable_irq(irq);
On Thu, 28 Aug 2014, Rafael J. Wysocki wrote:
On Wednesday, August 27, 2014 10:32:23 PM Thomas Gleixner wrote:
void suspend_device_irqs(void)
{
for_each_irq_desc(irq, desc) {
/* Disable the interrupt unconditionally */
disable_irq(irq);
We
On Thursday, August 28, 2014 11:23:11 AM Thomas Gleixner wrote:
On Thu, 28 Aug 2014, Rafael J. Wysocki wrote:
On Wednesday, August 27, 2014 10:32:23 PM Thomas Gleixner wrote:
void suspend_device_irqs(void)
{
for_each_irq_desc(irq, desc) {
/* Disable the interrupt
On Wednesday, August 27, 2014 10:32:23 PM Thomas Gleixner wrote:
> On Wed, 27 Aug 2014, Rafael J. Wysocki wrote:
> > The line of reasoning leading to that is as follows.
> >
> > The way suspend_device_irqs() works and the existing code in
> > check_wakeup_irqs(), called by syscore_suspend(),
On Wed, 27 Aug 2014, Rafael J. Wysocki wrote:
> The line of reasoning leading to that is as follows.
>
> The way suspend_device_irqs() works and the existing code in
> check_wakeup_irqs(), called by syscore_suspend(), imply that:
>
> (1) Interrupt handlers are not invoked for wakeup interrupts
On Wed, 27 Aug 2014, Rafael J. Wysocki wrote:
The line of reasoning leading to that is as follows.
The way suspend_device_irqs() works and the existing code in
check_wakeup_irqs(), called by syscore_suspend(), imply that:
(1) Interrupt handlers are not invoked for wakeup interrupts
On Wednesday, August 27, 2014 10:32:23 PM Thomas Gleixner wrote:
On Wed, 27 Aug 2014, Rafael J. Wysocki wrote:
The line of reasoning leading to that is as follows.
The way suspend_device_irqs() works and the existing code in
check_wakeup_irqs(), called by syscore_suspend(), imply that:
From: Rafael J. Wysocki
Make IRQs enabled for system wakeup via enable_irq_wake() wake up
the system from suspend-to-idle.
For this purpose, introduce a new routine, wakeup_mode_for_irqs(),
for switching wakeup IRQs into a special "wakeup mode" and back from
it and make freeze_enter() call it
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Make IRQs enabled for system wakeup via enable_irq_wake() wake up
the system from suspend-to-idle.
For this purpose, introduce a new routine, wakeup_mode_for_irqs(),
for switching wakeup IRQs into a special wakeup mode and back from
it and make
10 matches
Mail list logo
