From: Palash Kambar <quic_pkambar@quicinc.com>
To: Manivannan Sadhasivam <mani@kernel.org>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: <James.Bottomley@hansenpartnership.com>,
<martin.petersen@oracle.com>, <linux-arm-msm@vger.kernel.org>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<quic_nitirawa@quicinc.com>
Subject: Re: [PATCH v1] ufs: ufs-qcom: Align programming sequence of Shared ICE for UFS controller v5
Date: Thu, 7 Aug 2025 15:52:20 +0530 [thread overview]
Message-ID: <0bfb6a39-785b-431f-9cd4-c63df35c5ac3@quicinc.com> (raw)
In-Reply-To: <mhridnexscaevsmssu6k3l4x276cj63gl2rlvypym23kj2kgov@pw323zkhqcrg>
On 8/6/2025 11:09 PM, Manivannan Sadhasivam wrote:
> On Wed, Aug 06, 2025 at 02:56:43PM GMT, Konrad Dybcio wrote:
>> On 8/6/25 1:14 PM, Manivannan Sadhasivam wrote:
>>> On Wed, Aug 06, 2025 at 12:04:09PM GMT, Palash Kambar wrote:
>>>> Disable of AES core in Shared ICE is not supported during power
>>>> collapse for UFS Host Controller V5.0.
>>>>
>>>> Hence follow below steps to reset the ICE upon exiting power collapse
>>>> and align with Hw programming guide.
>>>>
>>>> a. Write 0x18 to UFS_MEM_ICE_CFG
>>>> b. Write 0x0 to UFS_MEM_ICE_CFG
>>>>
>>>> Signed-off-by: Palash Kambar <quic_pkambar@quicinc.com>
>>>> ---
>>
>> [...]
>>
>>>
>>>> + ufshcd_readl(hba, UFS_MEM_ICE);
>>>> + ufshcd_writel(hba, 0x0, UFS_MEM_ICE);
>>>> + ufshcd_readl(hba, UFS_MEM_ICE);
>>>
>>> Why do you need readl()? Writes to device memory won't get reordered.
>>
>> I'm not sure if we need a delay between them, otherwise they'll happen
>> within a couple cycles of each other which may not be enough since this
>> is a synchronous reset and the clock period is 20-50ns when running at
>> XO (19.2 / 38.4 MHz) rate
>>
>
> IIUC, the second register write is just reenabling the mask, so there is no
> delay required between these two writes. If that's not true, and if there is a
> delay required, then do:
>
> ufshcd_writel(0x18);
> ufshcd_readl();
> usleep()/msleep();
> ufshcd_write(0x0);
>
I will address this in next patch set.
-Palash K
next prev parent reply other threads:[~2025-08-07 10:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 6:34 Palash Kambar
2025-08-06 11:14 ` Manivannan Sadhasivam
2025-08-06 12:41 ` Palash Kambar
2025-08-06 17:49 ` Manivannan Sadhasivam
2025-08-07 10:20 ` Palash Kambar
2025-08-11 8:16 ` Manivannan Sadhasivam
2025-08-12 5:04 ` Palash Kambar
2025-08-06 12:56 ` Konrad Dybcio
2025-08-06 17:39 ` Manivannan Sadhasivam
2025-08-07 10:22 ` Palash Kambar [this message]
2025-08-07 11:06 ` Konrad Dybcio
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=0bfb6a39-785b-431f-9cd4-c63df35c5ac3@quicinc.com \
--to=quic_pkambar@quicinc.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_nitirawa@quicinc.com \
/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®