1. 04 1月, 2017 1 次提交
  2. 11 8月, 2015 1 次提交
    • M
      mfd: watchdog: iTCO_wdt: Expose watchdog properties using platform data · 420b54de
      Matt Fleming 提交于
      Intel Sunrisepoint (Skylake PCH) has the iTCO watchdog accessible across
      the SMBus, unlike previous generations of PCH/ICH where it was on the
      LPC bus. Because it's on the SMBus, it doesn't make sense to pass around
      a 'struct lpc_ich_info', and leaking the type of bus into the iTCO
      watchdog driver is kind of backwards anyway.
      
      This change introduces a new 'struct itco_wdt_platform_data' for use
      inside the iTCO watchdog driver and by the upcoming Intel Sunrisepoint
      code, which neatly avoids having to include lpc_ich headers in the i801
      i2c driver.
      
      This change is overdue because lpc_ich_info has already found its way
      into other TCO watchdog users, notably the intel_pmc_ipc driver where
      the watchdog actually isn't on the LPC bus as far as I can see.
      
      A simple translation layer is provided for converting from the existing
      'struct lpc_ich_info' inside the lpc_ich mfd driver.
      Signed-off-by: NMatt Fleming <matt.fleming@intel.com>
      Acked-by: Darren Hart <dvhart@linux.intel.com> [drivers/x86 refactoring]
      Reviewed-by: NGuenter Roeck <linux@roeck-us.net>
      Signed-off-by: NLee Jones <lee.jones@linaro.org>
      420b54de
  3. 19 3月, 2014 3 次提交
  4. 14 9月, 2012 1 次提交
    • 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
  5. 09 5月, 2012 1 次提交
  6. 01 5月, 2012 1 次提交