Messages in this thread | | | From | Linus Walleij <> | Date | Tue, 31 Jan 2017 14:28:44 +0100 | Subject | Re: [PATCH 0/7] gpio: mockup: extensions for testing purposes |
| |
On Wed, Jan 25, 2017 at 4:34 PM, Bartosz Golaszewski <bgolaszewski@baylibre.com> wrote:
> 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.
I sympathize fully with the goal and intentions of the series, I agree: this is awesome to have for testing and validation of GPIO.
I'm reluctant about the changes to gpiolib and want to make that code as optional as possible, definately #ifdef if nothing else works. Otherwise the memory footprint people will get me for this, haha. ;)
The absolutely best would be if the driver could inject "real" irqs and also exercise the gpiolib irqchip helpers. I have been vaguely thinking that sofware interrupts should be able to do this but I'm not very versed in that kind of stuff.
The changes to gpio-mockup.c are entirely uncontroversial, it is for testing so I'm willing to accept almost anything if it looks maintainable and helps in testing.
Yours, Linus Walleij
| |