diff options
| author | Sekhar Nori <nsekhar@ti.com> | 2010-03-07 18:05:54 +0530 |
|---|---|---|
| committer | Kevin Hilman <khilman@deeprootsystems.com> | 2010-05-06 15:02:03 -0700 |
| commit | 9c0a342c45b2d98209ac473ea7a429ddd5c1b473 (patch) | |
| tree | 3147f33381291c3352ff72ee4a1219c56909395f /net/TUNABLE | |
| parent | 8ecf6c54d44c535b2296319aa58567ea9a1db026 (diff) | |
| download | talos-obmc-linux-9c0a342c45b2d98209ac473ea7a429ddd5c1b473.tar.gz talos-obmc-linux-9c0a342c45b2d98209ac473ea7a429ddd5c1b473.zip | |
rtc: omap: let device wakeup capability be configured from chip init logic
The rtc-omap driver currently hardcodes the RTC wakeup capability
to be "not capable". While this seems to be true for existing OMAP1
boards which are not wired for this, the DA850/OMAP-L138 SoC, the
RTC can always be wake up source from its "deep sleep" mode.
This patch lets the wakeup capability to be set from platform data and
does not override the setting from the driver. For DA850/OMAP-L138, this
is done from arch/arm/mach-davinci/devices-da8xx.c:da8xx_register_rtc()
Note that this patch does not change the behavior on any existing OMAP1
board since the platform device registration sets the wakeup capability
to 0 by default.
Signed-off-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Diffstat (limited to 'net/TUNABLE')
0 files changed, 0 insertions, 0 deletions
