Hi Michal,
On 8 December 2016 at 23:18, Michal Nazarewicz wrote:
> On Thu, Dec 08 2016, Baolin Wang wrote:
>> When system try to close /dev/usb-ffs/adb/ep0 on one core, at the same
>> time another core try to attach new UDC, which will cause deadlock as
>> below scenario. Thus
Hi Michal,
On 8 December 2016 at 23:18, Michal Nazarewicz wrote:
> On Thu, Dec 08 2016, Baolin Wang wrote:
>> When system try to close /dev/usb-ffs/adb/ep0 on one core, at the same
>> time another core try to attach new UDC, which will cause deadlock as
>> below scenario. Thus we should release
On Thu, Dec 08 2016, Baolin Wang wrote:
> When system try to close /dev/usb-ffs/adb/ep0 on one core, at the same
> time another core try to attach new UDC, which will cause deadlock as
> below scenario. Thus we should release ffs lock before issuing
> unregister_gadget_item().
>
> [ 52.642225]
On Thu, Dec 08 2016, Baolin Wang wrote:
> When system try to close /dev/usb-ffs/adb/ep0 on one core, at the same
> time another core try to attach new UDC, which will cause deadlock as
> below scenario. Thus we should release ffs lock before issuing
> unregister_gadget_item().
>
> [ 52.642225]
When system try to close /dev/usb-ffs/adb/ep0 on one core, at the same
time another core try to attach new UDC, which will cause deadlock as
below scenario. Thus we should release ffs lock before issuing
unregister_gadget_item().
[ 52.642225] c1
When system try to close /dev/usb-ffs/adb/ep0 on one core, at the same
time another core try to attach new UDC, which will cause deadlock as
below scenario. Thus we should release ffs lock before issuing
unregister_gadget_item().
[ 52.642225] c1
6 matches
Mail list logo