linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Varadarajan Narayanan <quic_varada@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 7/8] arm64: dts: qcom: ipq9574: Add USB related nodes
Date: Mon, 6 Mar 2023 16:56:48 +0530	[thread overview]
Message-ID: <61e8c730-e46d-728d-d770-f1ead4405d12@quicinc.com> (raw)
In-Reply-To: <CAA8EJprbMybV0o1-436yLhVnnEX6qywrj=JmWDCL5usaH0DXiQ@mail.gmail.com>

Dmitry,

On 3/2/2023 9:52 PM, Dmitry Baryshkov wrote:
> On Thu, 2 Mar 2023 at 11:57, Varadarajan Narayanan
> <quic_varada@quicinc.com> wrote:
>> Add USB phy and controller related nodes
>>
>> Signed-off-by: Varadarajan Narayanan <quic_varada@quicinc.com>
>> ---
>>   arch/arm64/boot/dts/qcom/ipq9574.dtsi | 92 +++++++++++++++++++++++++++++++++++
>>   1 file changed, 92 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/ipq9574.dtsi b/arch/arm64/boot/dts/qcom/ipq9574.dtsi
>> index 2bb4053..319b5bd 100644
>> --- a/arch/arm64/boot/dts/qcom/ipq9574.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/ipq9574.dtsi
>> @@ -215,6 +215,98 @@
>>                  #size-cells = <1>;
>>                  ranges = <0 0 0 0xffffffff>;
>>
>> +               ssphy_0: ssphy@7D000 {
>> +                       compatible = "qcom,ipq9574-qmp-usb3-phy";
>> +                       reg = <0x7D000 0x1C4>;
>> +                       #clock-cells = <1>;
>> +                       #address-cells = <1>;
>> +                       #size-cells = <1>;
>> +                       ranges;
>> +
>> +                       clocks = <&gcc GCC_USB0_AUX_CLK>,
>> +                                <&gcc GCC_USB0_PHY_CFG_AHB_CLK>;
>> +                       clock-names = "aux", "cfg_ahb";
>> +
>> +                       resets =  <&gcc GCC_USB0_PHY_BCR>,
>> +                                <&gcc GCC_USB3PHY_0_PHY_BCR>;
>> +                       reset-names = "phy","common";
>> +                       status = "disabled";
>> +
>> +                       usb0_ssphy: lane@7D200 {
> Please use newer style device bindings for new PHYs.
>
>> +                               reg = <0x0007D200 0x130>,       /* Tx */
>> +                                     <0x0007D400 0x200>,       /* Rx */
>> +                                     <0x0007D800 0x1F8>,       /* PCS  */
>> +                                     <0x0007D600 0x044>;       /* PCS misc */
>> +                               #phy-cells = <0>;
>> +                               clocks = <&gcc GCC_USB0_PIPE_CLK>;
>> +                               clock-names = "pipe0";
>> +                               clock-output-names = "gcc_usb0_pipe_clk_src";
> No, this clock doesn't originate from gcc, so the gcc prefix is incorrect.
>
>> +                       };
>> +               };
>> +
>> +               qusb_phy_0: qusb@7B000 {
>> +                       compatible = "qcom,ipq9574-qusb2-phy";
>> +                       reg = <0x07B000 0x180>;
>> +                       #phy-cells = <0>;
>> +
>> +                       clocks = <&gcc GCC_USB0_PHY_CFG_AHB_CLK>,
>> +                               <&xo_board_clk>;
>> +                       clock-names = "cfg_ahb", "ref";
>> +
>> +                       resets = <&gcc GCC_QUSB2_0_PHY_BCR>;
>> +                       status = "disabled";
>> +               };
>> +
>> +               usb3: usb3@8A00000 {
> You know the drill. This node is in the wrong place.
>
>> +                       compatible = "qcom,dwc3";
>> +                       reg = <0x8AF8800 0x400>;
>> +                       #address-cells = <1>;
>> +                       #size-cells = <1>;
>> +                       ranges;
>> +
>> +                       clocks = <&gcc GCC_SNOC_USB_CLK>,
>> +                               <&gcc GCC_ANOC_USB_AXI_CLK>,
>> +                               <&gcc GCC_USB0_MASTER_CLK>,
>> +                               <&gcc GCC_USB0_SLEEP_CLK>,
>> +                               <&gcc GCC_USB0_MOCK_UTMI_CLK>;
>> +
>> +                       clock-names = "sys_noc_axi",
>> +                               "anoc_axi",
>> +                               "master",
>> +                               "sleep",
>> +                               "mock_utmi";
> Please fix the indentation of the lists.
>
>> +
>> +                       assigned-clocks = <&gcc GCC_SNOC_USB_CLK>,
>> +                                         <&gcc GCC_ANOC_USB_AXI_CLK>,
> Why do you assign clock rates to the NOC clocks? Should they be set
> using the interconnect instead?

The SNOC and ANOC run at a fixed speed of 350MHz and 342MHz respectively 
and are not scaled. These clocks are for the interface between the USB 
block and the SNOC/ANOC. Do we still need to use interconnect?

>> +                                         <&gcc GCC_USB0_MASTER_CLK>,
>> +                                         <&gcc GCC_USB0_MOCK_UTMI_CLK>;
>> +                       assigned-clock-rates = <200000000>,
>> +                                              <200000000>,
>> +                                              <200000000>,
>> +                                              <24000000>;
>> +
>> +                       resets = <&gcc GCC_USB_BCR>;
>> +                       status = "disabled";
>> +
>> +                       dwc_0: dwc3@8A00000 {
>> +                               compatible = "snps,dwc3";
>> +                               reg = <0x8A00000 0xcd00>;
>> +                               clock-names = "ref";
>> +                               clocks = <&gcc GCC_USB0_MOCK_UTMI_CLK>;
> clocks before clock-names
>
>> +                               interrupts = <GIC_SPI 140 IRQ_TYPE_LEVEL_HIGH>;
>> +                               phys = <&qusb_phy_0>, <&usb0_ssphy>;
>> +                               phy-names = "usb2-phy", "usb3-phy";
>> +                               tx-fifo-resize;
>> +                               snps,dis_ep_cache_eviction;
>> +                               snps,is-utmi-l1-suspend;
>> +                               snps,hird-threshold = /bits/ 8 <0x0>;
>> +                               snps,dis_u2_susphy_quirk;
>> +                               snps,dis_u3_susphy_quirk;
>> +                               snps,quirk-frame-length-adjustment = <0x0A87F0A0>;
>> +                               dr_mode = "host";
>> +                       };
>> +               };
>> +
>>                  pcie0_phy: phy@84000 {
>>                          compatible = "qcom,ipq9574-qmp-gen3x1-pcie-phy";
>>                          reg = <0x00084000 0x1bc>; /* Serdes PLL */
>> --
>> 2.7.4

Will address these and post a new revision.

Thanks

Varada


  reply	other threads:[~2023-03-06 11:27 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02  9:54 [PATCH 0/8] Enable IPQ9754 USB Varadarajan Narayanan
2023-03-02  9:55 ` [PATCH 2/8] dt-bindings: phy: qcom,qusb2: Document IPQ9574 compatible Varadarajan Narayanan
2023-03-02 16:23   ` Dmitry Baryshkov
2023-03-03  9:10     ` Varadarajan Narayanan
2023-03-03  7:36   ` Krzysztof Kozlowski
2023-03-02  9:55 ` [PATCH 3/8] dt-bindings: phy: qcom,qmp-usb: Add IPQ9574 USB3 PHY Varadarajan Narayanan
2023-03-02  9:55 ` [PATCH 4/8] clk: qcom: gcc-ipq9574: Add USB related clocks Varadarajan Narayanan
2023-03-02 16:24   ` Dmitry Baryshkov
2023-03-03  9:18     ` Varadarajan Narayanan
2023-03-02  9:55 ` [PATCH 5/8] phy: qcom-qusb2: add QUSB2 support for IPQ9574 Varadarajan Narayanan
2023-03-02 16:17   ` Dmitry Baryshkov
2023-03-03  9:19     ` Varadarajan Narayanan
2023-03-02  9:55 ` [PATCH 6/8] phy: qcom: qmp: Update IPQ9574 USB Phy initialization Sequence Varadarajan Narayanan
2023-03-02 16:16   ` Dmitry Baryshkov
2023-03-03  9:36     ` Varadarajan Narayanan
2023-03-02  9:55 ` [PATCH 7/8] arm64: dts: qcom: ipq9574: Add USB related nodes Varadarajan Narayanan
2023-03-02 16:22   ` Dmitry Baryshkov
2023-03-06 11:26     ` Varadarajan Narayanan [this message]
2023-03-06 11:51       ` Dmitry Baryshkov
2023-03-07  6:36         ` Varadarajan Narayanan
2023-03-07 11:49           ` Dmitry Baryshkov
2023-03-08  5:52             ` Varadarajan Narayanan
2023-03-16  6:30             ` Varadarajan Narayanan
2023-03-16  6:45               ` Manivannan Sadhasivam
2023-03-03  7:39   ` Krzysztof Kozlowski
2023-03-03  9:52     ` Varadarajan Narayanan
2023-03-02  9:55 ` [PATCH 8/8] arm64: dts: qcom: ipq9574: Enable USB Varadarajan Narayanan
2023-03-02 16:18   ` Dmitry Baryshkov
2023-03-03  9:54     ` Varadarajan Narayanan
2023-03-03  7:38   ` Krzysztof Kozlowski
2023-03-21  8:54 ` [PATCH v2 0/8] Enable IPQ9754 USB Varadarajan Narayanan
2023-03-21  8:54   ` [PATCH v2 1/8] dt-bindings: phy: qcom,qusb2: Document IPQ9574 compatible Varadarajan Narayanan
2023-03-21 11:17     ` Dmitry Baryshkov
2023-03-22  6:13       ` Varadarajan Narayanan
2023-03-21  8:54   ` [PATCH v2 2/8] dt-bindings: phy: qcom,qmp-usb: Add IPQ9574 USB3 PHY Varadarajan Narayanan
2023-03-21  8:54   ` [PATCH v2 3/8] dt-bindings: usb: dwc3: Add IPQ9574 compatible Varadarajan Narayanan
2023-03-21  8:54   ` [PATCH v2 4/8] clk: qcom: gcc-ipq9574: Add USB related clocks Varadarajan Narayanan
2023-03-21 17:45     ` Stephen Boyd
2023-04-06 18:45     ` Bjorn Andersson
2023-04-06 18:44       ` Krzysztof Kozlowski
2023-03-21  8:54   ` [PATCH v2 5/8] phy: qcom-qusb2: add QUSB2 support for IPQ9574 Varadarajan Narayanan
2023-03-21  8:54   ` [PATCH v2 6/8] phy: qcom: qmp: Update IPQ9574 USB Phy initialization Sequence Varadarajan Narayanan
2023-03-21 12:07     ` Konrad Dybcio
2023-03-22  6:14       ` Varadarajan Narayanan
2023-03-21  8:54   ` [PATCH v2 7/8] arm64: dts: qcom: ipq9574: Add USB related nodes Varadarajan Narayanan
2023-03-21 11:23     ` Dmitry Baryshkov
2023-03-22  6:16       ` Varadarajan Narayanan
2023-03-21  8:54   ` [PATCH v2 8/8] arm64: dts: qcom: ipq9574: Enable USB Varadarajan Narayanan
2023-03-21 11:53   ` [PATCH v2 0/8] Enable IPQ9754 USB Konrad Dybcio
2023-03-22  6:18     ` Varadarajan Narayanan

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=61e8c730-e46d-728d-d770-f1ead4405d12@quicinc.com \
    --to=quic_varada@quicinc.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.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).