Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752340AbcC3L0l (ORCPT ); Wed, 30 Mar 2016 07:26:41 -0400 Received: from mga01.intel.com ([192.55.52.88]:20999 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751522AbcC3L0j (ORCPT ); Wed, 30 Mar 2016 07:26:39 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,415,1455004800"; d="asc'?scan'208";a="944405773" From: Felipe Balbi To: Jun Li , Baolin Wang Cc: Peter Chen , Greg KH , Sebastian Reichel , Dmitry Eremin-Solenikov , David Woodhouse , Peter Chen , Alan Stern , "r.baldyga\@samsung.com" , Yoshihiro Shimoda , Lee Jones , Mark Brown , Charles Keepax , "patches\@opensource.wolfsonmicro.com" , Linux PM list , USB , "device-mainlining\@lists.linuxfoundation.org" , LKML Subject: RE: [PATCH v8 0/4] Introduce usb charger framework to deal with the usb gadget power negotation In-Reply-To: References: <20160325070937.GA22398@peterchendt> User-Agent: Notmuch/0.21+96~g9bbc54b (http://notmuchmail.org) Emacs/25.0.90.3 (x86_64-pc-linux-gnu) Date: Wed, 30 Mar 2016 14:24:41 +0300 Message-ID: <878u10jjie.fsf@intel.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4269 Lines: 103 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, Jun Li writes: >> -----Original Message----- >> From: Baolin Wang [mailto:baolin.wang@linaro.org] >> Sent: Wednesday, March 30, 2016 5:31 PM >> To: Jun Li >> Cc: Peter Chen ; Felipe Balbi ; >> Greg KH ; Sebastian Reichel ; >> Dmitry Eremin-Solenikov ; David Woodhouse >> ; Peter Chen ; Alan Stern >> ; r.baldyga@samsung.com; Yoshihiro Shimoda >> ; Lee Jones ; Ma= rk >> Brown ; Charles Keepax >> ; patches@opensource.wolfsonmicro.c= om; >> Linux PM list ; USB ; >> device-mainlining@lists.linuxfoundation.org; LKML > kernel@vger.kernel.org> >> Subject: Re: [PATCH v8 0/4] Introduce usb charger framework to deal with >> the usb gadget power negotation >>=20 >> On 30 March 2016 at 16:07, Jun Li wrote: >> > Hi >>=20 >> >> On 30 March 2016 at 10:54, Jun Li wrote: >> >> >> >> 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. >> >> >> >> >> > >> >> > According to usb charger spec, my understanding is you can't do >> >> > real charger detection procedure *after* gadget _connection_(pullup >> >> > DP), also I don't >> >> >> >> Why can not? Charger detection is usually from PMIC. >> > >> > Charger detection process will impact DP/DM line state, see usb >> > charger spec v1.2 for detail detection process, section 4.6.3 says: >> > >> > "A PD is allowed to *disconnect* and repeat the charger detection >> > process multiple times while attached. The PD is required to wait for >> > a time of at least TCP_VDM_EN max between disconnecting and restarting >> > the charger detection process." >> > >> > As Peter mentioned, the charger detection should happen between VBUS >> > detection and gadget pull up DP for first plug in case. So when&after >> > gadget connect (pullup DP), you should already know the charger type. >>=20 >> Make sense. In our company's solution, charger detection can be done by >> hardware from PMIC at first, then it will not affect the DP/DM line when >> gadget starts to enumeration.=20 > > I see, charger type detection is done automatically by PMIC when VBUS > is detected in your case, you just assume the process is complete assuming this finishes before gadget starts is a bad idea. It would've been much more robust to delay usb_gadget_connect() until we KNOW charger detection has completed. =2D-=20 balbi --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJW+7d6AAoJEIaOsuA1yqRE4YwQAKNouReSBJUPTj9JgT/txBp/ nOrxdmFupekc9dkDa9jc0gj4a/0zahM/5U6r8UQtRDJFzpcgP13Vdnjk0/Ha9vre 5nTotkVTmu6nSJlTDDgbxFwOApxPipNxAoQ1NZF5oAJ2LSY5/hn8T5CnY/YxfQc3 bQj8CdEXlFNekn0nmw9X+Wm+8Igz0tEbDFNP+/rGshZVB+So4EvOpzgHOC9kUj6H RYu8YWU56X4fiRdP1vPKiYGEgRrG4iHwRZgMD2iGHNkq/XDmgYUtldMKkPbDkfPZ Y/COwGykTvlag2NM1li94+Y+iwsWid7OMEeXy1kQocVfLVUGGUT6GJO4OYc3p7nd saAOEaCG/mtr4fwS9X+zdtdOZVLmeRo8c7EvUTHw8bR9FZEDZ3xJW3BGSnRPTBkT NNr0epBU2bfn2rNG10JVl8SMmgP5iZAaBvOTX1vDWHpK0vHjU40qyTpPg+zB2oTV 6siWFOJq/SXADJfeCZWdzVj7tyoOYN/RWk6EtlFXx4X/6UG+EKZp4BYxEUIpS6wo RvaposzuAASTwhIdnQsSuiyV1qUvvQ4rS4gUrUe7yltroP3/zMdKUes77/ff6Add 2FzjE0d4spUKR92RvG0A4r6KEqIiG+sFEWhQzaNwGbfJ9TNtOuYw8sVcCKBeyj+Q j5Uxa30BpjBWmL3AQGQu =ArvR -----END PGP SIGNATURE----- --=-=-=--