Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp1098544imj; Thu, 14 Feb 2019 01:00:26 -0800 (PST) X-Google-Smtp-Source: AHgI3IbWHgbtDabVSL3O8OVc4qSQsOYFOY+Onkoq9sZ28yTvrHs6wZvOlRVtHOCEqiFbANq7MpVS X-Received: by 2002:a17:902:684:: with SMTP id 4mr2981443plh.3.1550134826093; Thu, 14 Feb 2019 01:00:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550134826; cv=none; d=google.com; s=arc-20160816; b=lp7hFWBHXuhj7sPYeIulUbjnzuLzo7cSPJ8BCodbGx4O5FZ/pmK8n2mzljH9jRvSPZ bw0+RPg7V0xxxa2RBnTfCCFeeFG/OnIQdmGP96wusiJ9UdLEiOgUVWd6Z+zdXElF+4Oz ZvpyQ38BHCqPmLUbJO9M5DfVfLRaJ6DoiH7YdpXXOLFNlAnXeyMq+E9pNmPJ6mdVy0U6 BKbZHLDj9pxB/rbyGHSXOZtULQ9HHHiWh0g9rJgv2Os95WwS1UeeFqQsUekxUjeNHsah RlIKeldEo8AgaOjGDCQiMluyNjQVxzm7ege44UYS8ZRLqtYpNiUKTaj4JzQwsPZv9fUA AGZQ== 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; bh=HuZsMpTtMDs5/dtC99dFz32xoIqYbKwcEhqrvVdX3yw=; b=IjZtkpqlBhJt6jchH1nGO8kEk8NA/49erKXul4KMoKFv9b2ZfccKZJTNa5ZoJYXh7Q hcbcDEIsJA8tIJevRDU44ZW5tn+3S6/Pdm2Mu38o75oI3p7cQp5ldOGPi5QTz6Eo1ms6 zttCabgYaF3RR/5LUTugT318lXcmKvPN9ptIRgdK37Joqj7OxmrCmvhnIB+Kb03P8EwT +URy4sM8QlQAZvI8bE7rzLZqc1hmllCRzx55d8hKbo6dQvsLgdtM1wYYRxZL5Y7iL3Gm OMzy2dAOVYd6M7j5tdWXDBF4jhbrpEuzhTi03n4fVjjLVzCeSeujH96eECN4YtL7xoNb Hc2A== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v11si186032pgb.276.2019.02.14.01.00.10; Thu, 14 Feb 2019 01:00:26 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2436863AbfBMVng (ORCPT + 99 others); Wed, 13 Feb 2019 16:43:36 -0500 Received: from mail-ot1-f68.google.com ([209.85.210.68]:33985 "EHLO mail-ot1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2391795AbfBMVng (ORCPT ); Wed, 13 Feb 2019 16:43:36 -0500 Received: by mail-ot1-f68.google.com with SMTP id 98so7034684oty.1; Wed, 13 Feb 2019 13:43:35 -0800 (PST) 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=HuZsMpTtMDs5/dtC99dFz32xoIqYbKwcEhqrvVdX3yw=; b=bHpeNj3iG62pPeP31awF33hlK2DlNahsv6p6paA6nMeLSqezXVwO8HKVkAP4H5Njdh dHukxA6d1bmD8XOyoSl5AN4GB4ORRUJwcMk6n8JmBUGHx9Zhd0nlURs4C+3+Yvq7BLsL zJE0qHCRK02T/tGKZGLibKxOhBte2bTuMph4pN0b/537oa6UxdpdR0YEz6lw7hawUH0G f5POfR+MtMWEW4hFyHvJ3Ko5W90joFe1G2LEe6bDWQCGSwVeFpQ4cY48BJ3qrnRSqOIy mH4FxLj1Q1uuuoPLXDyjea5sJU6/7GH1qklEDFUg/bXRSK8cR6TjHdHihMcLuYzwBhWy tYyw== X-Gm-Message-State: AHQUAuaKqLNlM5FrKw8UbtBDVW96zVd2X0rQFv/EYGyPpMkuIi3SXBFw 5RDWMulCxypo8UNSJ6mM7A== X-Received: by 2002:aca:ba06:: with SMTP id k6mr192060oif.159.1550094214852; Wed, 13 Feb 2019 13:43:34 -0800 (PST) Received: from localhost (24-155-109-49.dyn.grandenetworks.net. [24.155.109.49]) by smtp.gmail.com with ESMTPSA id n185sm208758oih.18.2019.02.13.13.43.33 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 13 Feb 2019 13:43:34 -0800 (PST) Date: Wed, 13 Feb 2019 15:43:33 -0600 From: Rob Herring To: Jorge Ramirez-Ortiz Cc: bjorn.andersson@linaro.org, swboyd@chromium.org, andy.gross@linaro.org, shawn.guo@linaro.org, gregkh@linuxfoundation.org, mark.rutland@arm.com, kishon@ti.com, jackp@codeaurora.org, devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, khasim.mohammed@linaro.org Subject: Re: [PATCH v4 3/4] dt-bindings: Add Qualcomm USB SuperSpeed PHY bindings Message-ID: <20190213214333.GA8220@bogus> References: <20190207111734.24171-1-jorge.ramirez-ortiz@linaro.org> <20190207111734.24171-4-jorge.ramirez-ortiz@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190207111734.24171-4-jorge.ramirez-ortiz@linaro.org> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 07, 2019 at 12:17:33PM +0100, Jorge Ramirez-Ortiz wrote: > Binding description for Qualcomm's Synopsys 1.0.0 SuperSpeed phy > controller embedded in QCS404. > > Based on Sriharsha Allenki's original > definitions. > > Signed-off-by: Jorge Ramirez-Ortiz > --- > .../bindings/phy/qcom,snps-usb-ssphy.txt | 79 +++++++++++++++++++ > 1 file changed, 79 insertions(+) > create mode 100644 Documentation/devicetree/bindings/phy/qcom,snps-usb-ssphy.txt > > diff --git a/Documentation/devicetree/bindings/phy/qcom,snps-usb-ssphy.txt b/Documentation/devicetree/bindings/phy/qcom,snps-usb-ssphy.txt > new file mode 100644 > index 000000000000..354e6f9cef62 > --- /dev/null > +++ b/Documentation/devicetree/bindings/phy/qcom,snps-usb-ssphy.txt > @@ -0,0 +1,79 @@ > +Qualcomm Synopsys 1.0.0 SS phy controller > +=========================================== > + > +Qualcomm 1.0.0 SS phy controller supports SuperSpeed USB connectivity on > +some Qualcomm platforms. > + > +Required properties: > + > +- compatible: > + Value type: > + Definition: Should contain "qcom,snps-usb-ssphy". Still not specific. Put the SoC name(s) in it. > + > +- reg: > + Value type: > + Definition: USB PHY base address and length of the register map. > + > +- #phy-cells: > + Value type: > + Definition: Should be 0. See phy/phy-bindings.txt for details. > + > +- clocks: > + Value type: > + Definition: See clock-bindings.txt section "consumers". List of > + three clock specifiers for reference, phy core and > + pipe clocks. > + > +- clock-names: > + Value type: > + Definition: Names of the clocks in 1-1 correspondence with the "clocks" > + property. Must contain "ref", "phy" and "pipe". > + > +- vdd-supply: > + Value type: > + Definition: phandle to the regulator VDD supply node. > + > +- vdda1p8-supply: > + Value type: > + Definition: phandle to the regulator 1.8V supply node. > + > +Optional properties: > + > +- resets: > + Value type: > + Definition: See reset.txt section "consumers". Specifiers for COM and > + PHY resets. > + > +- reset-names: > + Value type: > + Definition: Names of the resets in 1-1 correspondence with the "resets" > + property. Must contain "com" and "phy" if the property is > + specified. > + > +Required child nodes: > + > +- usb connector node as defined in bindings/connector/usb-connector.txt > + containing the property vbus-supply. > + > +Example: > + > +usb3_phy: usb3-phy@78000 { > + compatible = "qcom,snps-usb-ssphy"; > + reg = <0x78000 0x400>; > + #phy-cells = <0>; > + clocks = <&rpmcc RPM_SMD_LN_BB_CLK>, > + <&gcc GCC_USB_HS_PHY_CFG_AHB_CLK>, > + <&gcc GCC_USB3_PHY_PIPE_CLK>; > + clock-names = "ref", "phy", "pipe"; > + resets = <&gcc GCC_USB3_PHY_BCR>, > + <&gcc GCC_USB3PHY_PHY_BCR>; > + reset-names = "com", "phy"; > + vdd-supply = <&vreg_l3_1p05>; > + vdda1p8-supply = <&vreg_l5_1p8>; > + usb3_c_connector: usb3-c-connector { > + compatible = "usb-c-connector"; > + label = "USB-C"; > + type = "micro"; 'micro' is certainly not right for USB-C. Probably should be omitted? > + vbus-supply = <&usb3_vbus_reg>; > + }; > +}; > -- > 2.20.1 >