From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Lee Jones <lee.jones@linaro.org>,
Alessandro Zummo <a.zummo@towertech.it>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Lars-Peter Clausen <lars@metafoo.de>
Cc: <rtc-linux@googlegroups.com>, <linux-iio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <nsekhar@ti.com>,
<linux-omap@vger.kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
Tony Lindgren <tony@atomide.com>, Nishanth Menon <nm@ti.com>,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: [PATCH 0/7] mfd: Drop IRQF_EARLY_RESUME flag
Date: Fri, 26 Feb 2016 17:42:50 +0200 [thread overview]
Message-ID: <1456501377-16871-1-git-send-email-grygorii.strashko@ti.com> (raw)
The IRQF_EARLY_RESUME flag is not required for nested irqs anymore,
since commit 3c646f2c6aa9 ("genirq: Don't suspend nested_thread irqs
over system suspend") was merged.
Hence, this flag can be dropped for MFD cell's devices where MFD interrupt
controller defines nested IRQs as nested threaded IRQs.
Cc: Lee Jones <lee.jones@linaro.org>
Cc: Alessandro Zummo <a.zummo@towertech.it>
Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: Chanwoo Choi <cw00.choi@samsung.com>
Cc: Hartmut Knaack <knaack.h@gmx.de>
Cc: Lars-Peter Clausen <lars@metafoo.de>
Cc: Peter Meerwald <pmeerw@pmeerw.net>
Cc: Tony Lindgren <tony@atomide.com>
Cc: Nishanth Menon <nm@ti.com>
Cc: Laxman Dewangan <ldewangan@nvidia.com>
Grygorii Strashko (7):
extcon: palmas: Drop IRQF_EARLY_RESUME flag
rtc: palmas: Drop IRQF_EARLY_RESUME flag
rtc: tps6586x: Drop IRQF_EARLY_RESUME flag
rtc: tps65910: Drop IRQF_EARLY_RESUME flag
rtc: tps80031: Drop IRQF_EARLY_RESUME flag
rtc: as3722: Drop IRQF_EARLY_RESUME flag
iio: adc: palmas: Drop IRQF_EARLY_RESUME flag
drivers/extcon/extcon-palmas.c | 4 ++--
drivers/iio/adc/palmas_gpadc.c | 6 +++---
drivers/rtc/rtc-as3722.c | 2 +-
drivers/rtc/rtc-palmas.c | 3 +--
drivers/rtc/rtc-tps6586x.c | 2 +-
drivers/rtc/rtc-tps65910.c | 2 +-
drivers/rtc/rtc-tps80031.c | 2 +-
7 files changed, 10 insertions(+), 11 deletions(-)
--
2.7.2
next reply other threads:[~2016-02-26 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 15:42 Grygorii Strashko [this message]
2016-02-26 15:42 ` [PATCH 1/7] extcon: palmas: " Grygorii Strashko
2016-02-29 2:22 ` Chanwoo Choi
2016-02-26 15:42 ` [PATCH 2/7] rtc: " Grygorii Strashko
2016-02-26 15:42 ` [PATCH 3/7] rtc: tps6586x: " Grygorii Strashko
2016-02-26 15:42 ` [PATCH 4/7] rtc: tps65910: " Grygorii Strashko
2016-02-26 15:42 ` [PATCH 5/7] rtc: tps80031: " Grygorii Strashko
2016-02-26 15:42 ` [PATCH 6/7] rtc: as3722: " Grygorii Strashko
2016-02-26 15:42 ` [PATCH 7/7] iio: adc: palmas: " Grygorii Strashko
2016-02-27 17:21 ` Jonathan Cameron
2016-02-28 23:45 ` [PATCH 0/7] mfd: " Alexandre Belloni
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=1456501377-16871-1-git-send-email-grygorii.strashko@ti.com \
--to=grygorii.strashko@ti.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=cw00.choi@samsung.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=ldewangan@nvidia.com \
--cc=lee.jones@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=pmeerw@pmeerw.net \
--cc=rtc-linux@googlegroups.com \
--cc=tony@atomide.com \
/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®