RFC RTC subsystem
Get series with b4
b4 am 20051226201901.54288289@inspironVersions newest first
- v1 RFC Latest7 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/7 | RTC subsystem, classdrivers/ drivers/ drivers/ +5 more | +403 | 0 replies | |
| 2/7 | RTC subsystem, ARM cleanuparch/ arch/ | +14 | 0 replies | |
| 3/7 | RTC subsystem, sysfs interfacedrivers/ drivers/ drivers/ | +111 | 0 replies | |
| 4/7 | RTC subsystem, proc interfacedrivers/ drivers/ drivers/ | +158 | 0 replies | |
| 5/7 | RTC subsystem, dev interfacedrivers/ drivers/ drivers/ | +371 | 0 replies | |
| 6/7 | RTC subsystem, x1205 driverdrivers/ drivers/ drivers/ | +740 | 0 replies | |
| 7/7 | RTC subsystem, test device/driverdrivers/ drivers/ drivers/ | +212 | 2 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC][PATCH 0/7] RTC subsystem
Hello,
thanks to all the suggestions I've got, I've
updated my proposal [1] for an RTC subsystem.
I tried to implement locking wherever necessary.
I'm on vacations right now and I don't have all the feedback emails at handy, so I'm sure I've forgot something.
I've left some XXX in the points where I have
doubts.
The dev interface now supports multiple RTCs and
hotplug events are generated whenever an RTC is added/removed.
Those udev lines can be used to create the device nodes
ACTION=="add", SUBSYSTEM=="rtc", ENV{MAJOR}=="[0-9]*", NAME="rtc%m"
ACTION=="add", SUBSYSTEM=="rtc", ENV{MINOR}=="0", SYMLINK+="rtc"
I also added a test device/driver which can be used
to excercize the APIs. This device can also generate interrupts using the sysfs interface (more details in the path).
hwclock seems to work fine, both in polling
and IRQ modes.
Signature · 9 lines
Best regards, Alessandro Zummo, Tower Technologies - Turin, Italy http://www.towertech.it [1] http://lkml.org/lkml/2005/12/20/220