Hi,
Alan Stern writes:
>> >> > The documentation doesn't state whether a gadget driver's
>> >> > ->disconnect() callback will be invoked when usb_gadget_disconnect()
>> >> > runs. Probably the UDC drivers' behavior has changed over the years.
>> >> >
>> >> > In any case, it's likely that vari
On Thu, 9 Aug 2018, Felipe Balbi wrote:
>
> Hi,
>
> Alan Stern writes:
> >> Alan Stern writes:
> >> > Felipe:
> >> >
> >> > The documentation doesn't state whether a gadget driver's
> >> > ->disconnect() callback will be invoked when usb_gadget_disconnect()
> >> > runs. Probably the UDC dri
Hi,
Alan Stern writes:
>> Alan Stern writes:
>> > Felipe:
>> >
>> > The documentation doesn't state whether a gadget driver's
>> > ->disconnect() callback will be invoked when usb_gadget_disconnect()
>> > runs. Probably the UDC drivers' behavior has changed over the years.
>> >
>> > In any c
On Wed, 8 Aug 2018, Felipe Balbi wrote:
>
> Hi,
>
> Alan Stern writes:
> > Felipe:
> >
> > The documentation doesn't state whether a gadget driver's
> > ->disconnect() callback will be invoked when usb_gadget_disconnect()
> > runs. Probably the UDC drivers' behavior has changed over the year
Hi,
Alan Stern writes:
> Felipe:
>
> The documentation doesn't state whether a gadget driver's
> ->disconnect() callback will be invoked when usb_gadget_disconnect()
> runs. Probably the UDC drivers' behavior has changed over the years.
>
> In any case, it's likely that various UDC drivers do
Felipe:
The documentation doesn't state whether a gadget driver's
->disconnect() callback will be invoked when usb_gadget_disconnect()
runs. Probably the UDC drivers' behavior has changed over the years.
In any case, it's likely that various UDC drivers do behave
differently. My current feeli
