Searched hist:"43 a029724d1c8219cc4e58e9fafbeedd1bc283fa" (Results 1 – 3 of 3) sorted by relevance
| /linux/Documentation/ABI/testing/ |
| H A D | configfs-usb-gadget-ffs | diff 43a029724d1c8219cc4e58e9fafbeedd1bc283fa Fri Jan 26 21:32:08 CET 2024 Peter Korsgaard <peter@korsgaard.com> usb: gadget: f_fs: expose ready state in configfs
When a USB gadget is configured through configfs with 1 or more f_fs
functions, then the logic setting up the gadget configuration has to wait
until the user space code (typically separate applications) responsible for
those functions have written their descriptors before the gadget can be
activated.
The f_fs instance already knows if this has been done, so expose it through
a "ready" attribute in configfs for easier synchronization.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Link: https://lore.kernel.org/r/20240126203208.2482573-1-peter@korsgaard.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
| /linux/Documentation/usb/ |
| H A D | gadget-testing.rst | diff 43a029724d1c8219cc4e58e9fafbeedd1bc283fa Fri Jan 26 21:32:08 CET 2024 Peter Korsgaard <peter@korsgaard.com> usb: gadget: f_fs: expose ready state in configfs
When a USB gadget is configured through configfs with 1 or more f_fs
functions, then the logic setting up the gadget configuration has to wait
until the user space code (typically separate applications) responsible for
those functions have written their descriptors before the gadget can be
activated.
The f_fs instance already knows if this has been done, so expose it through
a "ready" attribute in configfs for easier synchronization.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Link: https://lore.kernel.org/r/20240126203208.2482573-1-peter@korsgaard.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
| /linux/drivers/usb/gadget/function/ |
| H A D | f_fs.c | diff 43a029724d1c8219cc4e58e9fafbeedd1bc283fa Fri Jan 26 21:32:08 CET 2024 Peter Korsgaard <peter@korsgaard.com> usb: gadget: f_fs: expose ready state in configfs
When a USB gadget is configured through configfs with 1 or more f_fs
functions, then the logic setting up the gadget configuration has to wait
until the user space code (typically separate applications) responsible for
those functions have written their descriptors before the gadget can be
activated.
The f_fs instance already knows if this has been done, so expose it through
a "ready" attribute in configfs for easier synchronization.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Link: https://lore.kernel.org/r/20240126203208.2482573-1-peter@korsgaard.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|