From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_PASS,UNPARSEABLE_RELAY,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 29C2BC43381 for ; Tue, 12 Mar 2019 02:18:58 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id ECCF1214D8 for ; Tue, 12 Mar 2019 02:18:57 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="kFktXz0E" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org ECCF1214D8 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=mediatek.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Date:To:From:Subject:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=8bIS77gt0e8rekX8VqA1qccjNZ86aVW4+MEnJxdbW+M=; b=kFktXz0EjHpQsX 0NopejO/zqRcESDhKbn4njlZH8vkxSPnPlEY2nd7ejq8BY5oS6uTahoSJZGayZ3uQX3K5wrwlBNZd 9V3GsGQ0CnCDpan2vVNhtiHK0A/vlGMy0yxreZGCswJD65NmbdpUC79AN22ktcxjR9toE0+LtWjZ7 kcy62l0nG4Rs1e6mqYU5G5CHoqd/muYma8quB9JVLMkYEZ0QiRnoDawhngMROrUtruux8aC+t3ymH ogfRuC95d6Yz4qZNGwUMd0YeA8y2vfgYtyL8mYp2EwOC8OPT8e/XNpc3gG3pmr7T8nyCyMjfUGvR3 dZKOXGieBxMVcPWTPnSg==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1h3X0C-0005Zh-Fi; Tue, 12 Mar 2019 02:18:48 +0000 Received: from mailgw01.mediatek.com ([216.200.240.184]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1h3X07-0005YW-J1; Tue, 12 Mar 2019 02:18:45 +0000 X-UUID: 9459a9c4c39f4f9dbf2f0b126687f771-20190311 X-UUID: 9459a9c4c39f4f9dbf2f0b126687f771-20190311 Received: from mtkcas68.mediatek.inc [(172.29.94.19)] by mailgw01.mediatek.com (envelope-from ) (musrelay.mediatek.com ESMTP with TLS) with ESMTP id 168851907; Mon, 11 Mar 2019 18:18:39 -0800 Received: from MTKMBS31N2.mediatek.inc (172.27.4.87) by MTKMBS62N2.mediatek.inc (172.29.193.42) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 11 Mar 2019 19:18:38 -0700 Received: from MTKCAS36.mediatek.inc (172.27.4.186) by MTKMBS31N2.mediatek.inc (172.27.4.87) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 12 Mar 2019 10:18:35 +0800 Received: from [10.17.3.153] (172.27.4.253) by MTKCAS36.mediatek.inc (172.27.4.170) with Microsoft SMTP Server id 15.0.1395.4 via Frontend Transport; Tue, 12 Mar 2019 10:18:33 +0800 Message-ID: <1552357113.10179.32.camel@mhfsdcap03> Subject: Re: [PATCH 1/5] dt-bindings: connector: add optional properties for Type-B From: Chunfeng Yun To: Hans de Goede , Jun Li Date: Tue, 12 Mar 2019 10:18:33 +0800 In-Reply-To: References: <1552025622-15582-1-git-send-email-chunfeng.yun@mediatek.com> <1552025622-15582-2-git-send-email-chunfeng.yun@mediatek.com> <693b11e7-fa9e-ab1f-561a-beb758b1872f@redhat.com> <1552282383.10179.21.camel@mhfsdcap03> <3684aa62-68ad-13ef-7c6e-2b57f7cd62b8@redhat.com> X-Mailer: Evolution 3.2.3-0ubuntu6 MIME-Version: 1.0 X-MTK: N X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190311_191843_633536_9DA8CB24 X-CRM114-Status: GOOD ( 28.40 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , devicetree@vger.kernel.org, Heikki Krogerus , Greg Kroah-Hartman , linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, Badhri Jagan Sridharan , Andy Shevchenko , Rob Herring , linux-mediatek@lists.infradead.org, Min Guo , Matthias Brugger , Adam Thomson , linux-arm-kernel@lists.infradead.org, Li Jun Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Jun, Please pay attention to Hans' comments for your patch On Mon, 2019-03-11 at 12:04 +0100, Hans de Goede wrote: > Hi, > > On 11-03-19 12:00, Hans de Goede wrote: > > Hi, > > > > On 11-03-19 09:06, Hans de Goede wrote: > >> Hi, > >> > >> On 11-03-19 06:33, Chunfeng Yun wrote: > >>> Hi, > >>> > >>> On Fri, 2019-03-08 at 13:07 +0100, Hans de Goede wrote: > >>>> Hi, > >>>> > >>>> On 08-03-19 07:13, Chunfeng Yun wrote: > >>>>> Add id-gpios, vbus-gpios, vbus-supply and pinctrl properties for > >>>>> usb-b-connector > >>>>> > >>>>> Signed-off-by: Chunfeng Yun > >>>>> --- > >>>>> .../devicetree/bindings/connector/usb-connector.txt | 10 ++++++++++ > >>>>> 1 file changed, 10 insertions(+) > >>>>> > >>>>> diff --git a/Documentation/devicetree/bindings/connector/usb-connector.txt b/Documentation/devicetree/bindings/connector/usb-connector.txt > >>>>> index a9a2f2fc44f2..7a07b0f4f973 100644 > >>>>> --- a/Documentation/devicetree/bindings/connector/usb-connector.txt > >>>>> +++ b/Documentation/devicetree/bindings/connector/usb-connector.txt > >>>>> @@ -17,6 +17,16 @@ Optional properties: > >>>>> - self-powered: Set this property if the usb device that has its own power > >>>>> source. > >>>>> +Optional properties for usb-b-connector: > >>>>> +- id-gpios: gpio for USB ID pin. > >>>> > >>>> What about boards where the ID pin is *not* connected to a GPIO, > >>>> but e.g. to a special pin on the PMIC which can also detect > >>>> an ACA adapter ? Currently this case is handled by extcon > >>>> drivers, but we have no way to set e.g. vbus-supply for the > >>>> connector. Maybe in this case the usb-connector node should > >>>> be a child of the PMIC node ? > >>> Yes, it would be, PMIC is in charger of detecting the status of ID pin > >> > >> Ok, then I think this should be documented too. > >> > >>>> And in many cases there also is a mux to switch the datalines > >>>> between the host and device(gadget) controllers, how should > >>>> that be described in this model? See the new usb-role-switch > >>>> code under drivers/usb/roles > >>>> > >>>> In some cases the mux is controlled through a gpio, so we > >>>> may want to add a "mux-gpios" here in which case we also > >>>> need to define what 0/1 means. > >>> I'm not sure, the mux seems not belong to this connector, > >>> and may need another driver to register usb-role-switch, > >>> similar to: > >>> > >>> [v2,2/2] usb: typec: add typec switch via GPIO control > >>> https://patchwork.kernel.org/patch/10834327/ > >> > >> Right the mux/role-switch will need a driver, but the "owner" > >> of the usb_connector, e.g. the PMIC or the owner of the > >> id GPIO pin needs to know which device is the role-switch so > >> that it can set the role correctly based on the id-pin. > >> > >> Your binding already contains Vbus info, allowing the owner > >> of the usb_connector to enable/disable Vbus based on the id-pin, > >> but the owner will also be responsible for setting the role-switch. > >> > >> Note we cannot simply assume there will be only one role-switch, > >> we really need some link from the usb_connector to the role-switch > >> (or if it is a GPIO driven role-switch simply a role-switch-gpios > >> member in the usb_connector). > > > > I see now in your "[PATCH v3 1/2] dt-bindings: usb: add documentation for > > typec switch via GPIO" that you plan to use a > > Documentation/devicetree/bindings/graph.txt style binding for this, > > adding a remote-endpoint to the orientation-switch (in that patch), or > > to the role-switch. > > > > But a Type-C port can have both an orientation-switch and a role-switch > > (and a mux if it supports e.g. DP-altmode), how is the driver driving > > the device which has the actual usb_c_connecter child-node to which > > the remote-endpoints for both the orientation- and the role-switch points > > supposed to figure out which is which ? > > > > Also it feels the wrong-way around to me to have the orientation-switch > > point to the usb_c_connector, to me it would make more sense to have > > the usb_c_connector point to a port on the orientation-switch. > > I just noticed you put an "orientation-switch" bool property in the device > which has the orientation-switch property, if we do something similar for > the role-switch then that should solve this. > > Regards, > > Hans _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel