i2c: Add support for Xilinx XPS IIC Bus Interface
Subsystems (2)
PATCH v2 1/1 i2c: Add support for Xilinx XPS IIC Bus Interface
This patch adds support for the Xilinx XPS IIC Bus Interface.
The driver uses the dynamic mode, supporting to put several I2C messages in the FIFO to reduce the number of interrupts.
It has the same feature as ocores, it can be passed a list of devices that will be added when the bus is probed.
---
drivers/i2c/busses/Kconfig +10 -0
@@ -433,6 +433,16 @@ config I2C_OCORES This driver can also be built as a module. If so, the module will be called i2c-ocores. +config I2C_XILINX + tristate "Xilinx I2C Controller" + depends on EXPERIMENTAL && HAS_IOMEM + help + If you say yes to this option, support will be included for the + Xilinx I2C controller. + + This driver can also be built as a module. If so, the module + will be called xilinx_i2c. + config I2C_OMAP tristate "OMAP I2C adapter" depends on ARCH_OMAP
drivers/i2c/busses/Makefile +1 -0
@@ -40,6 +40,7 @@ obj-$(CONFIG_I2C_IXP2000) += i2c-ixp2000.o obj-$(CONFIG_I2C_MPC) += i2c-mpc.o obj-$(CONFIG_I2C_MV64XXX) += i2c-mv64xxx.o obj-$(CONFIG_I2C_OCORES) += i2c-ocores.o +obj-$(CONFIG_I2C_XILINX) += i2c-xiic.o obj-$(CONFIG_I2C_OMAP) += i2c-omap.o obj-$(CONFIG_I2C_PASEMI) += i2c-pasemi.o obj-$(CONFIG_I2C_PNX) += i2c-pnx.o
drivers/i2c/busses/i2c-xiic.c new file +802 -0
802 lines not on this page · raw message
include/linux/i2c-xiic.h new file +43 -0
43 lines not on this page · raw message
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 36 lines · Richard Röjfors
This patch adds support for the Xilinx XPS IIC Bus Interface.
The driver uses the dynamic mode, supporting to put several I2C messages in the FIFO to reduce the number of interrupts.
It has the same feature as ocores, it can be passed a list of devices that will be added when the bus is probed.
Signed-off-by Richard Röjfors <[email protected]>---
drivers/i2c/busses/Kconfig +10
-0@@ -433,6 +433,16 @@ config I2C_OCORES This driver can also be built as a module. If so, the module will be called i2c-ocores. +config I2C_XILINX + tristate "Xilinx I2C Controller" + depends on EXPERIMENTAL && HAS_IOMEM + help + If you say yes to this option, support will be included for the + Xilinx I2C controller. + + This driver can also be built as a module. If so, the module + will be called xilinx_i2c. + config I2C_OMAP tristate "OMAP I2C adapter" depends on ARCH_OMAPdrivers/i2c/busses/Makefile +0
-0
drivers/i2c/busses/Makefile obj-$(CONFIG_I2C_IXP2000) += i2c-ixp2000.o · line 46
Quoted 7 lines
drivers/i2c/busses/Makefile +1
-0@@ -40,6 +40,7 @@ obj-$(CONFIG_I2C_IXP2000) += i2c-ixp2000.o obj-$(CONFIG_I2C_MPC) += i2c-mpc.o obj-$(CONFIG_I2C_MV64XXX) += i2c-mv64xxx.o obj-$(CONFIG_I2C_OCORES) += i2c-ocores.o +obj-$(CONFIG_I2C_XILINX) += i2c-xiic.o obj-$(CONFIG_I2C_OMAP) += i2c-omap.o obj-$(CONFIG_I2C_PASEMI) += i2c-pasemi.o obj-$(CONFIG_I2C_PNX) += i2c-pnx.o
You have an interesting notion of alphabetical order.
Signature · 1 line
Jean Delvare
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 9 lines · Jean Delvare
Quoted 9 lines
config
I2C_OMAPdrivers/i2c/busses/Kconfig +0
-0tristate "OMAP I2C adapter" depends on ARCH_OMAPdrivers/i2c/busses/Makefile +0
-0@@ -40,6 +40,7 @@ obj-$(CONFIG_I2C_IXP2000) += i2c-ixp2000.o obj-$(CONFIG_I2C_MPC) += i2c-mpc.o
Quoted 8 lines
drivers/i2c/busses/Makefile obj-$(CONFIG_I2C_IXP2000) += i2c-ixp2000.o · line 46
Quoted 6 lines
drivers/i2c/busses/Makefile +1
-0obj-$(CONFIG_I2C_MV64XXX) += i2c-mv64xxx.o obj-$(CONFIG_I2C_OCORES) += i2c-ocores.o +obj-$(CONFIG_I2C_XILINX) += i2c-xiic.o obj-$(CONFIG_I2C_OMAP) += i2c-omap.o obj-$(CONFIG_I2C_PASEMI) += i2c-pasemi.o obj-$(CONFIG_I2C_PNX) += i2c-pnx.oYou have an interesting notion of alphabetical order.
:-)
New patch on its way...
--Richard