Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp5172856ybf; Wed, 4 Mar 2020 18:53:44 -0800 (PST) X-Google-Smtp-Source: ADFU+vvadS3nHDG8Wx8A5iIQhEB3V+KKy5f1ed7edCeW74eTws16nuHy6IvsNthvUx23j7muw1DZ X-Received: by 2002:a9d:2184:: with SMTP id s4mr4660251otb.121.1583376824132; Wed, 04 Mar 2020 18:53:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583376824; cv=none; d=google.com; s=arc-20160816; b=0rvtlxZ9Zmwt32MvbmQd4xnzOABisxkWcL7y6TSZZq2aqj9duBYDvDn05131LKTaOe vDHo9uAcG8xcWfbmoHHfe4FEBJzSf/D1fluVelUmtCQdKOnmwFQe2JA/t7j5ZGjc7Jz3 XwzoMDLc0joGO2RxhFptIIyjCPUicMWSvBNW/cPrieJRHYJ46kcCQ8KjOpENJa4J7X4S HJtl+UzFK4t2+clXA8LcKUee4vUiSzKCu/B2VCdjqKmtQXe5pmxweeE4pVtEwqkAgX+2 uGKHNyxw/gDWYjWryUX9Do027V7lZw9Qh63j405epfjsZeYTJ36m02Q7YkS+LYZW0CAk +KOQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=jjwmb8rIi6EoAXJ38sPdxaJN/i5o0m2lXv7D1kz/D9Q=; b=NaN3gr3/qcdJ+a8H5zwbU7fVtO5Pjsd5zyns+QQRy3FGwu6fvzW0CyL6LX0Abk1riv 1GS/IttIk9M/dxFRbu4YzBHqcr0ryYSEWXPxQkAiiOYYkhNZJG02dd5/p2xjER7rLSc5 W+4oUSqFV9Y4jepeYHTaZ1kYsm687NmmUrclt96qARDsTHCgiJBCR1vXjXRZZrQvSmhw r+d3TbxvT2uXm7uDnjeyojfrpp+A/D25yebewjsYNeERsSdLt2pZGiVpRCigtdRnUKfI o1XWtmv1LHkEo3SBMCoXWJIPHwspebWgEKDuV9hlJOiqd4eJkDOfE0nje2hMNo3gMNwV SKGg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=WQ6nwTNL; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a59si2478911otb.8.2020.03.04.18.53.30; Wed, 04 Mar 2020 18:53:44 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=WQ6nwTNL; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725900AbgCECxE (ORCPT + 99 others); Wed, 4 Mar 2020 21:53:04 -0500 Received: from mail-pf1-f193.google.com ([209.85.210.193]:46140 "EHLO mail-pf1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725797AbgCECxE (ORCPT ); Wed, 4 Mar 2020 21:53:04 -0500 Received: by mail-pf1-f193.google.com with SMTP id o24so1997152pfp.13 for ; Wed, 04 Mar 2020 18:53:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=jjwmb8rIi6EoAXJ38sPdxaJN/i5o0m2lXv7D1kz/D9Q=; b=WQ6nwTNL4CiEYcVKckruhYa+ZzD2UUw3GVum/LAFBP/nPXXWvw1tPNVpaoh5uhB1Y2 IJlVOfCaSSvZQluAYB0nB6CULQV9D61ZaMp1ACRY40rGvfimeUILaxdxNe4aQyyt382f a6658pb28Sj2tZW1oFOtgUhnrDqEITlOyaXG4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=jjwmb8rIi6EoAXJ38sPdxaJN/i5o0m2lXv7D1kz/D9Q=; b=HkXam2gcA+bwBQJu+FOk8vgvzOy52LQfPk9EACjbHodyGBckEujS4kMPWkdBTxDRju 9jKNsCtQOFfVdHtFi0ana1o67yKG4kagv+josUHHET1rzbA9cj20NgzhqxkcbPFeedlD 7QvBKTofy+Xt4ezCLblBliqV60767aQ9YoscxBYl/a/h61yzG0tPTJSW/eSqHIQIj2M7 JbREEqy+gXW3fK70K/UVqCmRibkNCHymrIImblwc0xr1olprUrgcrpRbKFjiWbLqpINM WiX0vmFdqHL+LcrL5akRvK0XSrmzMH6hq8baWB8M027ONCvu7rCJ7X+37/IpPa7BrMf5 kXag== X-Gm-Message-State: ANhLgQ28UTISRl7kiW4/XBBO3zKewaGpBYmu4P9dXGXV2hrw43vstcjR TTumSudbsukXYcojoVdmKGMSAw== X-Received: by 2002:a63:514f:: with SMTP id r15mr5130669pgl.432.1583376781520; Wed, 04 Mar 2020 18:53:01 -0800 (PST) Received: from google.com ([2620:15c:202:201:476b:691:abc3:38db]) by smtp.gmail.com with ESMTPSA id m12sm4035349pjf.25.2020.03.04.18.53.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 04 Mar 2020 18:53:00 -0800 (PST) Date: Wed, 4 Mar 2020 18:52:59 -0800 From: Prashant Malani To: Rob Herring Cc: devicetree@vger.kernel.org, Benson Leung , Stephen Boyd , Heikki Krogerus , Enric Balletbo i Serra , Bryan O'Donoghue , Chunfeng Yun , Greg Kroah-Hartman , "moderated list:ARM/Mediatek SoC support" , open list , "moderated list:ARM/Mediatek SoC support" , "open list:USB SUBSYSTEM" , Mark Rutland , Matthias Brugger , Miquel Raynal Subject: Re: [PATCH] dt-bindings: Convert usb-connector to YAML format. Message-ID: <20200305025259.GA142502@google.com> References: <20200304174942.124070-1-pmalani@chromium.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Rob, Thanks a lot for reviewing the patch. On Wed, Mar 04, 2020 at 01:55:22PM -0600, Rob Herring wrote: > On Wed, Mar 4, 2020 at 11:50 AM Prashant Malani wrote: > > > > Convert the usb-connector.txt bindings file to YAML format. This allows > > it to be used in dt_bindings_check verification. This patch was > > born out of a patch series for the addition of a Type C connector > > class port driver[1]. > > > > An attempt has been made to maintain the same documentation text and > > example structure as was in the .txt file, but wherever needed > > modifications have been made to satisfy dt_bindings_check. > > > > Also, update all references to usb-connector.txt to now use > > usb-connector.yaml. > > > > [1]: https://lkml.org/lkml/2020/2/19/1232 > > > > Signed-off-by: Prashant Malani > > --- > > .../connector/samsung,usb-connector-11pin.txt | 2 +- > > .../bindings/connector/usb-connector.txt | 135 ------------ > > .../bindings/connector/usb-connector.yaml | 193 ++++++++++++++++++ > > .../devicetree/bindings/usb/fcs,fusb302.txt | 2 +- > > .../devicetree/bindings/usb/generic.txt | 2 +- > > .../devicetree/bindings/usb/mediatek,mtu3.txt | 2 +- > > .../devicetree/bindings/usb/mediatek,musb.txt | 2 +- > > .../bindings/usb/richtek,rt1711h.txt | 2 +- > > .../devicetree/bindings/usb/ti,hd3ss3220.txt | 2 +- > > .../devicetree/bindings/usb/typec-tcpci.txt | 2 +- > > .../devicetree/bindings/usb/usb-conn-gpio.txt | 4 +- > > 11 files changed, 203 insertions(+), 145 deletions(-) > > delete mode 100644 Documentation/devicetree/bindings/connector/usb-connector.txt > > create mode 100644 Documentation/devicetree/bindings/connector/usb-connector.yaml > > > > diff --git a/Documentation/devicetree/bindings/connector/samsung,usb-connector-11pin.txt b/Documentation/devicetree/bindings/connector/samsung,usb-connector-11pin.txt > > index 22256e295a7a1..3dd8961154abf 100644 > > --- a/Documentation/devicetree/bindings/connector/samsung,usb-connector-11pin.txt > > +++ b/Documentation/devicetree/bindings/connector/samsung,usb-connector-11pin.txt > > @@ -19,7 +19,7 @@ Required nodes: > > 0: High Speed (HS), > > 3: Mobile High-Definition Link (MHL), specific to 11-pin Samsung micro-USB. > > > > -[1]: bindings/connector/usb-connector.txt > > +[1]: bindings/connector/usb-connector.yaml > > > > Example > > ------- > > diff --git a/Documentation/devicetree/bindings/connector/usb-connector.txt b/Documentation/devicetree/bindings/connector/usb-connector.txt > > deleted file mode 100644 > > index 88578ac1a8a76..0000000000000 > > --- a/Documentation/devicetree/bindings/connector/usb-connector.txt > > +++ /dev/null > > @@ -1,135 +0,0 @@ > > -USB Connector > > -============= > > - > > -A USB connector node represents a physical USB connector. It should be > > -a child of a USB interface controller. > > - > > -Required properties: > > -- compatible: describes type of the connector, must be one of: > > - "usb-a-connector", > > - "usb-b-connector", > > - "usb-c-connector". > > - > > -Optional properties: > > -- label: symbolic name for the connector, > > -- type: size of the connector, should be specified in case of USB-A, USB-B > > - non-fullsize connectors: "mini", "micro". > > -- self-powered: Set this property if the usb device that has its own power > > - source. > > - > > -Optional properties for usb-b-connector: > > -- id-gpios: an input gpio for USB ID pin. > > -- vbus-gpios: an input gpio for USB VBUS pin, used to detect presence of > > - VBUS 5V. > > - see gpio/gpio.txt. > > -- vbus-supply: a phandle to the regulator for USB VBUS if needed when host > > - mode or dual role mode is supported. > > - Particularly, if use an output GPIO to control a VBUS regulator, should > > - model it as a regulator. > > - see regulator/fixed-regulator.yaml > > -- pinctrl-names : a pinctrl state named "default" is optional > > -- pinctrl-0 : pin control group > > - see pinctrl/pinctrl-bindings.txt > > - > > -Optional properties for usb-c-connector: > > -- power-role: should be one of "source", "sink" or "dual"(DRP) if typec > > - connector has power support. > > -- try-power-role: preferred power role if "dual"(DRP) can support Try.SNK > > - or Try.SRC, should be "sink" for Try.SNK or "source" for Try.SRC. > > -- data-role: should be one of "host", "device", "dual"(DRD) if typec > > - connector supports USB data. > > - > > -Required properties for usb-c-connector with power delivery support: > > -- source-pdos: An array of u32 with each entry providing supported power > > - source data object(PDO), the detailed bit definitions of PDO can be found > > - in "Universal Serial Bus Power Delivery Specification" chapter 6.4.1.2 > > - Source_Capabilities Message, the order of each entry(PDO) should follow > > - the PD spec chapter 6.4.1. Required for power source and power dual role. > > - User can specify the source PDO array via PDO_FIXED/BATT/VAR/PPS_APDO() > > - defined in dt-bindings/usb/pd.h. > > -- sink-pdos: An array of u32 with each entry providing supported power > > - sink data object(PDO), the detailed bit definitions of PDO can be found > > - in "Universal Serial Bus Power Delivery Specification" chapter 6.4.1.3 > > - Sink Capabilities Message, the order of each entry(PDO) should follow > > - the PD spec chapter 6.4.1. Required for power sink and power dual role. > > - User can specify the sink PDO array via PDO_FIXED/BATT/VAR/PPS_APDO() defined > > - in dt-bindings/usb/pd.h. > > -- op-sink-microwatt: Sink required operating power in microwatt, if source > > - can't offer the power, Capability Mismatch is set. Required for power > > - sink and power dual role. > > - > > -Required nodes: > > -- any data bus to the connector should be modeled using the OF graph bindings > > - specified in bindings/graph.txt, unless the bus is between parent node and > > - the connector. Since single connector can have multiple data buses every bus > > - has assigned OF graph port number as follows: > > - 0: High Speed (HS), present in all connectors, > > - 1: Super Speed (SS), present in SS capable connectors, > > - 2: Sideband use (SBU), present in USB-C. > > - > > -Examples > > --------- > > - > > -1. Micro-USB connector with HS lines routed via controller (MUIC): > > - > > -muic-max77843@66 { > > - ... > > - usb_con: connector { > > - compatible = "usb-b-connector"; > > - label = "micro-USB"; > > - type = "micro"; > > - }; > > -}; > > - > > -2. USB-C connector attached to CC controller (s2mm005), HS lines routed > > -to companion PMIC (max77865), SS lines to USB3 PHY and SBU to DisplayPort. > > -DisplayPort video lines are routed to the connector via SS mux in USB3 PHY. > > - > > -ccic: s2mm005@33 { > > - ... > > - usb_con: connector { > > - compatible = "usb-c-connector"; > > - label = "USB-C"; > > - > > - ports { > > - #address-cells = <1>; > > - #size-cells = <0>; > > - > > - port@0 { > > - reg = <0>; > > - usb_con_hs: endpoint { > > - remote-endpoint = <&max77865_usbc_hs>; > > - }; > > - }; > > - port@1 { > > - reg = <1>; > > - usb_con_ss: endpoint { > > - remote-endpoint = <&usbdrd_phy_ss>; > > - }; > > - }; > > - port@2 { > > - reg = <2>; > > - usb_con_sbu: endpoint { > > - remote-endpoint = <&dp_aux>; > > - }; > > - }; > > - }; > > - }; > > -}; > > - > > -3. USB-C connector attached to a typec port controller(ptn5110), which has > > -power delivery support and enables drp. > > - > > -typec: ptn5110@50 { > > - ... > > - usb_con: connector { > > - compatible = "usb-c-connector"; > > - label = "USB-C"; > > - power-role = "dual"; > > - try-power-role = "sink"; > > - source-pdos = ; > > - sink-pdos = > - PDO_VAR(5000, 12000, 2000)>; > > - op-sink-microwatt = <10000000>; > > - }; > > -}; > > diff --git a/Documentation/devicetree/bindings/connector/usb-connector.yaml b/Documentation/devicetree/bindings/connector/usb-connector.yaml > > new file mode 100644 > > index 0000000000000..f0fac9bd63364 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/connector/usb-connector.yaml > > @@ -0,0 +1,193 @@ > > +# SPDX-License-Identifier: GPL-2.0-only > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/connector/usb-connector.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: USB Connector > > + > > +maintainers: > > + - linux-usb@vger.kernel.org > > + > > +description: > > + A USB connector node represents a physical USB connector. It should be a child > > + of a USB interface controller. > > + > > +properties: > > + compatible: > > + enum: > > + - usb-a-connector > > + - usb-b-connector > > + - usb-c-connector > > + > > + label: > > + description: Symbolic name for the connector. > > + > > + type: > > + description: Size of the connector, should be specified in case of USB-A, > > + USB-B non-fullsize connectors. > > + enum: > > + - mini > > + - micro > > Needs a type reference. > Done. > > + > > + self-powered: > > + description: Set this property if the USB device has its own power source. > > type: boolean > Done. > > + > > + # The following are optional properties for "usb-b-connector". > > + id-gpios: > > + description: An input gpio for USB ID pin. > > maxItems: 1 > Done. > > + > > + vbus-gpios: > > + description: An input gpio for USB VBus pin, used to detect presence of > > + VBUS 5V. See gpio/gpio.txt. > > maxItems: 1 > Done. > > + > > + vbus-supply: > > + description: A phandle to the regulator for USB VBUS if needed when host > > + mode or dual role mode is supported. > > + Particularly, if use an output GPIO to control a VBUS regulator, should > > + model it as a regulator. See regulator/fixed-regulator.yaml > > + > > + pinctrl-names: > > + description: A pinctrl state named "default" is optional. > > + > > + pinctrl-0: > > + description: Pin control group. See pinctrl/pinctrl-bindings.txt > > pinctrl properties get added automatically, so you can drop these 2. > Done. > > + > > + # The following are optional properties for "usb-c-connector". > > + power-role: > > + description: Determines the power role that the Type C connector will > > + support. > > + contains: > > + source: > > + description: Connector is a power source. > > + sink: > > + description: Connector is a power sink. > > + dual: > > + description: Connector is a Dual Role Port (DRP). > > Not valid json-schema. Should be like this: > > power-role: > allOf: > - $ref: /schemas/types.yaml#definitions/string > enum: > - source > - sink > - dual > Done. > > + > > + try-power-role: > > + description: Preferred power role. > > + contains: > > + sink: > > + description: Try.SNK is preferred power role. > > + source: > > + description: Try.SRC is preferred power role. > > + dual: > > + description: DRP can support Try.SNK or Try.SRC. > > Same here. > Done. > > + > > + data-role: > > + description: Data role if Type C connector supports USB data. > > + contains: > > + host: > > + description: Connector is a host. > > + device: > > + description: Connector is a device. > > + dual: > > + description: Connector is Dual Role Device (DRD). > > Similar here. > Done. > > + > > + # The following are optional properties for "usb-c-connector" with power > > + # delivery support. > > + source-pdos: > > + description: An array of u32 with each entry providing supported power > > + source data object(PDO), the detailed bit definitions of PDO can be found > > + in "Universal Serial Bus Power Delivery Specification" chapter 6.4.1.2 > > + Source_Capabilities Message, the order of each entry(PDO) should follow > > + the PD spec chapter 6.4.1. Required for power source and power dual role. > > + User can specify the source PDO array via PDO_FIXED/BATT/VAR/PPS_APDO() > > + defined in dt-bindings/usb/pd.h. > > + minItems: 1 > > + maxItems: 7 > > + allOf: > > + - $ref: /schemas/types.yaml#/definitions/uint32-array > > + > > + > > + sink-pdos: > > + description: An array of u32 with each entry providing supported power sink > > + data object(PDO), the detailed bit definitions of PDO can be found in > > + "Universal Serial Bus Power Delivery Specification" chapter 6.4.1.3 > > + Sink Capabilities Message, the order of each entry(PDO) should follow the > > + PD spec chapter 6.4.1. Required for power sink and power dual role. User > > + can specify the sink PDO array via PDO_FIXED/BATT/VAR/PPS_APDO() defined > > + in dt-bindings/usb/pd.h. > > + minItems: 1 > > + maxItems: 7 > > + allOf: > > + - $ref: /schemas/types.yaml#/definitions/uint32-array > > + > > + op-sink-microwatt: > > + description: Sink required operating power in microwatt, if source can't > > + offer the power, Capability Mismatch is set. Required for power sink and > > + power dual role. > > + > > +# Any data bus to the connector should be modeled using the OF graph bindings > > +# specified in bindings/graph.txt, unless the bus is between parent node and > > +# the connector. Since single connector can have multiple data buses every bus > > +# has assigned OF graph port number as follows: > > +# 0: High Speed (HS), present in all connectors, > > +# 1: Super Speed (SS), present in SS capable connectors, > > +# 2: Sideband use (SBU), present in USB-C. > > You need something like this: > > ports: > type: object > properties: > port@0: > type: object > description: High Speed (HS), present in all connectors > ... > required: > - port@0 Done. > Best regards, > > +required: > > + - compatible > > + > > +examples: > > + # Micro-USB connector with HS lines routed via controller (MUIC). > > + - |+ > > + muic-max77843@66 { > > + usb_con1: connector { > > + compatible = "usb-b-connector"; > > + label = "micro-USB"; > > + type = "micro"; > > + }; > > + }; > > + > > + # USB-C connector attached to CC controller (s2mm005), HS lines routed > > + # to companion PMIC (max77865), SS lines to USB3 PHY and SBU to DisplayPort. > > + # DisplayPort video lines are routed to the connector via SS mux in USB3 PHY. > > + - |+ > > + ccic: s2mm005@33 { > > + usb_con2: connector { > > + compatible = "usb-c-connector"; > > + label = "USB-C"; > > + > > + ports { > > + #address-cells = <1>; > > + #size-cells = <0>; > > + > > + port@0 { > > + reg = <0>; > > + usb_con_hs: endpoint { > > + remote-endpoint = <&max77865_usbc_hs>; > > + }; > > + }; > > + port@1 { > > + reg = <1>; > > + usb_con_ss: endpoint { > > + remote-endpoint = <&usbdrd_phy_ss>; > > + }; > > + }; > > + port@2 { > > + reg = <2>; > > + usb_con_sbu: endpoint { > > + remote-endpoint = <&dp_aux>; > > + }; > > + }; > > + }; > > + }; > > + }; > > + > > + # USB-C connector attached to a typec port controller(ptn5110), which has > > + # power delivery support and enables drp. > > + - |+ > > + #include > > + typec: ptn5110@50 { > > + usb_con3: connector { > > + compatible = "usb-c-connector"; > > + label = "USB-C"; > > + power-role = "dual"; > > + try-power-role = "sink"; > > + source-pdos = ; > > + sink-pdos = > + PDO_VAR(5000, 12000, 2000)>; > > + op-sink-microwatt = <10000000>; > > + }; > > + }; > > diff --git a/Documentation/devicetree/bindings/usb/fcs,fusb302.txt b/Documentation/devicetree/bindings/usb/fcs,fusb302.txt > > index ba2e32d500c02..60e4654297af7 100644 > > --- a/Documentation/devicetree/bindings/usb/fcs,fusb302.txt > > +++ b/Documentation/devicetree/bindings/usb/fcs,fusb302.txt > > @@ -9,7 +9,7 @@ Required sub-node: > > - connector : The "usb-c-connector" attached to the FUSB302 IC. The bindings > > of the connector node are specified in: > > > > - Documentation/devicetree/bindings/connector/usb-connector.txt > > + Documentation/devicetree/bindings/connector/usb-connector.yaml > > > > > > Example: > > diff --git a/Documentation/devicetree/bindings/usb/generic.txt b/Documentation/devicetree/bindings/usb/generic.txt > > index e6790d2a4da9b..474e74c06522d 100644 > > --- a/Documentation/devicetree/bindings/usb/generic.txt > > +++ b/Documentation/devicetree/bindings/usb/generic.txt > > @@ -34,7 +34,7 @@ Optional properties: > > - usb-role-switch: boolean, indicates that the device is capable of assigning > > the USB data role (USB host or USB device) for a given > > USB connector, such as Type-C, Type-B(micro). > > - see connector/usb-connector.txt. > > + see connector/usb-connector.yaml. > > > > This is an attribute to a USB controller such as: > > > > diff --git a/Documentation/devicetree/bindings/usb/mediatek,mtu3.txt b/Documentation/devicetree/bindings/usb/mediatek,mtu3.txt > > index e0ae6096f7ac8..a82ca438aec1f 100644 > > --- a/Documentation/devicetree/bindings/usb/mediatek,mtu3.txt > > +++ b/Documentation/devicetree/bindings/usb/mediatek,mtu3.txt > > @@ -34,7 +34,7 @@ Optional properties: > > dual-role mode. > > it's considered valid for compatibility reasons, not allowed for > > new bindings, and put into a usb-connector node. > > - see connector/usb-connector.txt. > > + see connector/usb-connector.yaml. > > - pinctrl-names : a pinctrl state named "default" is optional, and need be > > defined if auto drd switch is enabled, that means the property dr_mode > > is set as "otg", and meanwhile the property "mediatek,enable-manual-drd" > > diff --git a/Documentation/devicetree/bindings/usb/mediatek,musb.txt b/Documentation/devicetree/bindings/usb/mediatek,musb.txt > > index 2b8a87c90d9ea..5eedb02965622 100644 > > --- a/Documentation/devicetree/bindings/usb/mediatek,musb.txt > > +++ b/Documentation/devicetree/bindings/usb/mediatek,musb.txt > > @@ -23,7 +23,7 @@ Optional properties: > > MTCMOS > > > > Required child nodes: > > - usb connector node as defined in bindings/connector/usb-connector.txt > > + usb connector node as defined in bindings/connector/usb-connector.yaml > > Optional properties: > > - id-gpios : input GPIO for USB ID pin. > > - vbus-gpios : input GPIO for USB VBUS pin. > > diff --git a/Documentation/devicetree/bindings/usb/richtek,rt1711h.txt b/Documentation/devicetree/bindings/usb/richtek,rt1711h.txt > > index e3fc57e605ed6..6f8115db2ea9b 100644 > > --- a/Documentation/devicetree/bindings/usb/richtek,rt1711h.txt > > +++ b/Documentation/devicetree/bindings/usb/richtek,rt1711h.txt > > @@ -9,7 +9,7 @@ Required properties: > > Required sub-node: > > - connector: The "usb-c-connector" attached to the tcpci chip, the bindings > > of connector node are specified in > > - Documentation/devicetree/bindings/connector/usb-connector.txt > > + Documentation/devicetree/bindings/connector/usb-connector.yaml > > > > Example : > > rt1711h@4e { > > diff --git a/Documentation/devicetree/bindings/usb/ti,hd3ss3220.txt b/Documentation/devicetree/bindings/usb/ti,hd3ss3220.txt > > index 25780e945b154..2bd21b22ce95b 100644 > > --- a/Documentation/devicetree/bindings/usb/ti,hd3ss3220.txt > > +++ b/Documentation/devicetree/bindings/usb/ti,hd3ss3220.txt > > @@ -9,7 +9,7 @@ Required sub-node: > > - connector: The "usb-c-connector" attached to the hd3ss3220 chip. The > > bindings of the connector node are specified in: > > > > - Documentation/devicetree/bindings/connector/usb-connector.txt > > + Documentation/devicetree/bindings/connector/usb-connector.yaml > > > > Example: > > hd3ss3220@47 { > > diff --git a/Documentation/devicetree/bindings/usb/typec-tcpci.txt b/Documentation/devicetree/bindings/usb/typec-tcpci.txt > > index 0dd1469e73180..2082522b1c326 100644 > > --- a/Documentation/devicetree/bindings/usb/typec-tcpci.txt > > +++ b/Documentation/devicetree/bindings/usb/typec-tcpci.txt > > @@ -13,7 +13,7 @@ Required properties: > > Required sub-node: > > - connector: The "usb-c-connector" attached to the tcpci chip, the bindings > > of connector node are specified in > > - Documentation/devicetree/bindings/connector/usb-connector.txt > > + Documentation/devicetree/bindings/connector/usb-connector.yaml > > > > Example: > > > > diff --git a/Documentation/devicetree/bindings/usb/usb-conn-gpio.txt b/Documentation/devicetree/bindings/usb/usb-conn-gpio.txt > > index 3d05ae56cb0dc..ec80641208a53 100644 > > --- a/Documentation/devicetree/bindings/usb/usb-conn-gpio.txt > > +++ b/Documentation/devicetree/bindings/usb/usb-conn-gpio.txt > > @@ -8,11 +8,11 @@ Required properties: > > - compatible : should include "gpio-usb-b-connector" and "usb-b-connector". > > - id-gpios, vbus-gpios : input gpios, either one of them must be present, > > and both can be present as well. > > - see connector/usb-connector.txt > > + see connector/usb-connector.yaml > > > > Optional properties: > > - vbus-supply : can be present if needed when supports dual role mode. > > - see connector/usb-connector.txt > > + see connector/usb-connector.yaml > > > > - Sub-nodes: > > - port : can be present. > > -- > > 2.25.0.265.gbab2e86ba0-goog > >