From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Joel Becker <jlbec@evilplan.org>, Christoph Hellwig <hch@lst.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jonathan Corbet <corbet@lwn.net>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Kent Gibson <warthog618@gmail.com>,
linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH 0/8] gpio: implement the configfs testing module
Date: Sat, 30 Jan 2021 22:20:09 +0100 [thread overview]
Message-ID: <20210130212009.2uugdj6vmisegau2@pengutronix.de> (raw)
In-Reply-To: <20210129134624.9247-1-brgl@bgdev.pl>
[-- Attachment #1: Type: text/plain, Size: 2062 bytes --]
Hello,
On Fri, Jan 29, 2021 at 02:46:16PM +0100, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>
> This series adds a new GPIO testing module based on configfs committable items
> and sysfs. The goal is to provide a testing driver that will be configurable
> at runtime (won't need module reload) and easily extensible. The control over
> the attributes is also much more fine-grained than in gpio-mockup.
>
> I am aware that Uwe submitted a virtual driver called gpio-simulator some time
> ago and I was against merging it as it wasn't much different from gpio-mockup.
> I would ideally want to have a single testing driver to maintain so I am
> proposing this module as a replacement for gpio-mockup but since selftests
> and libgpiod depend on it and it also has users in the community, we can't
> outright remove it until everyone switched to the new interface. As for Uwe's
> idea for linking two simulated chips so that one controls the other - while
> I prefer to have an independent code path for controlling the lines (hence
> the sysfs attributes), I'm open to implementing it in this new driver. It
> should be much more feature friendly thanks to configfs than gpio-mockup.
Funny you still think about my simulator driver. I recently thought
about reanimating it for my private use. The idea was to implement a
rotary-encoder driver (that contrast to
drivers/input/misc/rotary_encoder.c really implements an encoder and not
a decoder). With the two linked chips I can plug
drivers/input/misc/rotary_encoder.c on one side and my encoder on the
other to test both drivers completely in software.
I didn't look into your driver yet, but getting such a driver into
mainline would be very welcome!
I intend to look into your driver next week, but please don't hold back
on merging for my feedback.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-01-30 21:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210129134624.9247-1-brgl@bgdev.pl>
[not found] ` <20210129134624.9247-6-brgl@bgdev.pl>
[not found] ` <YBQw3+K/6GDPK5xa@smile.fi.intel.com>
2021-01-30 20:25 ` [PATCH 5/8] lib: bitmap: remove the 'extern' keyword from function declarations Bartosz Golaszewski
2021-02-01 10:19 ` Andy Shevchenko
[not found] ` <20210129134624.9247-9-brgl@bgdev.pl>
[not found] ` <YBQwUkQz3LrG5G4i@smile.fi.intel.com>
2021-01-30 20:37 ` [PATCH 8/8] gpio: sim: new testing module Bartosz Golaszewski
2021-01-31 0:43 ` Kent Gibson
2021-02-01 8:37 ` Bartosz Golaszewski
2021-02-01 10:28 ` Andy Shevchenko
2021-02-01 10:59 ` Bartosz Golaszewski
2021-02-01 12:49 ` Andy Shevchenko
2021-02-01 12:53 ` Bartosz Golaszewski
2021-02-01 13:30 ` Andy Shevchenko
2021-01-30 21:20 ` Uwe Kleine-König [this message]
2021-02-01 8:37 ` [PATCH 0/8] gpio: implement the configfs " Bartosz Golaszewski
2021-02-01 9:24 ` Uwe Kleine-König
2021-02-01 12:50 ` Bartosz Golaszewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210130212009.2uugdj6vmisegau2@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=corbet@lwn.net \
--cc=geert@linux-m68k.org \
--cc=hch@lst.de \
--cc=jlbec@evilplan.org \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=warthog618@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).