public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq: do not disable IRQ_WAKEUP marked irqs on suspend
Date: Fri, 12 Jun 2009 11:33:40 -0700	[thread overview]
Message-ID: <87hbylb8u3.fsf@deeprootsystems.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0906122005140.2800@localhost.localdomain> (Thomas Gleixner's message of "Fri\, 12 Jun 2009 20\:09\:07 +0200 \(CEST\)")

Thomas Gleixner <tglx@linutronix.de> writes:

> On Fri, 12 Jun 2009, Kevin Hilman wrote:
>> Thomas Gleixner <tglx@linutronix.de> writes:
>> 
>> > commit 0a0c5168df (PM: Introduce functions for suspending and resuming
>> > device interrupts) iterates through all interrupts and disables them
>> > on the hardware level. Some architectures have functionality
>> > implemented to mark an interrupt source as wakeup source for suspend,
>> > but the new power management code disables them unconditionally which
>> > breaks the resume on interrupt functionality.
>> >
>> > The wakeup interrupts are marked in the status with the IRQ_WAKEUP
>> > bit. Skip the disablement for those interrupts which have the
>> > IRQ_WAKEUP bit set.
>> >     
>> > Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
>> > Cc: stable@kernel.org
>> 
>> Hi Thomas,
>> 
>> I posted the same patch last month and lost the argument, original
>> thread here:
>> 
>>   http://lkml.org/lkml/2009/5/6/549
>
> Err no. Care to look at the difference ? 

Oops, sent link to wrong patch.  Here's the one solving the same problem:

  http://marc.info/?l=linux-kernel&m=124148347804447&w=2

or

  http://lkml.org/lkml/2009/5/4/448

Only difference is I did the checking outside of the lock, which is
probably wrong.  In any case, you'll be interested in the thread that
follows.

Kevin

> I missed the above discussion, but I'm revisiting the delayed disable
> issue.
>
>> 
>> > diff --git a/kernel/irq/pm.c b/kernel/irq/pm.c
>> > index 638d8be..bce6afd 100644
>> > --- a/kernel/irq/pm.c
>> > +++ b/kernel/irq/pm.c
>> > @@ -29,7 +29,8 @@ void suspend_device_irqs(void)
>> >  		unsigned long flags;
>> >  
>> >  		spin_lock_irqsave(&desc->lock, flags);
>> > -		__disable_irq(desc, irq, true);
>> > +		if (!(desc->status & IRQ_WAKEUP))
>> > +			__disable_irq(desc, irq, true);
>> >  		spin_unlock_irqrestore(&desc->lock, flags);
>> >  	}
>> >  
>> > --
>> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> > the body of a message to majordomo@vger.kernel.org
>> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> > Please read the FAQ at  http://www.tux.org/lkml/
>> 

  reply	other threads:[~2009-06-12 18:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cMiA9-1MZ-13@gated-at.bofh.it>
2009-06-12 17:56 ` [PATCH] genirq: do not disable IRQ_WAKEUP marked irqs on suspend Kevin Hilman
2009-06-12 18:09   ` Thomas Gleixner
2009-06-12 18:33     ` Kevin Hilman [this message]
2009-06-12 19:52       ` Thomas Gleixner
2009-06-22 21:27         ` Andrew Morton
2009-06-22 22:56           ` Rafael J. Wysocki
2009-06-22 22:54         ` Rafael J. Wysocki
2009-06-12 17:09 Thomas Gleixner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87hbylb8u3.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox