From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Peter Zijlstra <peterz@infradead.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/6] ARM: at91: fix irq_pm_install_action WARNING
Date: Fri, 27 Feb 2015 23:33:35 +0100 [thread overview]
Message-ID: <50911513.ad0Lf8479H@vostro.rjw.lan> (raw)
In-Reply-To: <1425049798-5891-1-git-send-email-boris.brezillon@free-electrons.com>
On Friday, February 27, 2015 04:09:52 PM Boris Brezillon wrote:
> Commit cab303be91dc47942bc25de33dc1140123540800 [1] introduced a WARN_ON
> test which triggers a WARNING backtrace on at91 platforms.
> While this WARN_ON is absolutely necessary to warn users that they should
> not mix request with and without IRQF_NO_SUSPEND flags on shared IRQs,
> there is no easy way to solve this issue on at91 platforms.
>
> The main reason is that the init timer is often using a shared irq line
> and thus request this irq with IRQF_NO_SUSPEND flag set, while other
> peripherals request the same irq line without this flag.
>
> This problem has recently been addressed by this patch [2] which adds
> a new IRQF_COND_SUSPEND flag, that authorize mixing IRQF_NO_SUSPEND and
> !IRQF_NO_SUSPEND as long as irq handlers setting IRQF_COND_SUSPEND
> can safely be called in suspended state.
>
> Doing this also implies taking care of system wakeup in devices handlers
> if they tag the IRQ line as a wakeup source.
> The first patch of this series exports the pm_system_wakeup symbol so
> that drivers can call pm_system_wakeup from their interrupt handler.
>
> This series then patches all at91 drivers that can have devices sharing
> their IRQ line with a timer.
>
> This series depends on [2].
Series looks good to me (although admittedly I'm not familiar with the
drivers in question).
Do you want me to apply it on top of [2]?
> [1]https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/kernel/irq/pm.c?id=cab303be91dc47942bc25de33dc1140123540800
> [2]https://lkml.org/lkml/2015/2/26/675
>
> Boris Brezillon (6):
> PM / wakeup: export pm_system_wakeup symbol
> rtc: at91sam9: rework wakeup and interrupt handling
> rtc: at91rm9200: rework wakeup and interrupt handling
> clk: at91: implement suspend/resume for the PMC irqchip
> watchdog: at91sam9: request the irq with IRQF_NO_SUSPEND
> tty: serial: atmel: rework interrupt and wakeup handling
>
> drivers/base/power/wakeup.c | 1 +
> drivers/clk/at91/pmc.c | 20 ++++++++++-
> drivers/clk/at91/pmc.h | 1 +
> drivers/rtc/rtc-at91rm9200.c | 62 +++++++++++++++++++++++++--------
> drivers/rtc/rtc-at91sam9.c | 73 ++++++++++++++++++++++++++++++++-------
> drivers/tty/serial/atmel_serial.c | 49 +++++++++++++++++++++++---
> drivers/watchdog/at91sam9_wdt.c | 3 +-
> 7 files changed, 177 insertions(+), 32 deletions(-)
>
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2015-02-27 22:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 15:09 Boris Brezillon
2015-02-27 15:09 ` [PATCH 1/6] PM / wakeup: export pm_system_wakeup symbol Boris Brezillon
2015-02-27 15:09 ` [PATCH 2/6] rtc: at91sam9: rework wakeup and interrupt handling Boris Brezillon
2015-02-27 15:09 ` [PATCH 3/6] rtc: at91rm9200: " Boris Brezillon
2015-02-27 15:09 ` [PATCH 4/6] clk: at91: implement suspend/resume for the PMC irqchip Boris Brezillon
2015-02-27 15:09 ` [PATCH 5/6] watchdog: at91sam9: request the irq with IRQF_NO_SUSPEND Boris Brezillon
2015-02-27 15:09 ` [PATCH 6/6] tty: serial: atmel: rework interrupt and wakeup handling Boris Brezillon
2015-02-27 22:33 ` Rafael J. Wysocki [this message]
2015-03-02 9:05 ` [PATCH 0/6] ARM: at91: fix irq_pm_install_action WARNING Boris Brezillon
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=50911513.ad0Lf8479H@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@atmel.com \
--cc=peterz@infradead.org \
--cc=plagnioj@jcrosoft.com \
--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
all inboxes | Powered by JetHome®