Skip to content

more rtc framework/driver updates

David Brownell lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest6 patches 12 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/6rtc class /proc/driver/rtc updatedrivers/rtc/rtc-proc.c+4 -24 replies
2/6rtc-sa1100 tweaksdrivers/rtc/rtc-sa1100.c+6 -32 replies
3/6X86_PC optionally creates rtc_cmos platform devicearch/i386/kernel/setup.c arch/x86_64/kernel/setup.c+98 -280 replies
4/6ACPI exports RTC extensions through platform_datadrivers/acpi/glue.c include/linux/mc146818rtc.h+116 -00 replies
5/6rtc-cmos driverdrivers/acpi/sleep/proc.c drivers/rtc/Kconfig drivers/rtc/Makefile +1 more+775 -20 replies
6/6rtc-omap driverarch/arm/mach-omap1/devices.c drivers/rtc/Kconfig drivers/rtc/Makefile +1 more+582 -16 replies

Reviews trailers per patch

1 of 6 patches has a Reviewed-by or Acked-by.

PatchAlessandro Zummo
1/6
2/6
3/6
4/6
5/6
6/6A-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [patch 2.6.19-rc6 0/6] more rtc framework/driver updates

Here are more RTC framework updates, basically for the 2.6.20 queue:

- /proc/driver/rtc update ... display the 'struct rtc_wkalrm' status bits more sensibly (though the EFI "irq pending" flag is nonsense with an OS running)

- rtc-sa1100 update ... wasn't reporting "alarm enabled", and its extra procfs info duplicated information already found there

- X86_PC updates ... create an rtc_cmos platform device when PNPACPI isn't available do make one through PNP. (Non-PC platforms can do similar things if they have a "cmos" RTC.)

- Export ACPI RTC extensions through platform_data to the PNP device or the platform device, as appropriate.

- New "rtc-cmos" driver, for the RTC on most PCs. For most folk this seems like it should be able to replace drivers/char/rtc.c ...

- Newish "rtc-omap" driver, for the RTC on OMAP1 processors. No point in having this just live in the OMAP tree.

Folk wanting to try "rtc-cmos" will likely be wanting to tweak their /dev/rtc node to become a symlink to /dev/rtc0, at least until the new version of util-linux comes out (with updated "hwclock" knowing about the new RTC class devices).

- Dave