On Mon, Jan 09, 2023 at 04:00:35PM +0200, Andy Shevchenko wrote: > On Mon, Jan 09, 2023 at 02:41:24PM +0100, Geert Uytterhoeven wrote: > > On Mon, Jan 9, 2023 at 2:16 PM Linus Walleij <linus.walleij@xxxxxxxxxx> wrote: > > > On Tue, Jan 3, 2023 at 10:01 AM Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote: > > > > > If this should go into sysfs we should probably create something > > > > > generic, such as a list of stuff to be exported as sysfs switches. > > > > > > > > > > It generally also looks really dangerous, which is another reason > > > > > for keeping it in debugfs. It's the big hammer to hurt yourself with, > > > > > more or less. > > > > > > > > Yes, generic would be nice. Anyone familiar with other hardware > > > > that could make use of this? > > > > > > Drew was using this for Beagle Bone IIRC, Drew? > > > > Yes, that's what I remember, too. And I tested it on Koelsch. > > > > But again, that's for debugging purposes. For non-debugging > > operation, we need something different. > > I really would like to know the use case when you need to mux pins at run time. > And the guarantee it won't break users' devices into smoke or killing somebody > playing with robots. Btw, I might agree on having something like this in production, but enabling it should print a BIG warning that the functionality is DANGEROUS. Something like trace_printk() has. -- With Best Regards, Andy Shevchenko
