diff options
| author | Bjorn Helgaas <bjorn.helgaas@hp.com> | 2008-10-14 17:01:03 -0600 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2008-10-14 16:30:14 -0700 |
| commit | 758a7f7bb86b520aadc484f23da85e547b3bf3d8 (patch) | |
| tree | d268b55fb9607f24e9433d900a260ca6d0bc1f7c /drivers/rtc/rtc-cmos.c | |
| parent | a474aaedac99ba86e28ef6c912a7647c482db6dd (diff) | |
| download | linux-758a7f7bb86b520aadc484f23da85e547b3bf3d8.tar.bz2 | |
x86: register a platform RTC device if PNP doesn't describe it
Most if not all x86 platforms have an RTC device, but sometimes the RTC
is not exposed as a PNP0b00/PNP0b01/PNP0b02 device in PNPBIOS or ACPI:
http://bugzilla.kernel.org/show_bug.cgi?id=11580
https://bugzilla.redhat.com/show_bug.cgi?id=451188
It's best if we can discover the RTC via PNP because then we know
which flavor of device it is, where it lives, and which IRQ it uses.
But if we can't, we should register a platform device using the
compiled-in RTC_PORT/RTC_IRQ resource assumptions.
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
Acked-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: David Brownell <dbrownell@users.sourceforge.net>
Reported-by: Rik Theys <rik.theys@esat.kuleuven.be>
Reported-by: shr_msn@yahoo.com.tw
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/rtc/rtc-cmos.c')
0 files changed, 0 insertions, 0 deletions