[PATCH v6 0/4] mfd: add support for Diolan DLN-2

From: Octavian Purdila
Date: Thu Sep 25 2014 - 12:10:19 EST


This patch series adds support for Diolan USB-I2C/GPIO Master Adapter
DLN-2. Details about device can be found here:

https://www.diolan.com/i2c/i2c_interface.html.

Changes since v5:

* MFD: use enum for handles, fix a couple of miss spells, rename a few
fields for clarity, rework the disconnect mechanism, fix a couple of
missing newlines in printks, use straight list_for_each instead of
RCU versions in the update sides, used busnum << 8 | devnum as id in
mfd_add_devices()

* GPIO: renamed pin_dir to output_enabled, disable GPIO if we failed
getting the direction, don't set platform's driver owner field

* I2C: update Documentation/ABI for the added sysfs attributed, stored
the port number in the dln2_i2c structure, used a temporary pointer
to the tx/rx struct for readability, don't set platform's driver
owner field

Daniel Baluta (1):
gpio: add support for the Diolan DLN-2 USB GPIO driver

Laurentiu Palcu (1):
i2c: add support for Diolan DLN-2 USB-I2C adapter

Octavian Purdila (2):
mfd: add support for Diolan DLN-2 devices
gpiolib: add irq_not_threaded flag to gpio_chip

.../ABI/testing/sysfs-bus-i2c-busses-dln2 | 5 +
drivers/gpio/Kconfig | 12 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-dln2.c | 556 +++++++++++++++
drivers/gpio/gpiolib.c | 2 +-
drivers/i2c/busses/Kconfig | 10 +
drivers/i2c/busses/Makefile | 1 +
drivers/i2c/busses/i2c-dln2.c | 378 +++++++++++
drivers/mfd/Kconfig | 9 +
drivers/mfd/Makefile | 1 +
drivers/mfd/dln2.c | 752 +++++++++++++++++++++
include/linux/gpio/driver.h | 3 +
include/linux/mfd/dln2.h | 67 ++
13 files changed, 1796 insertions(+), 1 deletion(-)
create mode 100644 Documentation/ABI/testing/sysfs-bus-i2c-busses-dln2
create mode 100644 drivers/gpio/gpio-dln2.c
create mode 100644 drivers/i2c/busses/i2c-dln2.c
create mode 100644 drivers/mfd/dln2.c
create mode 100644 include/linux/mfd/dln2.h

--
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/