linux.git/drivers/rtc, branch v2.6.26-rc7

rtc: Ramtron FM3130 RTC support

2008-06-13T01:05:42+00:00

Ramtron FM3130 is a chip with two separate devices inside, RTC clock and
FRAM.  This driver provides only RTC functionality.

This chip is met in lots of custom boards with AT91SAMXXXX CPU I work
with, is cheap and in no way better or worse than any other RTC on market.
 While it is mostly met on much smaller devices, I think it is great to
have it supported in Linux.

Signed-off-by: Sergey Lapin 
Signed-off-by: Alessandro Zummo 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

provide rtc_cmos platform device

2008-06-13T01:05:42+00:00

Recently (around 2.6.25) I've noticed that RTC no longer works for me.  It
turned out this is because I use pnpacpi=off kernel option to work around
the parport_pc bugs.  I always did so, but RTC used to work fine in the
past, and now it have regressed.

The patch fixes the problem by creating the platform device for the RTC
when PNP is disabled.  This may also help running the PNP-enabled kernel
on an older PCs.

Signed-off-by: Stas Sergeev 
Cc: David Brownell 
Cc: Ingo Molnar 
Cc: Thomas Gleixner 
Cc: Bjorn Helgaas 
Cc: Adam Belay 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

rtc-at32ap700x: fix bug in at32_rtc_readalarm()

2008-06-13T01:05:40+00:00

alarm->pending indicates whether there's an alarm that has actually been
triggered, not whether we're waiting for it.  alarm->enabled indicates
that.

Also add missing locking around reading the RTC registers.

Signed-off-by: Haavard Skinnemoen 
Signed-off-by: Alessandro Zummo 
Cc: Hans-Christian Egtvedt 
Cc: David Brownell 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

rtc: class driver for ppc_md RTC functions

2008-06-06T18:29:13+00:00

This hooks up the platform-specific [gs]et_rtc_time functions so that
kernels using CONFIG_RTC_CLASS have RTC support on most PowerPC platforms.

A new driver, and one which we've been shipping in Fedora for a while
already, since otherwise RTC support breaks.

[akpm@linux-foundation.org: fix Kconfig indenting]
Signed-off-by: David Woodhouse 
Signed-off-by: Paul Mackerras 
Acked-by: Alessandro Zummo 
Acked-by: David Brownell 
Cc: Benjamin Herrenschmidt 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

rtc-ds1374: rename device to just "ds1374"

2008-06-06T18:29:10+00:00

Change the name of the device from "rtc-ds1374" to just "ds1374", to match
what all other RTC drivers do.  I seem to remember that this name was
chosen to avoid possible confusion with an older ds1374 driver, but that
driver was removed 3 months ago.

Signed-off-by: Jean Delvare 
Signed-off-by: Alessandro Zummo 
Acked-by: Kumar Gala 
Cc: Paul Mackerras 
Cc: Benjamin Herrenschmidt 
Cc: David Brownell 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

rtc: m41t80: include for printk()

2008-05-13T15:02:26+00:00

The driver uses printk(), but does not include  -- add it.

Signed-off-by: Maciej W. Rozycki 
Cc: Alessandro Zummo 
Cc: Alexander Bigga 
Cc: Wim Van Sebroeck 
Cc: David Brownell 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

RTC/watchdog: M41T80: fix a potential use of unitialized data

2008-05-13T15:02:26+00:00

Watchdog handlers within the driver make use of "save_client" -- make sure it
has been initalized before the handlers are registered.

Signed-off-by: Maciej W. Rozycki 
Cc: Alessandro Zummo 
Cc: Alexander Bigga 
Cc: Wim Van Sebroeck 
Cc: David Brownell 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

rtc: rtc_time_to_tm: use unsigned arithmetic

2008-05-13T15:02:25+00:00

The input argument to rtc_time_to_tm() is unsigned as well as are members of
the output structure.  However signed arithmetic is used within for
calculations leading to incorrect results for input values outside the signed
positive range.  If this happens the time of day returned is out of range.

Found the problem when fiddling with the RTC and the driver where year was set
to an unexpectedly large value like 2070, e.g.:

rtc0: setting system clock to 2070-01-01 1193046:71582832:26 UTC (3155760954)

while it should be:

rtc0: setting system clock to 2070-01-01 00:15:54 UTC (3155760954)

Changing types to unsigned fixes the problem.

[akpm@linux-foundation.org: remove old-fashioned `register' keyword]
Signed-off-by: Maciej W. Rozycki 
Cc: Alessandro Zummo 
Cc: David Brownell 
Cc: Dmitri Vorobiev 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

i2c: Match dummy devices by type

2008-05-11T18:37:06+00:00

As the old driver_name/type matching scheme is going away soon, change
the dummy device mechanism to use the new matching scheme.

This has the downside that dummy i2c clients can no longer choose
their name, they'll all appear as "dummy" in sysfs and in log
messages. I don't think it is a problem in practice though, as there
is little reason to use these i2c clients to log messages.

Signed-off-by: Jean Delvare

Merge git://git.kernel.org/pub/scm/linux/kernel/git/lethal/sh-2.6

2008-05-09T15:07:58+00:00

* git://git.kernel.org/pub/scm/linux/kernel/git/lethal/sh-2.6: (37 commits)
  SH: catch negative denormal_subf1() retval in denormal_add()
  sh: Fix DMAC base address for SH7709S
  sh: update smc91x platform data for se7206.
  sh: Stub in cpu_to_node() and friends for NUMA build.
  sh: intc register modify fix
  sh: no high level trigger on some sh3 cpus
  sh: clean up sh7710 and sh7720 intc tables
  sh: add interrupt ack code to sh3
  sh: unify external irq pin code for sh3
  sh-sci: avoid writing to nonexistent registers
  sh-sci: sh7722 lacks scsptr registers
  sh-sci: improve sh7722 support
  sh: reset hardware from early printk
  sh: drain and wait for early printk
  sh: use sci_out() for early printk
  sh: add memory resources to /proc/iomem
  sh: add kernel bss resource
  sh: fix sh7705 interrupt vector typo
  sh: update smc91x platform data for se7722
  sh: update smc91x platform data for MigoR
  ...