Hello, This is fourth version of patches containing improvements for FunctionFS which allows to use it with asynchronous I/O interface. It also adds poll function for ep0, to make it usable without creating additional thread, needed by blocking I/O. >From last version I have fixed few nit's, and made some modifications improving request completion handling. This patchset contains two patches with fixes, created by Michal Nazarewicz. More details in commit messages. Best regards Robert Baldyga Samsung R&D Institute Poland Changelog: v4: - move completion code into worker to make cancel function asynchronous v3: http://www.spinics.net/lists/linux-usb/msg101324.html - clean up code - add allocation result checks - fix FFS_SETUP_CANCELLED state handling in ffs_ep0_poll() function - aio_complete() function is not called if request was cancelled v2: http://www.spinics.net/lists/linux-usb/msg101104.html - fix style problems - add error handling in ffs_user_copy_worker() - fix paremeters of aio_complete() in ffs_epfile_async_io_complete() - in ffs_epfile_io() do copy_from_user() calls with spinlock unlocked - in ffs_ep0_poll() remove "default" from switch-case block and add case for each enum value - fix returned value in __ffs_ep0_queue_wait() funcion v1: http://www.spinics.net/lists/linux-usb/msg100969.html - initial proposal Michal Nazarewicz (2): usb: gadget: functionfs: fix typo in the enum variable usb: gadget: functionfs: replace FFS_SETUP_STATUS with an inline function Michal Nazarewicz (2): usb: gadget: functionfs: fix typo in the enum variable usb: gadget: functionfs: replace FFS_SETUP_STATUS with an inline function Robert Baldyga (3): usb: gadget: f_fs: fix setup request handling usb: gadget: f_fs: add poll for endpoint 0 usb: gadget: f_fs: add aio support drivers/usb/gadget/f_fs.c | 337 ++++++++++++++++++++++++++++++++++++++++----- drivers/usb/gadget/u_fs.h | 18 ++- 2 files changed, 308 insertions(+), 47 deletions(-) -- 1.7.9.5 -- 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
