From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv1 1/3] rtc: rtc-isl12057: add alarm support to Intersil ISL12057 RTC driver
Date: Tue, 16 Dec 2014 23:05:11 +0000 [thread overview]
Message-ID: <20141216230511.GV11764@sirena.org.uk> (raw)
In-Reply-To: <5490A873.1000706@kleine-koenig.org>
On Tue, Dec 16, 2014 at 10:47:31PM +0100, Uwe Kleine-K?nig wrote:
> On 12/16/2014 01:07 PM, Arnaud Ebalard wrote:
> > no, it is for this patch. I did a specific commit message for the second
> > patch. IIRC, it also has the example if it was the meaning of your
> > question.
> Is it usual that an rtc can wake up a machine from shutdown state? I
> thought it isn't.
It's fairly normal when the RTC is integrated into the PMIC - the PMIC
is typically the component initiating power on so it's easy for it to do
so.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141216/497941e6/attachment.sig>
next prev parent reply other threads:[~2014-12-16 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 23:54 [PATCHv1 0/3] Alarm support for ISL12057 + RFC dt property Arnaud Ebalard
2014-12-15 23:54 ` [PATCHv1 1/3] rtc: rtc-isl12057: add alarm support to Intersil ISL12057 RTC driver Arnaud Ebalard
2014-12-16 10:08 ` Uwe Kleine-König
2014-12-16 12:07 ` Arnaud Ebalard
2014-12-16 21:47 ` Uwe Kleine-König
2014-12-16 23:05 ` Mark Brown [this message]
2014-12-15 23:54 ` [PATCHv1 2/3] rtc: rtc-isl12057: add isil,irq2-can-wakeup-machine property for in-tree users Arnaud Ebalard
2014-12-15 23:55 ` [PATCHv1 3/3] ARM: mvebu: ISL12057 rtc chip can now wake up RN102, RN102 and RN2120 Arnaud Ebalard
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=20141216230511.GV11764@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).