devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ram Kumar Dwivedi <quic_rdwivedi@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, <mani@kernel.org>,
	<alim.akhtar@samsung.com>, <avri.altman@wdc.com>,
	<bvanassche@acm.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
	<conor+dt@kernel.org>, <andersson@kernel.org>,
	<konradybcio@kernel.org>, <agross@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V1 2/3] arm64: dts: qcom: sm8650: Enable MCQ support for UFS controller
Date: Thu, 31 Jul 2025 14:04:26 +0530	[thread overview]
Message-ID: <40ace3bc-7e5d-417a-b51a-148c5f498992@quicinc.com> (raw)
In-Reply-To: <eab85cb3-7185-4474-9428-8699fbe4a8e5@kernel.org>



On 31-Jul-25 12:15 PM, Krzysztof Kozlowski wrote:
> On 30/07/2025 10:22, Ram Kumar Dwivedi wrote:
>> Enable Multi-Circular Queue (MCQ) support for the UFS host controller
>> on the Qualcomm SM8650 platform by updating the device tree node. This
>> includes adding new register regions and specifying the MSI parent
>> required for MCQ operation.
>>
>> MCQ is a modern queuing model for UFS that improves performance and
>> scalability by allowing multiple hardware queues. 
>>
>> Changes:
>> - Add reg entries for mcq_sqd and mcq_vs regions.
>> - Define reg-names for the new regions.
>> - Specify msi-parent for interrupt routing.
>>
>> Signed-off-by: Ram Kumar Dwivedi <quic_rdwivedi@quicinc.com>
>> ---
>>  arch/arm64/boot/dts/qcom/sm8650.dtsi | 9 ++++++++-
>>  1 file changed, 8 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/sm8650.dtsi b/arch/arm64/boot/dts/qcom/sm8650.dtsi
>> index e14d3d778b71..5d164fe511ba 100644
>> --- a/arch/arm64/boot/dts/qcom/sm8650.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/sm8650.dtsi
>> @@ -3982,7 +3982,12 @@ ufs_mem_phy: phy@1d80000 {
>>  
>>  		ufs_mem_hc: ufshc@1d84000 {
>>  			compatible = "qcom,sm8650-ufshc", "qcom,ufshc", "jedec,ufs-2.0";
>> -			reg = <0 0x01d84000 0 0x3000>;
>> +			reg = <0 0x01d84000 0 0x3000>,
>> +			      <0 0x01da5000 0 0x2000>,
>> +			      <0 0x01da4000 0 0x0010>;
> 
> 
> These are wrong address spaces. Open your datasheet and look there.
>
Hi Krzysztof,

I’ve reviewed it again, and it is correct and functioning as expected both on our upstream and downstream codebase.
I think it is probably overlooked by you. Can you please double check from your end?

Thanks,
Ram.
 
> 
> Best regards,
> Krzysztof




  reply	other threads:[~2025-07-31  8:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-30  8:22 [PATCH V1 0/3] Enable UFS MCQ support for SM8650 and SM8750 Ram Kumar Dwivedi
2025-07-30  8:22 ` [PATCH V1 1/3] dt-bindings: ufs: qcom: Add reg and reg-names Ram Kumar Dwivedi
2025-07-30  9:11   ` Krzysztof Kozlowski
2025-07-30 10:27     ` Ram Kumar Dwivedi
2025-07-30 11:33       ` Krzysztof Kozlowski
2025-07-30 12:44         ` Krzysztof Kozlowski
2025-07-30  8:22 ` [PATCH V1 2/3] arm64: dts: qcom: sm8650: Enable MCQ support for UFS controller Ram Kumar Dwivedi
2025-07-30  9:12   ` Krzysztof Kozlowski
2025-07-30 10:30     ` Ram Kumar Dwivedi
2025-07-31  6:45   ` Krzysztof Kozlowski
2025-07-31  8:34     ` Ram Kumar Dwivedi [this message]
2025-07-31  8:38       ` Krzysztof Kozlowski
2025-08-01 12:24         ` Manivannan Sadhasivam
2025-08-01 14:20           ` Krzysztof Kozlowski
2025-08-01 15:33             ` Manivannan Sadhasivam
2025-08-01 16:09               ` Krzysztof Kozlowski
2025-08-11  9:27                 ` Manivannan Sadhasivam
2025-08-11 14:34                   ` Ram Kumar Dwivedi
2025-08-12 11:51                   ` Konrad Dybcio
2025-07-30  8:22 ` [PATCH V1 3/3] arm64: dts: qcom: sm8750: " Ram Kumar Dwivedi
2025-07-31  8:50 ` [PATCH V1 0/3] Enable UFS MCQ support for SM8650 and SM8750 neil.armstrong
2025-08-01 12:43   ` Manivannan Sadhasivam

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=40ace3bc-7e5d-417a-b51a-148c5f498992@quicinc.com \
    --to=quic_rdwivedi@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=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mani@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).