devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sandeep Maheswaram (Temp)" <sanm@codeaurora.org>
To: Stephen Boyd <swboyd@chromium.org>,
	Andy Gross <agross@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Rob Herring <robh+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	Manu Gautam <mgautam@codeaurora.org>
Subject: Re: [PATCH 1/1] arm64: dts: qcom: sc7180: Add USB related nodes
Date: Wed, 6 Nov 2019 15:07:26 +0530	[thread overview]
Message-ID: <3aa0e1a5-9dd6-fdb5-057d-70af88218fb4@codeaurora.org> (raw)
In-Reply-To: <5dc0c729.1c69fb81.4575.3392@mx.google.com>


On 11/5/2019 6:19 AM, Stephen Boyd wrote:
> Quoting Sandeep Maheswaram (2019-10-31 06:49:22)
>> diff --git a/arch/arm64/boot/dts/qcom/sc7180-idp.dts b/arch/arm64/boot/dts/qcom/sc7180-idp.dts
>> index 189254f..aecc994 100644
>> --- a/arch/arm64/boot/dts/qcom/sc7180-idp.dts
>> +++ b/arch/arm64/boot/dts/qcom/sc7180-idp.dts
>> @@ -400,3 +400,28 @@
>>                          bias-pull-up;
>>                  };
>>   };
>> +
>> +&usb_1 {
>> +       status = "okay";
>> +};
>> +
>> +&usb_1_dwc3 {
>> +       dr_mode = "host";
>> +};
>> +
>> +&usb_1_hsphy {
>> +       status = "okay";
>> +       vdd-supply = <&vreg_l4a_0p8>;
>> +       vdda-pll-supply = <&vreg_l11a_1p8>;
>> +       vdda-phy-dpdm-supply = <&vreg_l17a_3p0>;
>> +       qcom,imp-res-offset-value = <8>;
>> +       qcom,hstx-trim-value = <QUSB2_V2_HSTX_TRIM_21_6_MA>;
>> +       qcom,preemphasis-level = <QUSB2_V2_PREEMPHASIS_5_PERCENT>;
>> +       qcom,preemphasis-width = <QUSB2_V2_PREEMPHASIS_WIDTH_HALF_BIT>;
>> +};
>> +
>> +&usb_1_qmpphy {
>> +       status = "okay";
>> +       vdda-phy-supply = <&vreg_l3c_1p2>;
>> +       vdda-pll-supply = <&vreg_l4a_0p8>;
>> +};
>> \ No newline at end of file
> Why is there no newline at end of file?
Will correct in next version.
>> diff --git a/arch/arm64/boot/dts/qcom/sc7180.dtsi b/arch/arm64/boot/dts/qcom/sc7180.dtsi
>> index cb623b7..7ee068f 100644
>> --- a/arch/arm64/boot/dts/qcom/sc7180.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/sc7180.dtsi
>> @@ -9,6 +9,7 @@
>>   #include <dt-bindings/clock/qcom,rpmh.h>
>>   #include <dt-bindings/interrupt-controller/arm-gic.h>
>>   #include <dt-bindings/soc/qcom,rpmh-rsc.h>
>> +#include <dt-bindings/phy/phy-qcom-qusb2.h>
> Sort includes?
Will correct in next version.
>>   
>>   / {
>>          interrupt-parent = <&intc>;
>> @@ -184,6 +185,17 @@
>>                          #power-domain-cells = <1>;
>>                  };
>>   
>> +               qfprom@784000 {
>> +                       compatible = "qcom,qfprom";
>> +                       reg = <0 0x00784000 0 0x8ff>;
>> +                       #address-cells = <1>;
>> +                       #size-cells = <1>;
>> +
>> +                       qusb2p_hstx_trim: hstx-trim-primary@25b {
>> +                               reg = <0x25b 0x1>;
>> +                               bits = <1 3>;
>> +                       };
>> +               };
> Add newline here?
Will correct in next version.
>
>>                  pdc: interrupt-controller@b220000 {
>>                          compatible = "qcom,sdm845-pdc";
>>                          reg = <0 0xb220000 0 0x30000>;
>> @@ -913,6 +925,98 @@
>>                          status = "disabled";
>>                  };
>>   
>> +               usb_1_hsphy: phy@88e3000 {
>> +                       compatible = "qcom,sc7180-qusb2-phy";
>> +                       reg = <0 0x088e3000 0 0x400>;
>> +                       status = "disabled";
>> +                       #phy-cells = <0>;
>> +                       clocks = <&gcc GCC_USB_PHY_CFG_AHB2PHY_CLK>,
>> +                       <&rpmhcc RPMH_CXO_CLK>;
> Nitpick: Can you indent this to align with clocks above?
Will correct in next version.
>
>> +                       clock-names = "cfg_ahb","ref";
>> +                       resets = <&gcc GCC_QUSB2PHY_PRIM_BCR>;
>> +
>> +                       nvmem-cells = <&qusb2p_hstx_trim>;
>> +               };
>> +
>> +               usb_1_qmpphy: phy@88e9000 {
>> +                       compatible = "qcom,sc7180-qmp-usb3-phy";
>> +                       reg = <0 0x088e9000 0 0x18c>,
>> +                             <0 0x088e8000 0 0x38>;
>> +                       reg-names = "reg-base", "dp_com";
>> +                       status = "disabled";
>> +                       #clock-cells = <1>;
>> +                       #address-cells = <2>;
>> +                       #size-cells = <2>;
>> +                       ranges;
>> +
>> +                       clocks = <&gcc GCC_USB3_PRIM_PHY_AUX_CLK>,
>> +                                <&gcc GCC_USB_PHY_CFG_AHB2PHY_CLK>,
>> +                                <&gcc GCC_USB3_PRIM_CLKREF_CLK>,
>> +                                <&gcc GCC_USB3_PRIM_PHY_COM_AUX_CLK>;
>> +                       clock-names = "aux", "cfg_ahb", "ref", "com_aux";
>> +
>> +                       resets = <&gcc GCC_USB3_DP_PHY_PRIM_BCR>,
>> +                                <&gcc GCC_USB3_PHY_PRIM_BCR>;
>> +                       reset-names = "phy", "common";
>> +
>> +                       usb_1_ssphy: lanes@88e9200 {
>> +                               reg = <0 0x088e9200 0 0x128>,
>> +                                     <0 0x088e9400 0 0x200>,
>> +                                     <0 0x088e9c00 0 0x218>,
>> +                                     <0 0x088e9600 0 0x128>,
>> +                                     <0 0x088e9800 0 0x200>,
>> +                                     <0 0x088e9a00 0 0x18>;
>> +                               #phy-cells = <0>;
>> +                               clocks = <&gcc GCC_USB3_PRIM_PHY_PIPE_CLK>;
>> +                               clock-names = "pipe0";
>> +                               clock-output-names = "usb3_phy_pipe_clk_src";
> Does this clock go somewhere? Like GCC?
Yes this clock will go to GCC.
>> +                       };
>> +               };
>> +

-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation


      reply	other threads:[~2019-11-06  9:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31 13:49 [PATCH 0/1] Add USB related nodes for SC7180 Sandeep Maheswaram
2019-10-31 13:49 ` [PATCH 1/1] arm64: dts: qcom: sc7180: Add USB related nodes Sandeep Maheswaram
2019-11-05  0:49   ` Stephen Boyd
2019-11-06  9:37     ` Sandeep Maheswaram (Temp) [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3aa0e1a5-9dd6-fdb5-057d-70af88218fb4@codeaurora.org \
    --to=sanm@codeaurora.org \
    --cc=agross@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mgautam@codeaurora.org \
    --cc=robh+dt@kernel.org \
    --cc=swboyd@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).