]> git.kernelconcepts.de Git - karo-tx-linux.git/commit
x86: register a platform RTC device if PNP doesn't describe it
authorBjorn Helgaas <bjorn.helgaas@hp.com>
Sun, 26 Oct 2008 22:57:33 +0000 (18:57 -0400)
committerGreg Kroah-Hartman <gregkh@suse.de>
Fri, 7 Nov 2008 03:05:51 +0000 (19:05 -0800)
commitdcfdc4faa0dbe2aa4c68a43c79dc7eb630788351
tree279d7797bd405b3a874ae8a07b4392d6234b837a
parent3fd1740d9b92fabf8d00c9c6208af0c18e44da1f
x86: register a platform RTC device if PNP doesn't describe it

commit 758a7f7bb86b520aadc484f23da85e547b3bf3d8 upstream

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
Cc: Chuck Ebbert <cebbert@redhat.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
arch/x86/kernel/rtc.c