Feature #2742
Updated by Vadim Mutilin over 9 years ago
That is the correct order of function calls (in case of successful execution respectively):
<pre>
class_create
alloc_chrdev_region
usb_gadget_register_driver
usb_gadget_unregister_driver
unregister_chrdev_region
class_destroy
</pre>
This rule corresponds to _specific:usb:gadget_ class. 106_1a model will take care on this issue.
*Links*
Sample bugfix "2b9ec6c":https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=2b9ec6c