On 29 March 2016 at 16:45, Jun Li [off-list ref] wrote:

quoted

-----Original Message-----
From: linux-usb-owner@vger.kernel.org [mailto:linux-usb-
owner@vger.kernel.org] On Behalf Of Baolin Wang
Sent: Monday, March 28, 2016 2:52 PM
To: Peter Chen <redacted>
Cc: Felipe Balbi <balbi@kernel.org>; Greg KH <gregkh@linuxfoundation.org>;
Sebastian Reichel [off-list ref]; Dmitry Eremin-Solenikov
[off-list ref]; David Woodhouse [off-list ref]; Peter Chen
[off-list ref]; Alan Stern [off-list ref];
r.baldyga@samsung.com; Yoshihiro Shimoda
[off-list ref]; Lee Jones [off-list ref]; Mark
Brown [off-list ref]; Charles Keepax
[off-list ref]; patches@opensource.wolfsonmicro.com;
Linux PM list [off-list ref]; USB [off-list ref];
device-mainlining@lists.linuxfoundation.org; LKML <linux-
kernel@vger.kernel.org>
Subject: Re: [PATCH v8 0/4] Introduce usb charger framework to deal with
the usb gadget power negotation

On 25 March 2016 at 15:09, Peter Chen [off-list ref] wrote:

quoted

On Thu, Mar 24, 2016 at 08:35:53PM +0800, Baolin Wang wrote:

quoted

Currently the Linux kernel does not provide any standard integration
of this feature that integrates the USB subsystem with the system
power regulation provided by PMICs meaning that either vendors must
add this in their kernels or USB gadget devices based on Linux (such
as mobile phones) may not behave as they should. Thus provide a

standard framework for doing this in kernel.

quoted

quoted

Now introduce one user with wm831x_power to support and test the usb
charger, which is pending testing. Moreover there may be other
potential users will use it in future.

I am afraid I still not find the user (udc driver) for this framework,
I would like to see how udc driver block the enumeration until the
charger detection has finished, or am I missing something?

It is not for udc driver but for power users who want to negotiate with
USB subsystem.

Seems you don't want to guarantee charger type detection is done before
gadget connection(pullup DP), right?
I see you call usb_charger_detect_type() in each gadget usb state changes.

I am not sure I get your point correctly, please correct me if I
misunderstand you.
We need to check the charger type at every event comes from the usb
gadget state changes or the extcon device state changes, which means a
new charger plugin or pullup.

Li Jun

quoted

quoted

--
Best Regards,
Peter Chen

--
Baolin.wang
Best Regards
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html

-- 
Baolin.wang
Best Regards