public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Kim Kyuwon <chammoru@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Kim Kyuwon <q1.kim@samsung.com>, Ingo Molnar <mingo@elte.hu>,
	linux-pm@lists.linux-foundation.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] PM: suspend_device_irqs(): don't disable wakeup IRQs
Date: Sat, 30 May 2009 23:00:16 +0200	[thread overview]
Message-ID: <200905302300.17995.rjw@sisk.pl> (raw)
In-Reply-To: <4d34a0a70905300034q1dee8febl60b5213082e3a5d1@mail.gmail.com>

On Saturday 30 May 2009, Kim Kyuwon wrote:
> On Sat, May 30, 2009 at 8:35 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Monday 25 May 2009, Kim Kyuwon wrote:
> >> Rafael J. Wysocki wrote:
> >> > On Saturday 23 May 2009, Kim Kyuwon wrote:
> >> >> On Sat, May 23, 2009 at 7:29 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> >> >>> On Saturday 23 May 2009, Kim Kyuwon wrote:
> >> > [--snip--]
> >> >>>> You changed the really important part of Linux, which may affect most
> >> >>>> processor architectures. I think you should be careful. If some of
> >> >>>> architectures can't take care of it (they can implement
> >> >>>> disable_irq_wake correctly in H/W level, will you revert your changes?
> >> >>> No, the changes are not going to be reverted.  In fact things should have been
> >> >>> done like this already much earlier.
> >> >>>
> >> >>> Now, do you have any particular example of a problem related to these changes
> >> >>> or is it only a theoretical issue?
> >> >> I'd CCing you when I'm sending a mail for this particular example of a example.
> >> >> http://markmail.org/thread/fvt7d62arofon5xx
> >> >
> >> > Well, as I said above, reverting the changes that introduced
> >> > [suspend|resume]_device_irqs() is not an option, becuase it was the only sane
> >> > way to achieve the goal they were added for.  So, we need to fix the wake-up
> >> > problem on your platform with the assumption that
> >> > [suspend|resume]_device_irqs() are going to stay.
> >> >
> >> > For starters, would it be possible to teach the 'disable' hook of your
> >> > platform's interrupt controller not to mask the IRQs that have both
> >> > IRQ_WAKEUP and IRQ_SUSPENDED set?  That apparently would work around the
> >> > wake-up interrupts problem.
> >>
> >> Thank you for considering this issue and spending your time. In order to
> >> make your idea work, we need to add a dummy 'set_wake' hook which
> >> returns always zero. Anyway, IMO, I think your idea is good to work
> >> around this problem. But Kevin Hilman(OMAP PM Maintainer) would make
> >> final decision.
> >>
> >> Buy the way, how can you handle the problem that a few interrupt are
> >> discarded in a small window? I can be sure they are discarded, because I
> >> have debugged defects which generate in sleep/resume state hundreds of
> >> times on ARM Processors(PXA310, S3C6410, OMAP3430). Wake-up interrupts
> >> are generated as soon as arch_suspend_enable_irqs() invoked.
> >
> > Sorry for the delayed response.
> >
> > If the wake-up interrupts are not masked, they will be delivered to the drivers
> > as soon as arch_suspend_enable_irqs() has run.  So, if the drivers are able to
> > handle them at this point (ie. before resume_device_irqs() is called), they
> > won't be lost.
> 
> Thank you for your response!
> 
> Your suspend_device_irqs() disables all IRQs(except timer IRQ) while
> entering suspend. i.e. Before invoking resume_device_irqs() or
> resume_noirq callback, all IRQs(except timer IRQ) is in IRQ_DISABLED
> status. Right?
> But if an IRQ is in  IRQ_DISABLED status, its interrupt handler can be

s/can be/can't be/ (as you noticed in the follow-up message).

> invoked. (As you know, all IRQs with IRQ_DISABLE are not handled in
> handle_level_irq function). Thus, even if the wake-up interrupts are
> not masked, the drivers are not able to handle interrupts, because the
> interrupt handler can't be invoked due to IRQ_DISABLED set by
> suspend_device_irqs().

The solution to that may be to add some code that will clear the
IRQ_DISABLE flag for the wake-up interrupt that caused the wake-up to happen
in the early resume code of the platform.

> > The only problem I see is that the drivers may expect their
> > ->resume_noirq() callbacks to be executed first.
> 
> resume_noirq() callbacks are also invoked after arch_suspend_enable_irqs().

Yes, they are, and that may be a problem, because a driver may expect
resume_noirq() to be called before it can handle interrupts from the device.

Best,
Rafael

  parent reply	other threads:[~2009-05-30 21:00 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-05  0:27 [PATCH] PM: suspend_device_irqs(): don't disable wakeup IRQs Kevin Hilman
2009-05-05  6:54 ` Andrew Morton
     [not found] ` <20090504235405.647772ed.akpm@linux-foundation.org>
2009-05-05 14:11   ` Vitaly Wool
2009-05-05 15:52   ` Kevin Hilman
     [not found]   ` <acd2a5930905050711j57cbf81du2fe4dbb4e408e877@mail.gmail.com>
2009-05-05 15:56     ` Kevin Hilman
     [not found]   ` <87ocu7a6ng.fsf@deeprootsystems.com>
2009-05-05 20:58     ` Arve Hjønnevåg
     [not found]     ` <d6200be20905051358m34c2be02ped84ad4158cd9865@mail.gmail.com>
2009-05-05 23:15       ` Kevin Hilman
     [not found]       ` <87eiv35eg6.fsf@deeprootsystems.com>
2009-05-05 23:27         ` Rafael J. Wysocki
     [not found]         ` <200905060127.24777.rjw@sisk.pl>
2009-05-05 23:51           ` Arve Hjønnevåg
2009-05-06  0:13           ` Kevin Hilman
2009-05-06  0:20           ` Kim Kyuwon
     [not found]           ` <87y6tb3x6r.fsf@deeprootsystems.com>
2009-05-06  0:38             ` Kevin Hilman
     [not found]             ` <878wlb3w18.fsf@deeprootsystems.com>
2009-05-06  0:45               ` Kevin Hilman
2009-05-06 14:04             ` Kevin Hilman
     [not found]             ` <871vr22upr.fsf@deeprootsystems.com>
2009-05-06 21:18               ` Rafael J. Wysocki
     [not found]               ` <200905062318.23572.rjw@sisk.pl>
2009-05-07  0:16                 ` Kevin Hilman
     [not found]                 ` <87zldpu5rt.fsf@deeprootsystems.com>
2009-05-07  1:18                   ` Arve Hjønnevåg
     [not found]                   ` <d6200be20905061818h58145d5fie5c55ceaf900a196@mail.gmail.com>
2009-05-07  1:28                     ` Kim Kyuwon
     [not found]                     ` <4d34a0a70905061828l3e35a954k76967b30c1a241ab@mail.gmail.com>
2009-05-07  1:44                       ` Arve Hjønnevåg
     [not found]                       ` <d6200be20905061844q8a4945y83daa86b336dc49a@mail.gmail.com>
2009-05-07  2:04                         ` Kim Kyuwon
     [not found]                         ` <4d34a0a70905061904w338457efna8a3cbb80537e0c9@mail.gmail.com>
2009-05-07 14:13                           ` Kevin Hilman
2009-05-07 11:54                   ` Rafael J. Wysocki
2009-05-22  2:53           ` Kim Kyuwon
2009-05-22 16:04             ` Kim Kyuwon
2009-05-22 21:23             ` Rafael J. Wysocki
     [not found]             ` <4d34a0a70905220904h6734a8f1y2b2cffe08b6afa8b@mail.gmail.com>
2009-05-22 21:25               ` Rafael J. Wysocki
     [not found]               ` <200905222325.27950.rjw@sisk.pl>
2009-05-22 22:32                 ` Kim Kyuwon
     [not found]                 ` <4d34a0a70905221532l772d03b6gb6436f0b8eb10274@mail.gmail.com>
2009-05-22 23:47                   ` Rafael J. Wysocki
     [not found]                   ` <200905230147.16037.rjw@sisk.pl>
2009-05-23  0:42                     ` Kim Kyuwon
     [not found]             ` <200905222323.22390.rjw@sisk.pl>
2009-05-22 22:24               ` Kim Kyuwon
     [not found]               ` <4d34a0a70905221524i1ac5a241k5f0a60ee542d55a5@mail.gmail.com>
2009-05-22 22:29                 ` Rafael J. Wysocki
     [not found]                 ` <200905230029.18279.rjw@sisk.pl>
2009-05-22 23:03                   ` Kim Kyuwon
     [not found]                   ` <4d34a0a70905221603g785f5b78h330249ff258dbfdd@mail.gmail.com>
2009-05-23 20:14                     ` Rafael J. Wysocki
     [not found]                     ` <200905232214.57186.rjw@sisk.pl>
2009-05-25  7:02                       ` Kim Kyuwon
     [not found]                       ` <4A1A4297.50809@samsung.com>
2009-05-29 23:35                         ` Rafael J. Wysocki
2009-05-30  7:34                           ` Kim Kyuwon
     [not found]                           ` <4d34a0a70905300034q1dee8febl60b5213082e3a5d1@mail.gmail.com>
2009-05-30  7:40                             ` Kim Kyuwon
2009-05-30 21:00                             ` Rafael J. Wysocki [this message]
2009-05-05 23:57         ` Arve Hjønnevåg

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=200905302300.17995.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=chammoru@gmail.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mingo@elte.hu \
    --cc=q1.kim@samsung.com \
    --cc=torvalds@linux-foundation.org \
    /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