Hi Uwe, thanks for this interesting patch! On Mon, Oct 8, 2018 at 12:14 PM Uwe Kleine-König <uwe@xxxxxxxxxxxxxxxxx> wrote: > A gpio simulator device provides 2x 32 virtual GPIOs that are pairwise > connected. > > That is, if both GPIOs are configured as input both read a zero. If one > is an output the other reads the first's output value. > > This can for example be used to add a push button device on one side and > "push" it by driving the other side via gpioctl. > > Signed-off-by: Uwe Kleine-König <uwe@xxxxxxxxxxxxxxxxx> > --- > Hello, > > this is a patch that I intend to use to test a few patches that are > still on my todo list. > > Do you consider it interesting enough to be suitable for mainline? > > There is one issue (that I'm aware of): If the driver is unbound (via > sysfs) I get warnings that the gpios and/or irqs are still in use. Not > sure how to fix this properly. I would run this by Bartosz who maintains the gpio-mockup.c driver. I have basically two questions: 1. When compared to gpio-mockup.c, what features does this simulator offer that gpio-mockup doesn't already have? 2. Would it be possible to extend gpio-mockup.c to cover your usecases instead of introducing another unreal GPIO device? Vincent recently posted patches to even enable device tree probing of the mockup device, indicating that there is already some industrial use of that driver for prototyping. Yours, Linus Walleij