From: Nishanth Menon <nm@ti.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
Keerthy <j-keerthy@ti.com>, Mark Brown <broonie@linaro.org>,
Nishanth Menon <nm@ti.com>, Samuel Ortiz <sameo@linux.intel.com>,
<linux-omap@vger.kernel.org>, Tony Lindgren <tony@atomide.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH V2 0/3] mfd: palmas: add optional wakeup irq
Date: Fri, 5 Sep 2014 15:51:48 -0500 [thread overview]
Message-ID: <1409950311-25236-1-git-send-email-nm@ti.com> (raw)
Hi,
V2 of the series based on review conclusion in
https://patchwork.kernel.org/patch/4743321/
based on v3.17-rc1
Wakeup irq is a interrupt path which is provided by the pinctrl
hardware of certain SoCs such as TI's OMAP family of processors that
generates an interrupt for waking up from deep power saving modes.
Nishanth Menon (3):
Documentation: dt-bindings: mfd: palmas: Fix example style of i2c
peripheral
Documentation: dt-bindings: mfd: palmas: document optional wakeup IRQ
mfd: palmas: Add support for optional wakeup
Documentation/devicetree/bindings/mfd/palmas.txt | 22 +++++++-
drivers/mfd/palmas.c | 59 ++++++++++++++++++++++
include/linux/mfd/palmas.h | 2 +
3 files changed, 82 insertions(+), 1 deletion(-)
Regards,
Nishanth Menon
--
1.7.9.5
next reply other threads:[~2014-09-05 20:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 20:51 Nishanth Menon [this message]
2014-09-05 20:51 ` [PATCH V2 1/3] Documentation: dt-bindings: mfd: palmas: Fix example style of i2c peripheral Nishanth Menon
2014-09-05 20:51 ` [PATCH V2 2/3] Documentation: dt-bindings: mfd: palmas: document optional wakeup IRQ Nishanth Menon
2014-09-05 20:51 ` [PATCH V2 3/3] mfd: palmas: Add support for optional wakeup Nishanth Menon
2014-09-05 21:13 ` Thomas Gleixner
2014-09-08 15:41 ` Nishanth Menon
2014-09-18 13:54 ` Nishanth Menon
2014-09-18 17:33 ` Lee Jones
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=1409950311-25236-1-git-send-email-nm@ti.com \
--to=nm@ti.com \
--cc=broonie@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sameo@linux.intel.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
Powered by JetHome