From: Manivannan Sadhasivam <mani@kernel.org>
To: Andrew Halaney <ahalaney@redhat.com>
Cc: 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>,
Yaniv Gardi <ygardi@codeaurora.org>,
Dov Levenglick <dovl@codeaurora.org>,
Hannes Reinecke <hare@suse.de>,
Subhash Jadavani <subhashj@codeaurora.org>,
Gilad Broner <gbroner@codeaurora.org>,
Venkat Gopalakrishnan <venkatg@codeaurora.org>,
Janek Kotas <jank@cadence.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
Bart Van Assche <bvanassche@acm.org>,
Anjana Hari <quic_ahari@quicinc.com>,
Dolev Raviv <draviv@codeaurora.org>,
Can Guo <quic_cang@quicinc.com>, Will Deacon <will@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC v2 03/11] scsi: ufs: qcom: Perform read back after writing testbus config
Date: Wed, 27 Dec 2023 11:17:34 +0530 [thread overview]
Message-ID: <20231227054734.GA2814@thinkpad> (raw)
In-Reply-To: <20231221-ufs-reset-ensure-effect-before-delay-v2-3-75af2a9bae51@redhat.com>
On Thu, Dec 21, 2023 at 12:25:20PM -0600, Andrew Halaney wrote:
> Currently, the testbus configuration is written and completed with an
> mb().
>
> 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. Because the mb()'s
> purpose wasn't to add extra ordering (on top of the ordering guaranteed
> by writel()/readl()), it can safely be removed.
>
> Fixes: 9c46b8676271 ("scsi: ufs-qcom: dump additional testbus registers")
> Signed-off-by: Andrew Halaney <ahalaney@redhat.com>
> ---
> drivers/ufs/host/ufs-qcom.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/ufs/host/ufs-qcom.c b/drivers/ufs/host/ufs-qcom.c
> index 4c15c8a1d058..6df2ab3b6f23 100644
> --- a/drivers/ufs/host/ufs-qcom.c
> +++ b/drivers/ufs/host/ufs-qcom.c
> @@ -1332,6 +1332,9 @@ static void ufs_qcom_enable_test_bus(struct ufs_qcom_host *host)
> ufshcd_rmwl(host->hba, UFS_REG_TEST_BUS_EN,
> UFS_REG_TEST_BUS_EN, REG_UFS_CFG1);
> ufshcd_rmwl(host->hba, TEST_BUS_EN, TEST_BUS_EN, REG_UFS_CFG1);
> +
> + /* dummy read to ensure this has been enabled prior to returning */
> + ufshcd_readl(host->hba, REG_UFS_CFG1);
In this case, I do not see the necessity to do a read back itself since there is
no delay afterwards nor any dependent operation in an altogether different
domain.
So removing the mb() should be sufficient.
- Mani
> }
>
> static void ufs_qcom_get_default_testbus_cfg(struct ufs_qcom_host *host)
> @@ -1429,11 +1432,6 @@ int ufs_qcom_testbus_config(struct ufs_qcom_host *host)
> (u32)host->testbus.select_minor << offset,
> reg);
> ufs_qcom_enable_test_bus(host);
> - /*
> - * Make sure the test bus configuration is
> - * committed before returning.
> - */
> - mb();
>
> return 0;
> }
>
> --
> 2.43.0
>
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2023-12-27 5:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 18:25 [PATCH RFC v2 00/11] scsi: ufs: Remove overzealous memory barriers Andrew Halaney
2023-12-21 18:25 ` [PATCH RFC v2 01/11] scsi: ufs: qcom: Perform read back after writing reset bit Andrew Halaney
2023-12-21 18:25 ` [PATCH RFC v2 02/11] scsi: ufs: qcom: Perform read back after writing REG_UFS_SYS1CLK_1US Andrew Halaney
2023-12-21 18:25 ` [PATCH RFC v2 03/11] scsi: ufs: qcom: Perform read back after writing testbus config Andrew Halaney
2023-12-27 5:47 ` Manivannan Sadhasivam [this message]
2023-12-21 18:25 ` [PATCH RFC v2 04/11] scsi: ufs: qcom: Perform read back after writing unipro mode Andrew Halaney
2023-12-27 6:01 ` [PATCH RFC v2 04/11] scsi: ufs: qcom: Perform read back after writing unipro mode' Manivannan Sadhasivam
2023-12-21 18:25 ` [PATCH RFC v2 05/11] scsi: ufs: qcom: Perform read back after writing CGC enable Andrew Halaney
2023-12-27 6:04 ` [PATCH RFC v2 05/11] scsi: ufs: qcom: Perform read back after writing CGC enable' Manivannan Sadhasivam
2023-12-21 18:25 ` [PATCH RFC v2 06/11] scsi: ufs: cdns-pltfrm: Perform read back after writing HCLKDIV Andrew Halaney
2023-12-27 6:06 ` Manivannan Sadhasivam
2023-12-21 18:25 ` [PATCH RFC v2 07/11] scsi: ufs: core: Perform read back after writing UTP_TASK_REQ_LIST_BASE_H Andrew Halaney
2023-12-27 6:10 ` Manivannan Sadhasivam
2023-12-21 18:25 ` [PATCH RFC v2 08/11] scsi: ufs: core: Perform read back after disabling interrupts Andrew Halaney
2023-12-27 6:13 ` Manivannan Sadhasivam
2023-12-21 18:31 ` [PATCH RFC v2 00/11] scsi: ufs: Remove overzealous memory barriers Andrew Halaney
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=20231227054734.GA2814@thinkpad \
--to=mani@kernel.org \
--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=dovl@codeaurora.org \
--cc=draviv@codeaurora.org \
--cc=gbroner@codeaurora.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=martin.petersen@oracle.com \
--cc=quic_ahari@quicinc.com \
--cc=quic_cang@quicinc.com \
--cc=subhashj@codeaurora.org \
--cc=venkatg@codeaurora.org \
--cc=will@kernel.org \
--cc=ygardi@codeaurora.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