linux.git/drivers/rtc/rtc-sh.c, branch v2.6.23

rtc: rtc-sh: Correct sh_rtc_set_time() for some SH-3 parts.

2007-07-26T08:31:28+00:00

Some SH-3 parts (SH7720 and SH7705 at least) need to have the
start bit explicitly cleared, as the reset is not enough. This
is safe across all parts, so simply clear the start bit in
the sh_rtc_set_time() path.

Signed-off-by: Markus Brunner 
Signed-off by: Mark Jonas 
Signed-off-by: Paul Mundt

rtc: rtc-sh: Fix rtc_dev pointer for rtc_update_irq().

2007-05-09T03:37:53+00:00

When the rtc_update_irq() callsites stopped passing in the
class_dev, the rtc_dev references weren't fixed. Fix it up,
so we pass in the proper pointer.

Signed-off-by: Paul Mundt

rtc: rtc-sh: Fix up dev_dbg() warnings.

2007-05-09T01:35:00+00:00

Signed-off-by: Paul Mundt

rtc: rtc interfaces don't use class_device

2007-05-08T18:15:18+00:00

This patch removes class_device from the programming interface that the RTC
framework exposes to the rest of the kernel.  Now an rtc_device is passed,
which is more type-safe and streamlines all the relevant code.

Signed-off-by: David Brownell 
Acked-by: Greg Kroah-Hartman 
Acked-By: Alessandro Zummo 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] rtc-sh: act on rtc_wkalrm.enabled when setting an alarm

2007-01-23T15:52:06+00:00

This fixes the SH rtc driver correctly act on the "enabled" flag when
setting an alarm.

Signed-off-by: Jamie Lenehan 
Cc: David Brownell 
Cc: Alessandro Zummo 
Cc: Paul Mundt 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] rtc-sh: correctly report rtc_wkalrm.enabled

2007-01-12T02:18:20+00:00

This fixes the SH rtc driver to
  (a) correctly report 'enabled' status with other alarm status;
  (b) not duplicate that status in its procfs dump

Signed-off-by: David Brownell 
Acked-by: Paul Mundt 
Cc: Alessandro Zummo 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

rtc: rtc-sh: alarm support.

2006-12-11T23:42:08+00:00

This adds alarm support for the RTC_ALM_SET, RTC_ALM_READ,
RTC_WKALM_SET and RTC_WKALM_RD operations to rtc-sh.

The only unusual part is the handling of the alarm interrupt. If you
clear the alarm flag (AF) while the time in the RTC still matches the
time in the alarm registers than AF is immediately re-set, and if the
alarm interrupt (AIE) is still enabled then it re-triggers. I was
originally getting around 20k+ interrupts generated during the second
when the RTC and alarm registers matches.

The solution I've used is to clear AIE when the alarm goes off and
then use the carry interrupt to re-enabled it. The carry interrupt
will check AF and re-enabled AIE if it's clear. If AF is not clear
it'll clear it and then the check will be repeated next carry
interrupt. This a bit in rtc structure that indicates that it's
waiting to have AIE re-enabled so it doesn't turn it on when it
wasn't enabled anyway.

Signed-off-by: Jamie Lenehan 
Signed-off-by: Paul Mundt

rtc: rtc-sh: fix rtc for out-by-one for the month.

2006-12-11T23:42:08+00:00

The RMONCNT register, which holds the month in the RTC, takes a value
between 1 and 12 while the tm_mon field in the time structures takes
a value between 0 and 11. This wasn't being taken into account in
rtc-sh resulting in the month being out by one.

eg, on my board during boot the RTC is set to:

  RTC is set to Thu Jul 01 09:00:00 1999

but "hwclock -r" immediately after logging in was showing:

  Sun Aug  1 09:01:43 1999  0.000000 seconds

Signed-off-by: Jamie Lenehan 
Signed-off-by: Paul Mundt

rtc: rtc-sh: fix for period rtc interrupts.

2006-12-11T23:42:07+00:00

When testing the per second interrupt support (RTC_UIE_ON/RTC_UIE_OFF)
of the new RTC system it would die in sh_rtc_interrupt due to a null
ptr dereference. The following gets it working correctly.

Signed-off-by: Jamie Lenehan 
Signed-off-by: Paul Mundt

sh: Updates for IRQ handler changes.

2006-10-06T06:31:16+00:00

Trivial fixes for build breakage introduced by IRQ handler changes.

Signed-off-by: Paul Mundt