From: arno@natisbad.org (Arnaud Ebalard)
To: Jason Cooper <jason@lakedaemon.net>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Alessandro Zummo" <a.zummo@towertech.it>,
"Peter Huewe" <peter.huewe@infineon.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Thierry Reding" <treding@nvidia.com>,
"Mark Brown" <broonie@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Darshana Padmadas" <darshanapadmadas@gmail.com>,
"Rob Herring" <rob.herring@calxeda.com>,
"Pawel Moll" <pawel.moll@arm.com>,
"Stephen Warren" <swarren@wwwdotorg.org>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Grant Likely" <grant.likely@linaro.org>,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
"Rob Landley" <rob@landley.net>,
rtc-linux@googlegroups.com, "Guenter Roeck" <linux@roeck-us.net>,
"Jason Gunthorpe" <jgunthorpe@obsidianresearch.com>,
"Kumar Gala" <galak@codeaurora.org>,
linux-arm-kernel@l
Subject: Re: [PATCHv0 2/5] ARM: mvebu: ISL12057 rtc chip can be used to wake up RN102
Date: Mon, 15 Dec 2014 19:00:57 +0100 [thread overview]
Message-ID: <877fxskd2e.fsf@natisbad.org> (raw)
In-Reply-To: <20141215135308.GB967@titan.lakedaemon.net> (Jason Cooper's message of "Mon, 15 Dec 2014 08:53:08 -0500")
Jason Cooper <jason@lakedaemon.net> writes:
> On Sun, Dec 14, 2014 at 02:42:28AM +0100, Arnaud Ebalard wrote:
>>
>> Now that alarm support for ISL12057 chip is available, let's use a
>> feature of the driver dedicated to NETGEAR ReadyNAS 102 specific
>> routing of RTC IRQ#2 pin; on the device, this pin is not connected
>> to the SoC but to a PMIC, which allows the device to be powered
>> up when RTC alarm rings.
>>
>> For that to work, the chip needs to be explicitly marked as a
>> device wakeup source using the "can-wakeup-machine" boolean
>> property. This makes 'wakealarm' sysfs entry available to
>> configure the alarm.
>>
>> Signed-off-by: Arnaud Ebalard <arno@natisbad.org>
>> ---
>> arch/arm/boot/dts/armada-370-netgear-rn102.dts | 1 +
>> 1 file changed, 1 insertion(+)
>
> Please group patches 2 - 4 into one patch.
Will do.
a+
next prev parent reply other threads:[~2014-12-15 18:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 1:42 [PATCHv0 0/5] ISL12057 alarm support and isil vs isl fix Arnaud Ebalard
2014-12-14 1:42 ` [PATCHv0 1/5] rtc: rtc-isl12057: add alarm support to Intersil ISL12057 RTC driver Arnaud Ebalard
2014-12-15 19:36 ` RFC: new dt property "can-wakeup-machine" [Was: [PATCHv0 1/5] rtc: rtc-isl12057: add alarm support to Intersil ISL12057 RTC driver] Uwe Kleine-König
2014-12-15 20:18 ` Arnaud Ebalard
2014-12-14 1:42 ` [PATCHv0 2/5] ARM: mvebu: ISL12057 rtc chip can be used to wake up RN102 Arnaud Ebalard
2014-12-15 13:53 ` Jason Cooper
2014-12-15 18:00 ` Arnaud Ebalard [this message]
2014-12-14 1:42 ` [PATCHv0 3/5] ARM: mvebu: ISL12057 rtc chip can be used to wake up RN104 Arnaud Ebalard
2014-12-14 1:43 ` [PATCHv0 4/5] ARM: mvebu: ISL12057 rtc chip can be used to wake up RN2120 Arnaud Ebalard
2014-12-14 1:43 ` [PATCHv0 5/5] dt-bindings: fix isl vs isil prefix issue for Intersil Arnaud Ebalard
2014-12-15 13:55 ` Jason Cooper
2014-12-15 18:05 ` Arnaud Ebalard
2014-12-15 18:06 ` Jason Cooper
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=877fxskd2e.fsf@natisbad.org \
--to=arno@natisbad.org \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=darshanapadmadas@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@l \
--cc=linux-doc@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=peter.huewe@infineon.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=rtc-linux@googlegroups.com \
--cc=swarren@wwwdotorg.org \
--cc=treding@nvidia.com \
--cc=uwe@kleine-koenig.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).