From: Krishna Kurapati <quic_kriskura@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <quic_ppratap@quicinc.com>,
<quic_jackp@quicinc.com>
Subject: Re: [PATCH 1/2] arm64: dts: qcom: Add support for usb nodes on QCS8300
Date: Thu, 10 Oct 2024 20:26:50 +0530 [thread overview]
Message-ID: <fe3ebd31-946c-499f-ac96-2cf71c6752e6@quicinc.com> (raw)
In-Reply-To: <xwidjnw3fqc2slwl3vftw7yi4j7juiw6rwszjhtxepqd6zz33s@ncoi4aikbb4e>
On 10/10/2024 7:52 PM, Dmitry Baryshkov wrote:
> On Thu, Oct 10, 2024 at 01:26:35AM GMT, Krishna Kurapati wrote:
>> Add support for USB controllers on QCS8300. The second
>> controller is only High Speed capable.
>>
>> Signed-off-by: Krishna Kurapati <quic_kriskura@quicinc.com>
>> ---
>> arch/arm64/boot/dts/qcom/qcs8300.dtsi | 165 ++++++++++++++++++++++++++
>> 1 file changed, 165 insertions(+)
>
> [...]
>
>> +
>> + usb_2: usb@a4f8800 {
>> + compatible = "qcom,qcs8300-dwc3", "qcom,dwc3";
>> + reg = <0x0 0x0a4f8800 0x0 0x400>;
>> + #address-cells = <2>;
>> + #size-cells = <2>;
>> + ranges;
>> +
>> + clocks = <&gcc GCC_CFG_NOC_USB2_PRIM_AXI_CLK>,
>> + <&gcc GCC_USB20_MASTER_CLK>,
>> + <&gcc GCC_AGGRE_USB2_PRIM_AXI_CLK>,
>> + <&gcc GCC_USB20_SLEEP_CLK>,
>> + <&gcc GCC_USB20_MOCK_UTMI_CLK>;
>> + clock-names = "cfg_noc",
>> + "core",
>> + "iface",
>> + "sleep",
>> + "mock_utmi";
>> +
>> + assigned-clocks = <&gcc GCC_USB20_MOCK_UTMI_CLK>,
>> + <&gcc GCC_USB20_MASTER_CLK>;
>> + assigned-clock-rates = <19200000>, <120000000>;
>> +
>> + interrupts-extended = <&intc GIC_SPI 444 IRQ_TYPE_LEVEL_HIGH>,
>> + <&intc GIC_SPI 443 IRQ_TYPE_LEVEL_HIGH>,
>> + <&pdc 10 IRQ_TYPE_EDGE_BOTH>,
>> + <&pdc 9 IRQ_TYPE_EDGE_BOTH>;
>> + interrupt-names = "pwr_event",
>> + "hs_phy_irq",
>> + "dp_hs_phy_irq",
>> + "dm_hs_phy_irq";
>> +
>> + power-domains = <&gcc GCC_USB20_PRIM_GDSC>;
>> + required-opps = <&rpmhpd_opp_nom>;
>> +
>> + resets = <&gcc GCC_USB20_PRIM_BCR>;
>> +
>> + interconnects = <&aggre1_noc MASTER_USB2 0 &mc_virt SLAVE_EBI1 0>,
>> + <&gem_noc MASTER_APPSS_PROC 0 &config_noc SLAVE_USB2 0>;
>> + interconnect-names = "usb-ddr", "apps-usb";
>
> As this is a USB2-only host, shouldn't it also have qcom,select-utmi-as-pipe-clk ?
>
Hi Dmitry,
Thanks for the catch. You are right, it needs to be added according to
bindings. Since I would be sending another patch after this series to
enable the second controller, would it be fine if I add it in that patch
or do you suggest updating this one.
Also I see some others are not using it as well, like sc7280 which also
might need to be updated.
Regards,
Krishna,
>> +
>> + status = "disabled";
>> +
>> + usb_2_dwc3: usb@a400000 {
>> + compatible = "snps,dwc3";
>> + reg = <0x0 0x0a400000 0x0 0xe000>;
>> + interrupts = <GIC_SPI 442 IRQ_TYPE_LEVEL_HIGH>;
>> + iommus = <&apps_smmu 0x20 0x0>;
>> + phys = <&usb_2_hsphy>;
>> + phy-names = "usb2-phy";
>> + snps,dis_u2_susphy_quirk;
>> + snps,dis_enblslpm_quirk;
>> + };
>> + };
>> };
>>
>> arch_timer: timer {
>> --
>> 2.34.1
>>
>
next prev parent reply other threads:[~2024-10-10 14:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 19:56 [PATCH 0/2] Add Devicetree support for USB controllers " Krishna Kurapati
2024-10-09 19:56 ` [PATCH 1/2] arm64: dts: qcom: Add support for usb nodes " Krishna Kurapati
2024-10-10 14:22 ` Dmitry Baryshkov
2024-10-10 14:56 ` Krishna Kurapati [this message]
2024-10-10 15:12 ` Dmitry Baryshkov
2024-10-10 15:34 ` Krishna Kurapati
2024-10-09 19:56 ` [PATCH 2/2] arm64: dts: qcom: Enable USB controllers for QCS8300 Krishna Kurapati
2024-10-10 16:04 ` Dmitry Baryshkov
2024-10-10 16:27 ` Krishna Kurapati
2024-10-10 18:06 ` 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=fe3ebd31-946c-499f-ac96-2cf71c6752e6@quicinc.com \
--to=quic_kriskura@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_jackp@quicinc.com \
--cc=quic_ppratap@quicinc.com \
--cc=robh@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
all inboxes | Powered by JetHome®