From: Alexandra Yates <alexandra.yates@linux.intel.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: tglx@linutronix.de, kristen.c.accardi@intel.com,
linux-pm@vger.kernel.org, rjw@rjwysocki.net
Subject: Re: [PATCH V7] Report interrupt that caused system wakeup
Date: Thu, 10 Sep 2015 11:42:15 -0700 [thread overview]
Message-ID: <55F1CF07.8070505@linux.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1509101012180.1422-100000@iolanthe.rowland.org>
Hi Alan,
On 09/10/2015 07:14 AM, Alan Stern wrote:
> On Wed, 9 Sep 2015, Alexandra Yates wrote:
>
>> This feature reports which IRQ cause the system to wakeup from sleep last
>> time it was suspended.
> I thought you said V7 of this patch was written based on the feedback I
> provided. Obviously that is not true.
Yes, that was the intention.
> This feature does NOT report which IRQ caused the system to wake up
> from sleep the last time it was suspended! All it does is report one
> of the IRQs which have occurred since the last time the system started
> a sleep transition.
I'm not sure why you say this, please elaborate further.
The way I understand the code and proposed solution is that when
the system goes into freeze mode, at that point wakeup_irq is set to 0.
Once the system sees an interrupt at wakeup from freeze. wakeup_irq is
set to
the irq_number that caused the wakeup. This path of code is protected
by spin lock,
which should protect the code path from other IRQs that came after the
first IRQ.
This is only set once. When other IRQs come and the wakeup_irq is set
then the code
doesn't store them.
> Alan Stern
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Thank you,
<Alexandra>
next prev parent reply other threads:[~2015-09-10 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH V7] Report interrupt that caused system wakeup>
2015-09-10 2:48 ` [PATCH V7] Report interrupt that caused system wakeup Alexandra Yates
2015-09-10 7:36 ` Sergey Senozhatsky
2015-09-10 14:14 ` Alan Stern
2015-09-10 18:42 ` Alexandra Yates [this message]
2015-09-10 19:15 ` Alan Stern
2015-09-10 22:21 ` Rafael J. Wysocki
2015-09-11 14:07 ` Alan Stern
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=55F1CF07.8070505@linux.intel.com \
--to=alexandra.yates@linux.intel.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=stern@rowland.harvard.edu \
--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;
as well as URLs for NNTP newsgroup(s).