From: Can Guo <quic_cang@quicinc.com>
To: Andrew Halaney <ahalaney@redhat.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Hannes Reinecke <hare@suse.de>, Janek Kotas <jank@cadence.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
Bart Van Assche <bvanassche@acm.org>
Cc: Will Deacon <will@kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: Re: [PATCH RFC v3 01/11] scsi: ufs: qcom: Perform read back after writing reset bit
Date: Fri, 22 Dec 2023 16:18:38 +0800 [thread overview]
Message-ID: <7a162d14-6a7a-44f0-ab45-12abfea5dedd@quicinc.com> (raw)
In-Reply-To: <20231221-ufs-reset-ensure-effect-before-delay-v3-1-2195a1b66d2e@redhat.com>
On 12/22/2023 3:09 AM, Andrew Halaney wrote:
> Currently, the reset bit for the UFS provided reset controller (used by
> its phy) is written to, and then a mb() happens to try and ensure that
> hit the device. Immediately afterwards a usleep_range() occurs.
>
> mb() ensure that the write completes, but completion doesn't mean that
> it isn't stored in a buffer somewhere. The recommendation for
> ensuring this bit has taken effect on the device is to perform a read
> back to force it to make it all the way to the device. This is
> documented in device-io.rst and a talk by Will Deacon on this can
> be seen over here:
>
> https://youtu.be/i6DayghhA8Q?si=MiyxB5cKJXSaoc01&t=1678
>
> Let's do that to ensure the bit hits the device. By doing so and
> guaranteeing the ordering against the immediately following
> usleep_range(), the mb() can safely be removed.
>
> Fixes: 81c0fc51b7a7 ("ufs-qcom: add support for Qualcomm Technologies Inc platforms")
> Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> Signed-off-by: Andrew Halaney <ahalaney@redhat.com>
> ---
> drivers/ufs/host/ufs-qcom.h | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/ufs/host/ufs-qcom.h b/drivers/ufs/host/ufs-qcom.h
> index 9dd9a391ebb7..b9de170983c9 100644
> --- a/drivers/ufs/host/ufs-qcom.h
> +++ b/drivers/ufs/host/ufs-qcom.h
> @@ -151,10 +151,10 @@ static inline void ufs_qcom_assert_reset(struct ufs_hba *hba)
> ufshcd_rmwl(hba, UFS_PHY_SOFT_RESET, UFS_PHY_SOFT_RESET, REG_UFS_CFG1);
>
> /*
> - * Make sure assertion of ufs phy reset is written to
> - * register before returning
> + * Dummy read to ensure the write takes effect before doing any sort
> + * of delay
> */
> - mb();
> + ufshcd_readl(hba, REG_UFS_CFG1);
> }
>
> static inline void ufs_qcom_deassert_reset(struct ufs_hba *hba)
> @@ -162,10 +162,10 @@ static inline void ufs_qcom_deassert_reset(struct ufs_hba *hba)
> ufshcd_rmwl(hba, UFS_PHY_SOFT_RESET, 0, REG_UFS_CFG1);
>
> /*
> - * Make sure de-assertion of ufs phy reset is written to
> - * register before returning
> + * Dummy read to ensure the write takes effect before doing any sort
> + * of delay
> */
> - mb();
> + ufshcd_readl(hba, REG_UFS_CFG1);
> }
>
> /* Host controller hardware version: major.minor.step */
>
Reviewed-by: Can Guo <quic_cang@quicinc.com>
next prev parent reply other threads:[~2023-12-22 8:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 19:09 [PATCH RFC v3 00/11] scsi: ufs: Remove overzealous memory barriers Andrew Halaney
2023-12-21 19:09 ` [PATCH RFC v3 01/11] scsi: ufs: qcom: Perform read back after writing reset bit Andrew Halaney
2023-12-22 8:18 ` Can Guo [this message]
2023-12-21 19:09 ` [PATCH RFC v3 02/11] scsi: ufs: qcom: Perform read back after writing REG_UFS_SYS1CLK_1US Andrew Halaney
2023-12-22 8:18 ` Can Guo
2023-12-21 19:09 ` [PATCH RFC v3 03/11] scsi: ufs: qcom: Perform read back after writing testbus config Andrew Halaney
2023-12-22 8:20 ` Can Guo
2023-12-21 19:09 ` [PATCH RFC v3 04/11] scsi: ufs: qcom: Perform read back after writing unipro mode Andrew Halaney
2023-12-22 8:23 ` Can Guo
2023-12-21 19:09 ` [PATCH RFC v3 05/11] scsi: ufs: qcom: Perform read back after writing CGC enable Andrew Halaney
2023-12-22 8:25 ` Can Guo
2023-12-21 19:09 ` [PATCH RFC v3 06/11] scsi: ufs: cdns-pltfrm: Perform read back after writing HCLKDIV Andrew Halaney
2023-12-21 19:09 ` [PATCH RFC v3 07/11] scsi: ufs: core: Perform read back after writing UTP_TASK_REQ_LIST_BASE_H Andrew Halaney
2023-12-21 19:30 ` Bart Van Assche
2023-12-22 8:26 ` Can Guo
2023-12-21 19:09 ` [PATCH RFC v3 08/11] scsi: ufs: core: Perform read back after disabling interrupts Andrew Halaney
2023-12-21 19:30 ` Bart Van Assche
2023-12-22 8:26 ` Can Guo
2023-12-21 19:09 ` [PATCH RFC v3 09/11] scsi: ufs: core: Perform read back after disabling UIC_COMMAND_COMPL Andrew Halaney
2023-12-21 19:29 ` Bart Van Assche
2023-12-22 8:26 ` Can Guo
2023-12-27 6:16 ` Manivannan Sadhasivam
2023-12-21 19:09 ` [PATCH RFC v3 10/11] scsi: ufs: core: Perform read back to commit doorbell Andrew Halaney
2023-12-21 19:28 ` Bart Van Assche
2023-12-22 8:27 ` Can Guo
2023-12-27 6:18 ` Manivannan Sadhasivam
2023-12-21 19:09 ` [PATCH RFC v3 11/11] scsi: ufs: core: Perform read back before writing run/stop regs Andrew Halaney
2023-12-21 19:25 ` Bart Van Assche
2023-12-22 8:27 ` Can Guo
2023-12-27 6:21 ` Manivannan Sadhasivam
2023-12-21 19:13 ` [PATCH RFC v3 00/11] scsi: ufs: Remove overzealous memory barriers 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=7a162d14-6a7a-44f0-ab45-12abfea5dedd@quicinc.com \
--to=quic_cang@quicinc.com \
--cc=agross@kernel.org \
--cc=ahalaney@redhat.com \
--cc=alim.akhtar@samsung.com \
--cc=andersson@kernel.org \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=jank@cadence.com \
--cc=jejb@linux.ibm.com \
--cc=konrad.dybcio@linaro.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=manivannan.sadhasivam@linaro.org \
--cc=martin.petersen@oracle.com \
--cc=will@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®