linux-stable.git/drivers/rtc/rtc-omap.c, branch linux-3.12.y

drivers/rtc/rtc-omap.c: add rtc wakeup support to alarm events

2013-09-11T22:58:54+00:00

On some platforms (like AM33xx), a special register (RTC_IRQWAKEEN) is
available to enable Alarm Wakeup feature.  This register needs to be
properly handled for the rtcwake to work properly.

Platforms using such IP should set "ti,am3352-rtc" in rtc device dt
compatibility node.

Signed-off-by: Hebbar Gururaja 
Acked-by: Kevin Hilman 
Acked-by: Sekhar Nori 
Cc: Grant Likely 
Cc: Rob Herring 
Cc: Rob Landley 
Cc: Alessandro Zummo 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

rtc: omap: restore back (hard-code) wakeup support

2013-07-03T23:08:00+00:00

rtc-omap driver modules is used both by OMAP1/2, Davinci SoC platforms.

However, rtc wake support on OMAP1 is broken.  Hence the
device_init_wakeup() was removed from rtc-omap driver and moved to
platform board files that supported it (DA850/OMAP-L138).  [1]

However, recently [2] it was suggested that driver should always do a
device_init_wakeup(dev, true). Platforms that don't want/need
wakeup support can disable it from userspace via:

    echo disabled > /sys/devices/.../power/wakeup

Also, with the new DT boot-up, board file doesn't exist and hence there
is no way to have device wakeup support rtc.

The fix for above issues, is to hard code device_init_wakeup() inside
driver and let platforms that don't need this, handle it through the
sysfs power entry.

[1]
https://patchwork.kernel.org/patch/136731/

[2]
http://www.mail-archive.com/davinci-linux-open-source@linux.
davincidsp.com/msg26077.html

Signed-off-by: Hebbar Gururaja 
Cc: Alessandro Zummo 
Acked-by: Kevin Hilman 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

drivers/rtc/rtc-omap.c: include instead of

2013-07-03T23:07:48+00:00

Use #include  instead of  as pointed out by
checkpatch.

Signed-off-by: Sachin Kamat 
Cc: George G. Davis 
Cc: Jingoo Han 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

drivers/rtc: don't check resource with devm_ioremap_resource

2013-05-18T09:57:07+00:00

devm_ioremap_resource does sanity checks on the given resource. No need to
duplicate this in the driver.

Signed-off-by: Wolfram Sang 
Acked-by: Stephen Warren

rtc: rtc-omap: convert omap_rtc_driver to dev_pm_ops

2013-04-30T01:28:39+00:00

Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.

Signed-off-by: Jingoo Han 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

drivers/rtc/rtc-omap.c: update to devm_* API

2013-04-30T01:28:33+00:00

Update the code to use devm_* API so that driver core will manage
resources.

Signed-off-by: Vishwanathrao Badarkhe, Manish 
Tested-by: Sekhar Nori 
Cc: Jingoo Han 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

rtc: rtc-omap: use module_platform_driver_probe()

2013-04-30T01:28:23+00:00

Use module_platform_driver_probe() macro which makes the code smaller and
simpler.

Signed-off-by: Jingoo Han 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

rtc: omap: add runtime pm support

2012-12-18T01:15:20+00:00

OMAP1 RTC driver is used in multiple devices like, OMAPL138 and AM33XX.
Driver currently doesn't handle any clocks, which may be right for OMAP1
architecture but in case of AM33XX, the clock/module needs to be enabled
in order to access the registers.

So convert this driver to runtime pm, which internally handles rest.

[afzal@ti.com: handle error path]
Signed-off-by: Vaibhav Hiremath 
Signed-off-by: Afzal Mohammed 
Acked-by: Sekhar Nori 
Cc: Grant Likely 
Cc: Sekhar Nori 
Cc: Kevin Hilman 
Cc: Russell King 
Cc: Alessandro Zummo 
Cc: Daniel Mack 
Cc: Vaibhav Hiremath 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

rtc: omap: dt support

2012-12-18T01:15:20+00:00

Enhance rtc-omap driver with DT capability

Signed-off-by: Afzal Mohammed 
Acked-by: Sekhar Nori 
Cc: Grant Likely 
Cc: Sekhar Nori 
Cc: Kevin Hilman 
Cc: Russell King 
Cc: Alessandro Zummo 
Cc: Daniel Mack 
Cc: Vaibhav Hiremath 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

rtc: omap: kicker mechanism support

2012-12-18T01:15:20+00:00

OMAP RTC IP can have kicker feature.  This prevents spurious writes to
register.  To write to registers kicker lock has to be released.
Procedure to do it as follows,

1. write to kick0 register, 0x83e70b13
2. write to kick1 register, 0x95a4f1e0

Writing value other than 0x83e70b13 to kick0 enables write locking, more
details about kicker mechanism can be found in section 20.3.3.5.3 of
AM335X TRM @www.ti.com/am335x

Here id table information is added and is used to distinguish those that
require kicker handling and the ones that doesn't need it.  There are more
features in the newer IP's compared to legacy ones other than kicker,
which driver currently doesn't handle, supporting additional features
would be easier with the addition of id table.

Older IP (of OMAP1) doesn't have revision register as per TRM, so revision
register can't be relied always to find features, hence id table is being
used.

While at it, replace __raw_writeb/__raw_readb with writeb/readb; this
driver is used on ARMv7 (AM335X SoC)

Signed-off-by: Afzal Mohammed 
Acked-by: Sekhar Nori 
Cc: Grant Likely 
Cc: Sekhar Nori 
Cc: Kevin Hilman 
Cc: Russell King 
Cc: Alessandro Zummo 
Cc: Daniel Mack 
Cc: Vaibhav Hiremath 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds