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

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

drivers/rtc: remove IRQF_DISABLED

2012-03-23T23:58:39+00:00

Since commit e58aa3d2d0cc ("genirq: run irq handlers with interrupts
disabled") we run all interrupt handlers with interrupts disabled and we
even check and yell when an interrupt handler returns with interrupts
enabled - see commit b738a50a2026 ("genirq: warn when handler enables
interrupts").

So now this flag is a NOOP and can be removed.

Signed-off-by: Yong Zhang 
Acked-by: Linus Walleij 
Acked-by: Wan ZongShun 
Cc: Alessandro Zummo 
Cc: Thomas Gleixner 
Cc: Ingo Molnar 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

rtc-omap: fix initialization of control register

2011-08-04T00:25:20+00:00

As the comment explains, the intention of the code is to clear the
OMAP_RTC_CTRL_MODE_12_24 bit, but instead it only clears the
OMAP_RTC_CTRL_SPLIT and OMAP_RTC_CTRL_AUTO_COMP bits, which should be
kept.  OMAP_RTC_CTRL_DISABLE, OMAP_RTC_CTRL_SET_32_COUNTER,
OMAP_RTC_CTRL_TEST, and OMAP_RTC_CTRL_ROUND_30S are also better off
being cleared.

Signed-off-by: Daniel Glöckner 
Cc: Alessandro Zummo 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

RTC: rtc-omap: Fix a leak of the IRQ during init failure

2011-04-18T08:39:38+00:00

In omap_rtc_probe error path, free_irq() was using NULL rather than the
driver data as the data pointer so free_irq() wouldn't have matched.

Signed-off-by: Axel Lin 
Cc: "George G. Davis" 
Cc: Alessandro Zummo 
Cc: rtc-linux@googlegroups.com
Link: http://lkml.kernel.org/r/%3C1303005778.2889.2.camel%40phoenix%3E
Signed-off-by: Thomas Gleixner

RTC: Clean out UIE icotl implementations

2011-03-09T19:24:54+00:00

With the generic RTC rework, the UIE mode irqs are handled
in the generic layer, and only hardware specific ioctls
get passed down to the rtc driver layer.

So this patch removes the UIE mode ioctl handling in the rtc
driver layer, which never get used.

CC: Thomas Gleixner 
CC: Alessandro Zummo 
CC: Marcelo Roberto Jimenez 
CC: rtc-linux@googlegroups.com
Signed-off-by: John Stultz

RTC: Convert rtc drivers to use the alarm_irq_enable method

2011-02-03T21:02:35+00:00

Some rtc drivers use the ioctl method instead of the alarm_irq_enable
method for enabling alarm interupts. With the new virtualized RTC
rework, its important for drivers to use the alarm_irq_enable instead.

This patch converts the drivers that use the AIE ioctl method to
use the alarm_irq_enable method. Other ioctl cmds are left untouched.

I have not been able to test or even compile most of these drivers.
Any help to make sure this change is correct would be appreciated!

CC: Alessandro Zummo 
CC: Thomas Gleixner 
CC: Marcelo Roberto Jimenez 
Reported-by: Marcelo Roberto Jimenez 
Tested-by: Marcelo Roberto Jimenez 
Signed-off-by: John Stultz

drivers/rtc/rtc-omap.c: fix a memory leak

2011-01-13T16:03:12+00:00

request_mem_region() will call kzalloc to allocate memory for struct
resource.  release_resource() unregisters the resource but does not free
the allocated memory, thus use release_mem_region() instead to fix the
memory leak.

Also add a missing iounmap() in omap_rtc_remove().

Signed-off-by: Axel Lin 
Cc: Alessandro Zummo 
Cc: Sekhar Nori 
Cc: Kevin Hilman 
Cc: Tony Lindgren 
Acked-by: Mark A. Greer 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

rtc: omap: let device wakeup capability be configured from chip init logic

2010-10-28T01:03:06+00:00

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 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 
Signed-off-by: Kevin Hilman 
Cc: Alessandro Zummo 
Cc: Wan ZongShun 
Cc: Tony Lindgren 
Cc: David Brownell 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds