From: Tony Lindgren <tony@atomide.com>
To: Marcin Niestroj <m.niestroj@grinn-global.com>
Cc: rtc-linux@googlegroups.com, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Keerthy <j-keerthy@ti.com>,
linux-omap@vger.kernel.org
Subject: [rtc-linux] Re: [PATCH] rtc: omap: Support ext_wakeup configuration
Date: Mon, 4 Apr 2016 15:40:47 -0700 [thread overview]
Message-ID: <20160404224046.GA17042@atomide.com> (raw)
In-Reply-To: <1459785403-1725-1-git-send-email-m.niestroj@grinn-global.com>
Hi,
* Marcin Niestroj <m.niestroj@grinn-global.com> [160404 08:57]:
> 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.
I suggest you just set this pin up as a minimal gpiochip. That way
we can use the standard binding :) And if we get lucky, this pin can
also trigger during runtime.
Regards,
Tony
--
--
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.
next prev parent reply other threads:[~2016-04-04 22:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 15:56 [rtc-linux] [PATCH] rtc: omap: Support ext_wakeup configuration Marcin Niestroj
2016-04-04 22:40 ` Tony Lindgren [this message]
2016-04-08 10:40 ` [rtc-linux] " Grygorii Strashko
2016-04-08 15:14 ` Tony Lindgren
2016-04-08 17:16 ` Grygorii Strashko
2016-04-08 17:51 ` Tony Lindgren
2016-04-09 16:42 ` Tony Lindgren
2016-04-12 17:25 ` Marcin Niestroj
2016-04-15 16:46 ` Grygorii Strashko
2016-04-15 16:52 ` Nishanth Menon
2016-04-15 17:18 ` Grygorii Strashko
2016-04-26 7:39 ` Marcin Niestroj
2016-04-26 15:39 ` Tony Lindgren
2016-06-15 8:37 ` Marcin Niestroj
2016-06-15 10:56 ` Tony Lindgren
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=20160404224046.GA17042@atomide.com \
--to=tony@atomide.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=m.niestroj@grinn-global.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.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