diff options
| author | Michael Lange <linuxstuff@milaw.biz> | 2016-01-21 18:10:16 +0100 |
|---|---|---|
| committer | Alexandre Belloni <alexandre.belloni@free-electrons.com> | 2016-02-04 23:44:17 +0100 |
| commit | 8bc2a40730ec74271a0573a6882871308d069f5d (patch) | |
| tree | 8b15ad190fd951a22b4e42fcbf4ecc70e15c3f2d /security/smack/smack_access.c | |
| parent | 04d3ba70a3c9c9ba593d3208531463c65f055526 (diff) | |
| download | linux-8bc2a40730ec74271a0573a6882871308d069f5d.tar.bz2 | |
rtc: ds1307: add support for the DT property 'wakeup-source'
For RTC chips with no IRQ directly connected to the SoC, the RTC chip
can be forced as a wakeup source by stating that explicitly in
the device's .dts file using the "wakeup-source" boolean property.
This will guarantee the 'wakealarm' sysfs entry is available on the
device, if supported by the RTC.
With these changes to the driver rtc-ds1307 and the necessary entries
in the .dts file, I get an working ds1337 RTC on the Witty Pi extension
board by UUGear for the Raspberry Pi.
An example for the entry in the .dts file:
rtc: ds1337@68 {
compatible = "dallas,ds1337";
reg = <0x68>;
wakeup-source;
If the "wakeup-source" property is set, do not request an IRQ.
Set also UIE mode to unsupported, to get a working 'hwclock' binary.
Signed-off-by: Michael Lange <linuxstuff@milaw.biz>
Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Diffstat (limited to 'security/smack/smack_access.c')
0 files changed, 0 insertions, 0 deletions