Messages in this thread | | | From | Bartosz Golaszewski <> | Date | Mon, 7 Sep 2020 17:14:58 +0200 | Subject | Re: [PATCH 23/23] Documentation: gpio: add documentation for gpio-mockup |
| |
On Mon, Sep 7, 2020 at 4:08 PM Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote: > > On Mon, Sep 07, 2020 at 03:49:23PM +0200, Bartosz Golaszewski wrote: > > On Mon, Sep 7, 2020 at 2:22 PM Greg Kroah-Hartman > > <gregkh@linuxfoundation.org> wrote: > > > On Mon, Sep 07, 2020 at 02:06:15PM +0200, Bartosz Golaszewski wrote: > > ... > > > > Yes it is. Or at least until you fix all existing users so that if you > > > do change it, no one notices it happening :) > > > > > > > Then another question is: do we really want to commit to a stable ABI > > for a module we only use for testing purposes and which doesn't > > interact with any real hardware. > > > > Rewriting this module without any legacy cruft is tempting though. :) > > Another thought spoken loudly: maybe it can be unified with GPIO aggregator > code? In that case it makes sense. >
Cc'ing Geert but I don't quite see how this would make sense. :)
Also one thing I'm not sure about re configfs is the interface we use to read values/set pull i.e. the line attributes in debugfs, do you think configfs allows this type of attributes?
Bart
| |