>> This function is called whenever an ep file is released by user space (be it ep0 file or the other “regular” ep files). It is complementary to the ffs_data_opened function which in tandem track whether >> at least one epfile is open.
>> The way it works is that if user space closes all the ep files, FunctionFS will assume it's done with the function and reset to a clean state for a new user space program to access and make use.
>> So I think what's happening is that you are closing all the ep files in your user space program which causes the whole thing to be reset. To prevent it you just need to stick to at least one of the ep files. >> If you do so, you should no longer see the disconnects.
I agree with your point. But this doesn’t work when used this driver in Android platform. Kernel driver sends USB_DISCONNECT event even in BUS reset case and by that time USB disconnect is not expected from FunctionFs driver.
Moreover consider a case where SET_CONFIG(Config#0) commands comes from HOST. As per the composite driver, reset_config will be called.
In this case FunctionFs driver sends FUNCTIONFS_DISABLE event which makes all ep files release and leads to USB disconnect.
BTW, why it is expected to do USB disconnect from FunctionFs just to clean state for new user space program. Is it really requirement or FunctionFs driver? I mean to say what is expectation from functionfs_ready_callback and functionfs_closed_callback??
Thanks,
Roshan
��.n��������+%������w��{.n�����{���)�� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
