diff options
author | Arnaud Ebalard <[email protected]> | 2015-02-13 14:40:39 -0800 |
---|---|---|
committer | Linus Torvalds <[email protected]> | 2015-02-13 21:21:42 -0800 |
commit | 1a67e256dbd80f47f339c4a88c34deee12489aa0 (patch) | |
tree | 83bb8a98238c8ede9ac5d2c7bd92e5e40148ae64 /tools/perf/util/scripting-engines/trace-event-perl.c | |
parent | 298ff0122ab19d253d3a8fea45a7227491beaf98 (diff) |
ARM: mvebu: ISL12057 rtc chip can now wake up RN102, RN102 and RN2120
Now that alarm support for ISL12057 chip is available w/ the specific
"isil,irq2-can-wakeup-machine" property, let's use that feature of the
driver dedicated to NETGEAR ReadyNAS 102, 104 and 2120 specific routing of
RTC Alarm IRQ#2 pin; on those devices, 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 this "isil,irq2-can-wakeup-machine" boolean property.
This makes 'wakealarm' sysfs entry available to configure the alarm.
Signed-off-by: Arnaud Ebalard <[email protected]>
Cc: Mark Rutland <[email protected]>
Cc: Alessandro Zummo <[email protected]>
Cc: Peter Huewe <[email protected]>
Cc: Linus Walleij <[email protected]>
Cc: Thierry Reding <[email protected]>
Cc: Mark Brown <[email protected]>
Cc: Arnd Bergmann <[email protected]>
Cc: Darshana Padmadas <[email protected]>
Cc: Rob Herring <[email protected]>
Cc: Pawel Moll <[email protected]>
Cc: Stephen Warren <[email protected]>
Cc: Ian Campbell <[email protected]>
Cc: Grant Likely <[email protected]>
Cc: Rob Landley <[email protected]>
Cc: Jason Cooper <[email protected]>
Cc: Guenter Roeck <[email protected]>
Cc: Jason Gunthorpe <[email protected]>
Cc: Kumar Gala <[email protected]>
Cc: Uwe Kleine-König <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-perl.c')
0 files changed, 0 insertions, 0 deletions