From: mika.westerberg@linux.intel.com (Mika Westerberg)
To: linux-arm-kernel@lists.infradead.org
Subject: [4.4-rc][PATCH] genirq / PM: restore system wake up from chained interrupts
Date: Tue, 10 Nov 2015 13:13:14 +0200 [thread overview]
Message-ID: <20151110111314.GC1509@lahna.fi.intel.com> (raw)
In-Reply-To: <1447149492-20699-1-git-send-email-grygorii.strashko@ti.com>
On Tue, Nov 10, 2015 at 11:58:12AM +0200, Grygorii Strashko wrote:
> Commit e509bd7da149 ("genirq: Allow migration of chained interrupts
> by installing default action") breaks PCS wake up IRQ behaviour on
> TI OMAP based platforms (dra7-evm).
>
> TI OMAP IRQ wake up configuration:
> GIC-irqchip->PCM_IRQ
> |- omap_prcm_register_chain_handler
> |- PRCM-irqchip -> PRCM_IO_IRQ
> |- pcs_irq_chain_handler
> |- pinctrl-irqchip -> PCS_uart1_wakeup_irq
>
> This happens because IRQ PM code (irq/pm.c) is expected to ignore
> chained interrupts by default:
> static bool suspend_device_irq(struct irq_desc *desc)
> {
> if (!desc->action || desc->no_suspend_depth)
> return false;
> - it's expected !desc->action = true for chained interrupts;
Indeed it is. I missed that, sorry.
> but, after above change, all chained interrupt descriptors will
> have default action handler installed - chained_action.
> As result, chained interrupts will be silently disabled during system
> suspend.
>
> Hence, fix it by introducing helper function irq_desc_is_chained() and
> use it in suspend_device_irq() for chained interrupts identification
> and skip them, once detected.
>
> Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
FWIW,
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
prev parent reply other threads:[~2015-11-10 11:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 9:58 [4.4-rc][PATCH] genirq / PM: restore system wake up from chained interrupts Grygorii Strashko
2015-11-10 11:13 ` Mika Westerberg [this message]
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=20151110111314.GC1509@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).