On Fri, 18 Sep 2009, [utf-8] MichaÅ? Nazarewicz wrote: > Hello everyone. > > This is continuation of my previous patchset introducing Mass > Storage composite Function. It fixes issue where MSF created > one thread per USB configuration it has been added to. > > > I would also like to ask, how you see solving a problem of > killing the kernel thread MSF is using. Currently this > problem is ignored (and it's probably the last thing I need > to fix prior to having the final version of MSF). I don't understand this question. Obviously the gadget can't work if the kernel thread is killed. So why is it a problem? > I was > thinking about creating a callback function from MSF back to > gadget that uses it which is called when thread exists. In > such setup it'll be gadget's responsibility to ensure it is > unregistered only once and to make decision as to how proceed. > > Also, in case of simple gadgets like MSG decision how to > proceed is probably simple -- do the same thing FSG does and > unregister itself but what more complicated gadgets shall do, > ie. gadgets which have MSF in only one configuration or where > MSF is only one of it's functionality? Why do you need to do anything besides unregistering the gadget/function? In theory you don't even need to do that much, but it makes things a little cleaner from the host's point of view. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
