Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 09 5月, 2012 1 次提交
  3. 11 4月, 2012 1 次提交
  5. 08 4月, 2012 1 次提交
  7. 07 4月, 2012 1 次提交
  9. 23 3月, 2012 1 次提交
  11. 17 3月, 2012 1 次提交
  13. 04 2月, 2012 1 次提交
    • S
      gpio: Add a driver for Sodaville GPIO controller · b43ab901
      由 Sebastian Andrzej Siewior 提交于 
      Sodaville has GPIO controller behind the PCI bus. To my suprissed it is
not the same as on PXA.

The interrupt & gpio chip can be referenced from the device tree like
from any other driver. Unfortunately the driver which uses the gpio
interrupt has to use irq_of_parse_and_map() instead of
platform_get_irq(). The problem is that the platform device (which is
created from the device tree) is most likely created before the
interrupt chip is registered and therefore irq_of_parse_and_map() fails.

In theory the driver works as module. In reality most of the irq
functions are not exported to modules and it is possible that _this_
module is unloaded while the provided irqs are still in use.
Signed-off-by: NHans J. Koch <hjk@linutronix.de>
[torbenh@linutronix.de: make it work after the irq namespace cleanup,
	                add some device tree entries.]
Signed-off-by: NTorben Hohn <torbenh@linutronix.de>
[bigeasy@linutronix.de: convert to generic irq & gpio chip]
Signed-off-by: NSebastian Andrzej Siewior <bigeasy@linutronix.de>
[grant.likely@secretlab.ca: depend on x86 to avoid irq_domain breakage]
Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      b43ab901
  15. 30 1月, 2012 1 次提交
  17. 18 1月, 2012 1 次提交
  19. 05 1月, 2012 1 次提交
  21. 03 1月, 2012 1 次提交
  23. 20 12月, 2011 1 次提交
  25. 13 12月, 2011 1 次提交
  27. 28 11月, 2011 1 次提交
  29. 15 11月, 2011 1 次提交
  31. 24 10月, 2011 1 次提交
    • A
      mfd: remove CONFIG_MFD_SUPPORT · 8a0a8e8e
      由 Arnd Bergmann 提交于 
      We currently have two symbols to control compilation the MFD subsystem,
MFD_SUPPORT and MFD_CORE. The MFD_SUPPORT is actually not required
at all, it only hides the submenu when not set, with the effect that
Kconfig warns about missing dependencies when another driver selects
an MFD driver while MFD_SUPPORT is disabled. Turning the MFD submenu
back from menuconfig into a plain menu simplifies the Kconfig syntax
for those kinds of users and avoids the surprise when the menu
suddenly appears because another driver was enabled that selects this
symbol.
Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      8a0a8e8e
  33. 06 10月, 2011 2 次提交
  35. 23 9月, 2011 1 次提交
  37. 21 9月, 2011 4 次提交
  39. 08 9月, 2011 1 次提交
  41. 01 8月, 2011 3 次提交
  43. 16 7月, 2011 1 次提交
    • P
      mcp23s08: add i2c support · 752ad5e8
      由 Peter Korsgaard 提交于 
      Add i2c bindings for the mcp230xx devices. This is quite a lot simpler
than the spi one as there's no funky sub addressing done (one struct
i2c_client per struct gpio_chip).

The mcp23s08_platform_data structure is reused for i2c, even though
only a single mcp23s08_chip_info structure is needed.

To use, simply fill out a platform_data structure and pass it in
i2c_board_info, E.G.:

static const struct mcp23s08_platform_data mcp23017_data = {
	.chip[0] = {
		.pullups = 0x00ff,
	},
	.base = 240,
};

static struct i2c_board_info __initdata i2c_devs[] = {
	{ I2C_BOARD_INFO("mcp23017", 0x20),
	  .platform_data = &smartview_mcp23017_data, },
	...
};
Signed-off-by: NPeter Korsgaard <jacmet@sunsite.dk>
Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      752ad5e8
  45. 07 7月, 2011 2 次提交
  47. 09 6月, 2011 1 次提交
  49. 08 6月, 2011 1 次提交
  51. 07 6月, 2011 7 次提交
  53. 06 6月, 2011 1 次提交