From: Rob Herring <robh@kernel.org>
To: Marcin Niestroj <m.niestroj@grinn-global.com>
Cc: Tony Lindgren <tony@atomide.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Keerthy <j-keerthy@ti.com>, Pawel Moll <pawel.moll@arm.com>,
Alessandro Zummo <a.zummo@towertech.it>,
rtc-linux@googlegroups.com, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [rtc-linux] Re: [PATCH v5] rtc: omap: Support ext_wakeup configuration
Date: Fri, 16 Sep 2016 10:37:59 -0500 [thread overview]
Message-ID: <20160916153759.GA12050@rob-hp-laptop> (raw)
In-Reply-To: <20160908105203.8641-1-m.niestroj@grinn-global.com>
On Thu, Sep 08, 2016 at 12:52:03PM +0200, Marcin Niestroj wrote:
> Support configuration of ext_wakeup sources. This patch makes it
> possible to enable ext_wakeup and set it's polarity, depending on board
> configuration. AM335x's dedicated PMIC (tps65217) uses ext_wakeup to
> notify about power-button presses. Handling power-button presses enables
> to recover from RTC-only power states correctly.
>
> Signed-off-by: Marcin Niestroj <m.niestroj@grinn-global.com>
> ---
> Hi,
>
> This patch adds support for ext_wakeup using generic pinconf device-tree
> bindings, with one added custom property.
>
> Changes v4 -> v5 (suggested by Rob):
> * Don't use GPIO defines in ti,input-polarity, use optional ti,active-high
> boolean instead.
> * Use '-' instead of '_' in node name.
>
> Changes v1 -> v4:
> * This is a total reimplementation, so it is not based on any of the previous
> patch versions. This approach has been suggested by Tony and Grygorii
> in [1].
>
> Patch was developed on 4.7, rebased on 4.8-rc5, tested using chiliBoard.
>
> [1] http://www.spinics.net/lists/devicetree/msg131516.html
>
> Documentation/devicetree/bindings/rtc/rtc-omap.txt | 21 +++
For the binding:
Acked-by: Rob Herring <robh@kernel.org>
> drivers/rtc/Kconfig | 1 +
> drivers/rtc/rtc-omap.c | 168 ++++++++++++++++++++-
> 3 files changed, 182 insertions(+), 8 deletions(-)
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
prev parent reply other threads:[~2016-09-16 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 10:52 [rtc-linux] [PATCH v5] rtc: omap: Support ext_wakeup configuration Marcin Niestroj
2016-09-08 14:20 ` [rtc-linux] " kbuild test robot
2016-09-12 9:01 ` Marcin Niestroj
2016-09-13 21:58 ` Alexandre Belloni
2016-09-14 9:21 ` Marcin Niestroj
2016-09-15 12:08 ` Alexandre Belloni
2016-09-08 14:27 ` kbuild test robot
2016-09-08 15:03 ` kbuild test robot
2016-09-16 15:37 ` Rob Herring [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=20160916153759.GA12050@rob-hp-laptop \
--to=robh@kernel.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=j-keerthy@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=m.niestroj@grinn-global.com \
--cc=pawel.moll@arm.com \
--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