On Mon, Sep 07, 2020 at 12:26:34PM +0200, Bartosz Golaszewski wrote: > On Mon, Sep 7, 2020 at 11:59 AM Andy Shevchenko > <[email protected]> wrote: > > > > On Fri, Sep 04, 2020 at 08:15:59PM -0700, Randy Dunlap wrote: > > > On 9/4/20 8:45 AM, Bartosz Golaszewski wrote: > > > > ... > > > > > > +GPIO Testing Driver > > > > +=================== > > > > + > > > > +The GPIO Testing Driver (gpio-mockup) provides a way to create > > > > simulated GPIO > > > > +chips for testing purposes. There are two ways of configuring the > > > > chips exposed > > > > +by the module. The lines can be accessed using the standard GPIO > > > > character > > > > +device interface as well as manipulated using the dedicated debugfs > > > > directory > > > > +structure. > > > > > > Could configfs be used for this instead of debugfs? > > > debugfs is ad hoc. > > > > Actually sounds like a good idea. > > > > Well, then we can go on and write an entirely new mockup driver > (ditching module params and dropping any backwards compatibility) > because we're already using debugfs for line values. > > How would we pass the device properties to configfs created GPIO chips > anyway? Devices seem to only be created using mkdir. Am I missing > something?
Same way how USB composite works, no? -- With Best Regards, Andy Shevchenko
