Hi,
Baolin Wang writes:
> For supporting the usb charger, it adds the usb_charger_init() and
> usb_charger_exit() functions for usb charger initialization and exit.
>
> It will report to the usb charger when the gadget state is changed,
> then the usb char
Hi Felipe,
On 29 June 2016 at 20:06, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
For supporting the usb charger, it adds the usb_charger_init() and
usb_charger_exit() functions for usb charger initialization and exit.
It will report to the usb charger
Hi,
Baolin Wang writes:
>>> For supporting the usb charger, it adds the usb_charger_init() and
>>> usb_charger_exit() functions for usb charger initialization and exit.
>>>
>>> It will report to the usb charger when the gadget state is changed,
>>> then the usb charger can do
On 29 June 2016 at 16:34, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>> For supporting the usb charger, it adds the usb_charger_init() and
>> usb_charger_exit() functions for usb charger initialization and exit.
>>
>> It will report to the usb charger when the gadget stat
Hi,
Baolin Wang writes:
> For supporting the usb charger, it adds the usb_charger_init() and
> usb_charger_exit() functions for usb charger initialization and exit.
>
> It will report to the usb charger when the gadget state is changed,
> then the usb charger can do the power
Hi Felipe,
On 29 June 2016 at 16:20, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>>> Baolin Wang writes:
For supporting the usb charger, it adds the usb_charger_init() and
usb_charger_exit() functions for usb charger initialization and exit.
It will report to the usb
Hi,
Baolin Wang writes:
>> Baolin Wang writes:
>>> For supporting the usb charger, it adds the usb_charger_init() and
>>> usb_charger_exit() functions for usb charger initialization and exit.
>>>
>>> It will report to the usb charger when the gadget state is changed,
>>> then the usb charger ca
Hi,
On 21 June 2016 at 18:27, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>> For supporting the usb charger, it adds the usb_charger_init() and
>> usb_charger_exit() functions for usb charger initialization and exit.
>>
>> It will report to the usb charger when the gadget state is change
On 21 June 2016 at 20:53, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
> Can't you just tie a charger to a UDC and avoid the charger class
> completely?
Yeah, I also hope so. But we really want something to manage the
charger devices, do you have
Hi,
Baolin Wang writes:
>> Can't you just tie a charger to a UDC and avoid the charger class
>> completely?
>
> Yeah, I also hope so. But we really want something to manage the
> charger devices, do you have any good suggestion to avoid the 'class'
> but also can manage the charger devices?
man
Hi,
Felipe Balbi writes:
> Can't you just tie a charger to a UDC and avoid the charger class
> completely?
Yeah, I also hope so. But we really want something to manage the
charger devices, do you have any good suggestion to avoid the 'class'
bu
Hi,
Baolin Wang writes:
Can't you just tie a charger to a UDC and avoid the charger class
completely?
>>>
>>> Yeah, I also hope so. But we really want something to manage the
>>> charger devices, do you have any good suggestion to avoid the 'class'
>>> but also
On 21 June 2016 at 20:36, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>>> Baolin Wang writes:
> Baolin Wang writes:
>>> Can't you just tie a charger to a UDC and avoid the charger class
>>> completely?
>>
>> Yeah, I also hope so. But we really want something to manag
Hi,
Baolin Wang writes:
>> Baolin Wang writes:
Can't you just tie a charger to a UDC and avoid the charger class
completely?
>>>
>>> Yeah, I also hope so. But we really want something to manage the
>>> charger devices, do you have any good suggestion to avoid the 'class'
>>> but also
Hi,
Baolin Wang writes:
>> Baolin Wang writes:
Baolin Wang writes:
>> Can't you just tie a charger to a UDC and avoid the charger class
>> completely?
>
> Yeah, I also hope so. But we really want something to manage the
> charger devices, do you have any good suggestio
On 21 June 2016 at 20:27, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>>> Baolin Wang writes:
> Can't you just tie a charger to a UDC and avoid the charger class
> completely?
Yeah, I also hope so. But we really want something to manage the
charger devices, do you
On 21 June 2016 at 19:49, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>>> Can't you just tie a charger to a UDC and avoid the charger class
>>> completely?
>>
>> Yeah, I also hope so. But we really want something to manage the
>> charger devices, do you have any good suggestion to avoid t
On 21 June 2016 at 18:27, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>> For supporting the usb charger, it adds the usb_charger_init() and
>> usb_charger_exit() functions for usb charger initialization and exit.
>>
>> It will report to the usb charger when the gadget state is changed,
>>
Hi,
Baolin Wang writes:
> For supporting the usb charger, it adds the usb_charger_init() and
> usb_charger_exit() functions for usb charger initialization and exit.
>
> It will report to the usb charger when the gadget state is changed,
> then the usb charger can do the power things.
>
> Signed-
19 matches
Mail list logo
