From: Taniya Das <taniya.das@oss.qualcomm.com>
To: Bjorn Andersson <andersson@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Taniya Das <quic_tdas@quicinc.com>,
Ajit Pandey <quic_ajipan@quicinc.com>,
Imran Shaik <quic_imrashai@quicinc.com>,
Jagadeesh Kona <quic_jkona@quicinc.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 6/7] dt-bindings: clock: qcom: document the Glymur Global Clock Controller
Date: Thu, 14 Aug 2025 23:29:08 +0530 [thread overview]
Message-ID: <657a4915-fc24-4e6e-bd28-4e122e66c97d@oss.qualcomm.com> (raw)
In-Reply-To: <2ac5aaa8-18ba-466a-ba67-8212daf9c3b5@oss.qualcomm.com>
>>> + - description: USB 2 Phy PIPEGMUX clock source
>>> + - description: USB 2 Phy SYS PCIE PIPEGMUX clock source
>>> + - description: PCIe 3a pipe clock
>>> + - description: PCIe 4b pipe clock
Bjorn, will fix this typo and the below one as well.
>>> + - description: PCIe 4 pipe clock
>>> + - description: PCIe 5 pipe clock
>>> + - description: PCIe 6 pipe clock
>>> + - description: PCIe 6b pipe clock
Got this extra due to huge list of external clocks.
>>
>> When I look at the documentation, we seem to have pipe clocks for pcie
>> 0, 1, 2, 3a, 3b, 4, 5, and 6. And this seems to better match the clock
>> defines below as well...
>>
>
> Bjorn, the PCIE 0, 1, 2 are connected to USB4 PHY 0/1/2 pcie pipe clock
> source.
>
>> Can you please confirm that the inputs you have listed here are complete
>> and correct? (It's not going to be possible to add things in the middle
>> later and adding 0, 1, and 2 at the bottom will not sit well with my
>> OCD).
>>
>
> These are the complete list of external clocks and nothing else is required.
>
>> Regards,
>> Bjorn
>>
>>> + - description: QUSB4 0 PHY RX 0 clock source
>>> + - description: QUSB4 0 PHY RX 1 clock source
>>> + - description: QUSB4 1 PHY RX 0 clock source
>>> + - description: QUSB4 1 PHY RX 1 clock source
>>> + - description: QUSB4 2 PHY RX 0 clock source
>>> + - description: QUSB4 2 PHY RX 1 clock source
>>> + - description: UFS PHY RX Symbol 0 clock source
>>> + - description: UFS PHY RX Symbol 1 clock source
>>> + - description: UFS PHY TX Symbol 0 clock source
>>> + - description: USB3 PHY 0 pipe clock source
>>> + - description: USB3 PHY 1 pipe clock source
>>> + - description: USB3 PHY 2 pipe clock source
>>> + - description: USB3 UNI PHY pipe 0 clock source
>>> + - description: USB3 UNI PHY pipe 1 clock source
>>> + - description: USB4 PHY 0 pcie pipe clock source
>>> + - description: USB4 PHY 0 Max pipe clock source
>>> + - description: USB4 PHY 1 pcie pipe clock source
>>> + - description: USB4 PHY 1 Max pipe clock source
>>> + - description: USB4 PHY 2 pcie pipe clock source
>>> + - description: USB4 PHY 2 Max pipe clock source
>>> +
>>> +required:
>>> + - compatible
>>> + - clocks
>>> + - '#power-domain-cells'
>>> +
>>> +allOf:
>>> + - $ref: qcom,gcc.yaml#
>>> +
>>> +unevaluatedProperties: false
>>> +
>>> +examples:
>>> + - |
>>> + #include <dt-bindings/clock/qcom,rpmh.h>
>>> + clock-controller@100000 {
>>> + compatible = "qcom,glymur-gcc";
>>> + reg = <0x100000 0x1f9000>;
>>> + clocks = <&rpmhcc RPMH_CXO_CLK>,
>>> + <&rpmhcc RPMH_CXO_CLK_A>,
>>> + <&sleep_clk>,
>>> + <&usb_0_phy_dp0_gmux>,
>>> + <&usb_0_phy_dp1_gmux>,
>>> + <&usb_0_phy_pcie_pipegmux>,
>>> + <&usb_0_phy_pipegmux>,
>>> + <&usb_0_phy_sys_pcie_pipegmux>,
>>> + <&usb_1_phy_dp0_gmux_2>,
>>> + <&usb_1_phy_dp1_gmux_2>,
>>> + <&usb_1_phy_pcie_pipegmux>,
>>> + <&usb_1_phy_pipegmux>,
>>> + <&usb_1_phy_sys_pcie_pipegmux>,
>>> + <&usb_2_phy_dp0_gmux 2>,
>>> + <&usb_2_phy_dp1_gmux 2>,
>>> + <&usb_2_phy_pcie_pipegmux>,
>>> + <&usb_2_phy_pipegmux>,
>>> + <&usb_2_phy_sys_pcie_pipegmux>,
>>> + <&pcie_3a_pipe>, <&pcie_4b_pipe>,
Fix here.
>>> + <&pcie_4_pipe>, <&pcie_5_pipe>,
>>> + <&pcie_6_pipe>, <&pcie_6b_pipe>,
Fix here as well.
>>> + <&qusb4_0_phy_rx_0>, <&qusb4_0_phy_rx_1>,
>>> + <&qusb4_1_phy_rx_0>, <&qusb4_1_phy_rx_1>,
>>> + <&qusb4_2_phy_rx_0>, <&qusb4_2_phy_rx_1>,
>>> + <&ufs_phy_rx_symbol_0>, <&ufs_phy_rx_symbol_1>,
>>> + <&ufs_phy_tx_symbol_0>,
>>> + <&usb3_phy_0_pipe>, <&usb3_phy_1_pipe>,
>>> + <&usb3_phy_2_pipe>,
>>> + <&usb3_uni_phy_pipe_0>, <&usb3_uni_phy_pipe_1>,
>>> + <&usb4_phy_0_pcie_pipe>, <&usb4_phy_0_max_pipe>,
>>> + <&usb4_phy_1_pcie_pipe>, <&usb4_phy_1_max_pipe>,
>>> + <&usb4_phy_2_pcie_pipe>, <&usb4_phy_2_max_pipe>;
>>> + #clock-cells = <1>;
>>> + #reset-cells = <1>;
>>> + #power-domain-cells = <1>;
>>> + };
>>> +
--
Thanks,
Taniya Das
next prev parent reply other threads:[~2025-08-14 17:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 7:55 [PATCH v4 0/7] Add support for Clock controllers for Glymur SoC Taniya Das
2025-08-13 7:55 ` [PATCH v4 1/7] dt-bindings: clock: qcom-rpmhcc: Add support for Glymur SoCs Taniya Das
2025-08-13 13:40 ` Bjorn Andersson
2025-08-14 8:05 ` Krzysztof Kozlowski
2025-08-13 7:55 ` [PATCH v4 2/7] dt-bindings: clock: qcom: Document the Glymur SoC TCSR Clock Controller Taniya Das
2025-08-13 13:41 ` Bjorn Andersson
2025-08-14 8:07 ` Krzysztof Kozlowski
2025-08-14 8:07 ` Krzysztof Kozlowski
2025-08-14 17:55 ` Taniya Das
2025-08-13 7:55 ` [PATCH v4 3/7] clk: qcom: Add TCSR clock driver for Glymur SoC Taniya Das
2025-08-20 8:39 ` Abel Vesa
2025-08-13 7:55 ` [PATCH v4 4/7] clk: qcom: rpmh: Add support for Glymur rpmh clocks Taniya Das
2025-08-13 7:55 ` [PATCH v4 5/7] clk: qcom: clk-alpha-pll: Add support for Taycan EKO_T PLL Taniya Das
2025-08-13 7:55 ` [PATCH v4 6/7] dt-bindings: clock: qcom: document the Glymur Global Clock Controller Taniya Das
2025-08-13 13:51 ` Bjorn Andersson
2025-08-14 13:06 ` Taniya Das
2025-08-14 17:59 ` Taniya Das [this message]
2025-08-13 7:55 ` [PATCH v4 7/7] clk: qcom: gcc: Add support for " Taniya Das
2025-08-13 13:45 ` Dmitry Baryshkov
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=657a4915-fc24-4e6e-bd28-4e122e66c97d@oss.qualcomm.com \
--to=taniya.das@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_ajipan@quicinc.com \
--cc=quic_imrashai@quicinc.com \
--cc=quic_jkona@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=robh@kernel.org \
--cc=sboyd@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).