Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 29 9月, 2016 1 次提交
  3. 24 11月, 2015 1 次提交
  5. 31 10月, 2015 1 次提交
  7. 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
  9. 22 6月, 2015 1 次提交
    • M
      mfd: lpc_ich: Assign subdevice ids automatically · 1abf25a2
      由 Mika Westerberg 提交于 
      Using -1 as platform device id means that the platform driver core will not
assign any id to the device (the device name will not have id at all). This
results problems on systems that have multiple PCHs (Platform Controller
HUBs) because all of them also include their own copy of LPC device.

All the subsequent device creations will fail because there already exists
platform device with the same name.

Fix this by passing PLATFORM_DEVID_AUTO as platform device id. This makes
the platform device core to allocate new ids automatically.
Signed-off-by: NMika Westerberg <mika.westerberg@linux.intel.com>
Signed-off-by: NLee Jones <lee.jones@linaro.org>
      1abf25a2
  11. 09 4月, 2015 1 次提交
  13. 30 3月, 2015 1 次提交
  15. 26 9月, 2014 2 次提交
  17. 03 6月, 2014 1 次提交
  19. 19 3月, 2014 9 次提交
  21. 21 1月, 2014 1 次提交
  23. 27 11月, 2013 1 次提交
  25. 05 11月, 2013 1 次提交
  27. 23 10月, 2013 1 次提交
  29. 01 8月, 2013 1 次提交
  31. 20 6月, 2013 1 次提交
  33. 18 6月, 2013 1 次提交
  35. 12 6月, 2013 1 次提交
  37. 16 2月, 2013 1 次提交
  39. 14 2月, 2013 2 次提交
  41. 29 11月, 2012 4 次提交
  43. 22 11月, 2012 2 次提交
  45. 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
  47. 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