1. 16 2月, 2013 1 次提交
  2. 14 2月, 2013 2 次提交
  3. 29 11月, 2012 4 次提交
  4. 22 11月, 2012 2 次提交
  5. 16 9月, 2012 2 次提交
    • J
      mfd: lpc_ich: Add Device IDs for Intel Lynx Point-LP PCH · 7fb9c1a4
      James Ralston 提交于
      This patch adds the Watchdog Timer Device IDs for the Intel Lynx Point-LP PCH.
      The Device IDs are defined in drivers/mfd/lpc_ich.c
      Signed-off-by: NJames Ralston <james.d.ralston@intel.com>
      Acked-by: NWim Van Sebroeck <wim@iguana.be>
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      7fb9c1a4
    • M
      mfd: core: Push irqdomain mapping out into devices · 0848c94f
      Mark Brown 提交于
      Currently the MFD core supports remapping MFD cell interrupts using an
      irqdomain but only if the MFD is being instantiated using device tree
      and only if the device tree bindings use the pattern of registering IPs
      in the device tree with compatible properties.  This will be actively
      harmful for drivers which support non-DT platforms and use this pattern
      for their DT bindings as it will mean that the core will silently change
      remapping behaviour and it is also limiting for drivers which don't do
      DT with this particular pattern.  There is also a potential fragility if
      there are interrupts not associated with MFD cells and all the cells are
      omitted from the device tree for some reason.
      
      Instead change the code to take an IRQ domain as an optional argument,
      allowing drivers to take the decision about the parent domain for their
      interrupts.  The one current user of this feature is ab8500-core, it has
      the domain lookup pushed out into the driver.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      0848c94f
  6. 14 9月, 2012 2 次提交
    • J
      gpio: gpio-ich: Share ownership of GPIO groups · 4f600ada
      Jean Delvare 提交于
      The ICH chips have their GPIO pins organized in 2 or 3 independent
      groups of 32 GPIO pins. It can happen that the ACPI BIOS wants to make
      use of pins in one group, preventing the OS to access these. This does
      not prevent the OS from accessing the other group(s).
      
      This is the case for example on my Asus Z8NA-D6 board. The ACPI BIOS
      wants to control GPIO 18 (group 1), while I (the OS) need to control
      GPIO 52 and 53 (group 2) for SMBus multiplexing.
      
      So instead of checking for ACPI resource conflict on the whole I/O
      range, check on a per-group basis, and consider it a success if at
      least one of the groups is available for the OS to use.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Cc: Peter Tyser <ptyser@xes-inc.com>
      Cc: Aaron Sierra <asierra@xes-inc.com>
      Cc: Grant Likely <grant.likely@secretlab.ca>
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      4f600ada
    • M
      mfd: core: Push irqdomain mapping out into devices · 55692af5
      Mark Brown 提交于
      Currently the MFD core supports remapping MFD cell interrupts using an
      irqdomain but only if the MFD is being instantiated using device tree
      and only if the device tree bindings use the pattern of registering IPs
      in the device tree with compatible properties.  This will be actively
      harmful for drivers which support non-DT platforms and use this pattern
      for their DT bindings as it will mean that the core will silently change
      remapping behaviour and it is also limiting for drivers which don't do
      DT with this particular pattern.  There is also a potential fragility if
      there are interrupts not associated with MFD cells and all the cells are
      omitted from the device tree for some reason.
      
      Instead change the code to take an IRQ domain as an optional argument,
      allowing drivers to take the decision about the parent domain for their
      interrupts.  The one current user of this feature is ab8500-core, it has
      the domain lookup pushed out into the driver.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      55692af5
  7. 24 8月, 2012 1 次提交
    • F
      mfd: lpc_ich: Fix a 3.5 kernel regression for iTCO_wdt driver · 092369ef
      Feng Tang 提交于
      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: NFeng 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: NSamuel Ortiz <sameo@linux.intel.com>
      092369ef
  8. 23 8月, 2012 1 次提交
    • F
      mfd: lpc_ich: Fix a 3.5 kernel regression for iTCO_wdt driver · a0e35322
      Feng Tang 提交于
      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: NFeng 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: NSamuel Ortiz <sameo@linux.intel.com>
      a0e35322
  9. 09 5月, 2012 1 次提交
  10. 01 5月, 2012 1 次提交