Hi,
Greg KH writes:
> On Tue, Jan 17, 2017 at 10:07:40AM +0200, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Jim Lin writes:
>> > When gadget is disconnected, running sequence is like this.
>> > . android_work: sent uevent USB_STATE=DISCONNECTED
>>
>> I'm gonna have to ask you to try with actual main
On 2017年01月17日 16:07, Felipe Balbi wrote:
Hi,
Jim Lin writes:
When gadget is disconnected, running sequence is like this.
. android_work: sent uevent USB_STATE=DISCONNECTED
I'm gonna have to ask you to try with actual mainline where there are no
Android changes.
Let me rephrase and resend.
On Tue, Jan 17, 2017 at 10:07:40AM +0200, Felipe Balbi wrote:
>
> Hi,
>
> Jim Lin writes:
> > When gadget is disconnected, running sequence is like this.
> > . android_work: sent uevent USB_STATE=DISCONNECTED
>
> I'm gonna have to ask you to try with actual mainline where there are no
> Android
Hi,
Jim Lin writes:
> When gadget is disconnected, running sequence is like this.
> . android_work: sent uevent USB_STATE=DISCONNECTED
I'm gonna have to ask you to try with actual mainline where there are no
Android changes.
--
balbi
--
To unsubscribe from this list: send the line "unsubscrib
When gadget is disconnected, running sequence is like this.
. android_work: sent uevent USB_STATE=DISCONNECTED
. Call trace:
usb_string_copy+0xd0/0x128
gadget_config_name_configuration_store+0x4
gadget_config_name_attr_store+0x40/0x50
configfs_write_file+0x198/0x1f4
vfs_write+0x100/0x220