On Fri, Sep 2, 2016 at 9:11 PM, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > On Fri, Sep 2, 2016 at 5:20 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxxx> wrote: >> >> Thoughts ? > > I really think this is a horrible hack. > > It's basically the kernel giving up, and relying on user space to give > a single flag, and it's broken nasty crap. Worse, it's broken nasty > crap with a user interface, so we'll be stuck with it forever. Please > no. I agree that interface is bad, but I do believe we need something like this... > > What are the drivers that need this, and why can't those drivers just > be fixed to not do braindead things? Like what? Some devices do need to have firmware loaded so we know their capabilities, so we really can't push the firmware loading into "open". If your touch controller for some reason decided to crap over it's nvram and comes in bootloader mode it is nice for it to slurp in config data or firmware so use does not have to trigger update manually. And while the controller is in bootloader mode we can't create input device because we do not know what capabilities to declare. These devices we want to probe asynchronously and simply tell firmware loader to wait for firmware to become available. The problem we do not know when to give up, since we do not know where the firmware might be. But userspace knows and can tel us. Thanks. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
