From: Xin Liu <quic_liuxin@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
Bart Van Assche <bvanassche@acm.org>,
Andy Gross <agross@kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-phy@lists.infradead.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
<quic_jiegan@quicinc.com>, <quic_aiquny@quicinc.com>,
<quic_tingweiz@quicinc.com>, <quic_sayalil@quicinc.com>
Subject: Re: [PATCH v3 2/3] arm64: dts: qcom: qcs615: add UFS node
Date: Mon, 9 Dec 2024 15:56:13 +0800 [thread overview]
Message-ID: <677251eb-d3c3-48e1-ba79-fb8ec1e29c6f@quicinc.com> (raw)
In-Reply-To: <d4f7ca97-b37e-4b8f-918c-9976e4a9cf41@oss.qualcomm.com>
在 2024/12/6 5:21, Konrad Dybcio 写道:
> On 22.11.2024 7:44 AM, Xin Liu wrote:
>> From: Sayali Lokhande <quic_sayalil@quicinc.com>
>>
>> Add the UFS Host Controller node and its PHY for QCS615 SoC.
>>
>> Signed-off-by: Sayali Lokhande <quic_sayalil@quicinc.com>
>> Co-developed-by: Xin Liu <quic_liuxin@quicinc.com>
>> Signed-off-by: Xin Liu <quic_liuxin@quicinc.com>
>> ---
>
> [...]
>
>> +
>> + operating-points-v2 = <&ufs_opp_table>;
>> + interconnects = <&aggre1_noc MASTER_UFS_MEM QCOM_ICC_TAG_ALWAYS
>> + &mc_virt SLAVE_EBI1 QCOM_ICC_TAG_ALWAYS>,
>> + <&gem_noc MASTER_APPSS_PROC QCOM_ICC_TAG_ALWAYS
>> + &config_noc SLAVE_UFS_MEM_CFG QCOM_ICC_TAG_ALWAYS>;
>
> QCOM_ICC_TAG_ACTIVE_ONLY for the cpu path
I need to ask you for advice. I have reviewed the ufs_mem_hc of many
devices and found that all of them use QCOM_ICC_TAG_ALWAYS for their
interconnects cpu path. Why do I need to use QCOM_ICC_TAG_ACTIVE_ONLY here?
>
>> + interconnect-names = "ufs-ddr",
>> + "cpu-ufs";
>> +
>> + power-domains = <&gcc UFS_PHY_GDSC>;
>> + required-opps = <&rpmhpd_opp_nom>;
>
> this contradicts the levels in the OPP table:
The required-opps here corresponds to opp-200000000 in the opp_table
below. Similarly, I referred to sm8550.dtsi, whose required-opps also
corresponds to the opp table.
>
>> +
>> + iommus = <&apps_smmu 0x300 0x0>;
>> + dma-coherent;
>> +
>> + lanes-per-direction = <1>;
>> +
>> + phys = <&ufs_mem_phy>;
>> + phy-names = "ufsphy";
>> +
>> + #reset-cells = <1>;
>> +
>> + status = "disabled";
>> +
>> + ufs_opp_table: opp-table {
>> + compatible = "operating-points-v2";
>> +
>> + opp-50000000 {
>> + opp-hz = /bits/ 64 <50000000>,
>> + /bits/ 64 <0>,
>> + /bits/ 64 <0>,
>> + /bits/ 64 <37500000>,
>> + /bits/ 64 <75000000>,
>> + /bits/ 64 <0>,
>> + /bits/ 64 <0>,
>> + /bits/ 64 <0>;
>> + required-opps = <&rpmhpd_opp_low_svs>;
>> + };
>> +
>
> Konrad
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2024-12-09 7:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 6:44 [PATCH v3 0/3] Enable UFS on QCS615 Xin Liu
2024-11-22 6:44 ` [PATCH v3 1/3] dt-bindings: ufs: qcom: Add UFS Host Controller for QCS615 Xin Liu
2024-11-22 6:44 ` [PATCH v3 2/3] arm64: dts: qcom: qcs615: add UFS node Xin Liu
2024-12-02 14:44 ` Manivannan Sadhasivam
2024-12-05 21:21 ` Konrad Dybcio
2024-12-09 7:56 ` Xin Liu [this message]
2024-12-12 16:11 ` Konrad Dybcio
2024-11-22 6:44 ` [PATCH v3 3/3] arm64: dts: qcom: qcs615-ride: Enable " Xin Liu
2024-12-02 14:48 ` Manivannan Sadhasivam
2024-12-09 8:31 ` Xin Liu
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=677251eb-d3c3-48e1-ba79-fb8ec1e29c6f@quicinc.com \
--to=quic_liuxin@quicinc.com \
--cc=agross@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andersson@kernel.org \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_aiquny@quicinc.com \
--cc=quic_jiegan@quicinc.com \
--cc=quic_sayalil@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=robh@kernel.org \
--cc=vkoul@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