I would like to create an automated test-suite for libgpiod, but the gpio-mockup driver is quite limited when it comes to current user space functionality - I can't test neither line event notifications nor finding GPIO lines by name. This series proposes to extend the gpio framework by allowing to inject line events from the kernel code and by providing a debugfs interface for that to the gpio-mockup driver. We also allow the user to request that the mockup driver name the lines. The first patch contains only minor clean-ups. Patches 2/7-4/7 implement the in-kernel mechanism for injecting events, while patch 5/7 extends the mockup driver to provide a relevant debugfs interface. Patch 6/7 adds a new module param allowing to request naming of the lines. The last patch contains some coding style tweaks. Bartosz Golaszewski (7): gpiolib: clean up includes gpiolib: support monitoring mockup devices gpio: mockup: set the mockup flag in struct gpio_chip gpiolib: allow injecting line events gpio: mockup: implement injecting events over debugfs gpio: mockup: implement naming the GPIO lines gpio: mockup: readability tweaks drivers/gpio/gpio-dwapb.c | 1 - drivers/gpio/gpio-mockup.c | 147 +++++++++++++++++++++++++++++++++++++---- drivers/gpio/gpio-xgene-sb.c | 1 - drivers/gpio/gpiolib-acpi.c | 2 - drivers/gpio/gpiolib-devprop.c | 2 - drivers/gpio/gpiolib-legacy.c | 3 - drivers/gpio/gpiolib-of.c | 1 - drivers/gpio/gpiolib-sysfs.c | 2 - drivers/gpio/gpiolib.c | 44 +++++++++--- drivers/gpio/gpiolib.h | 5 ++ include/linux/gpio/driver.h | 4 ++ 11 files changed, 175 insertions(+), 37 deletions(-) -- 2.9.3 -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html