From: Thomas Gleixner <tglx@linutronix.de>
To: Lina Iyer <ilina@codeaurora.org>
Cc: Stephen Boyd <swboyd@chromium.org>,
linux-kernel@vger.kernel.org, Marc Zyngier <maz@kernel.org>,
Douglas Anderson <dianders@chromium.org>,
Maulik Shah <mkshah@codeaurora.org>
Subject: Re: [PATCH] genirq: Clarify that irq wake state is orthogonal to enable/disable
Date: Wed, 05 Feb 2020 15:52:56 +0000 [thread overview]
Message-ID: <87tv45rpyf.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20200205153410.GA3898@codeaurora.org>
Lina Iyer <ilina@codeaurora.org> writes:
> On Wed, Feb 05 2020 at 05:27 -0700, Thomas Gleixner wrote:
>>> @@ -731,6 +731,11 @@ static int set_irq_wake_real(unsigned int irq, unsigned int on)
>>> *
>>> * Wakeup mode lets this IRQ wake the system from sleep
>>> * states like "suspend to RAM".
>>> + *
>>> + * Note: irq enable/disable state is completely orthogonal
>>> + * to the enable/disable state of irq wake. An irq can be
>>> + * disabled with disable_irq() and still wake the system as
>>> + * long as the irq has wake enabled.
>>
>>It clearly should say that this is really depending on the hardware
>>implementation of the particual interrupt chip whether disabled + wake
>>mode is supported.
>>
> Could an irqchip flag be used to warn users that we may not wakeup from
> suspend/resume if the interrupt if the hardware does not support wakeup
> when disabled ?
There are also magic ways of wakeup for irqchips which do not have wake
setup functions and still wake the system up when the interrupt line is
disabled by the kernel on suspend. :)
Thanks,
tglx
next prev parent reply other threads:[~2020-02-05 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 6:09 [PATCH] genirq: Clarify that irq wake state is orthogonal to enable/disable Stephen Boyd
2020-02-05 12:27 ` Thomas Gleixner
2020-02-05 15:34 ` Lina Iyer
2020-02-05 15:52 ` Thomas Gleixner [this message]
2020-02-05 20:37 ` Stephen Boyd
2020-02-06 9:42 ` 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=87tv45rpyf.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=dianders@chromium.org \
--cc=ilina@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=mkshah@codeaurora.org \
--cc=swboyd@chromium.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