summaryrefslogtreecommitdiffstats
path: root/drivers/mfd/mfd-core.c
diff options
context:
space:
mode:
authorFeng Tang <feng.tang@intel.com>2012-08-16 15:50:10 +0800
committerSamuel Ortiz <sameo@linux.intel.com>2012-08-23 16:51:01 +0200
commita0e35322910555e20e9eced3f050a76c7b3a1f92 (patch)
treeaac56e9a92c5fc1f660965939434ae95960df77e /drivers/mfd/mfd-core.c
parent1922b0f2758badc0b971d1ebbd300bc6635a6aef (diff)
downloadop-kernel-dev-a0e35322910555e20e9eced3f050a76c7b3a1f92.zip
op-kernel-dev-a0e35322910555e20e9eced3f050a76c7b3a1f92.tar.gz
mfd: lpc_ich: Fix a 3.5 kernel regression for iTCO_wdt driver
There are many reports (including 2 of my machines) that iTCO_wdt watchdog driver fails to be initialized in 3.5 kernel with error message like: [ 5.265175] ACPI Warning: 0x00001060-0x0000107f SystemIO conflicts with Region \_SB_.PCI0.LPCB.TCOI 1 (20120320/utaddress-251) [ 5.265192] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 5.265206] lpc_ich: Resource conflict(s) found affecting iTCO_wdt The root cause the iTCO_wdt driver in 3.4 probes the HW IO resource from LPC's PCI config space, while in 3.5 kernel it relies on lpc_ich driver for the probe, which adds a new acpi_check_resource_conflict() check, and give up the probe if there is any conflict with ACPI. Fix it by removing all the checks for iTCO_wdt to keep the same behavior as 3.4 kernel. https://bugzilla.kernel.org/show_bug.cgi?id=44991 Actually the same check could be removed for the gpio-ich in lpc_ich.c, but I'm not sure if it will cause problems. Signed-off-by: Feng Tang <feng.tang@intel.com> Cc: Aaron Sierra <asierra@xes-inc.com> Cc: Wim Van Sebroeck <wim@iguana.be> Cc: Len Brown <len.brown@intel.com> Cc: Bob Moore <robert.moore@intel.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Diffstat (limited to 'drivers/mfd/mfd-core.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud