From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: martin.petersen@oracle.com, jejb@linux.ibm.com,
avri.altman@wdc.com, alim.akhtar@samsung.com,
bjorn.andersson@linaro.org, linux-arm-msm@vger.kernel.org,
quic_asutoshd@quicinc.com, quic_cang@quicinc.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] scsi: ufs: core: Remove redundant wmb() in ufshcd_send_command()
Date: Sat, 23 Apr 2022 17:16:35 +0530 [thread overview]
Message-ID: <20220423114635.GC374560@thinkpad> (raw)
In-Reply-To: <10d7e4a7-4364-b579-fecf-53c953d22b7d@acm.org>
On Fri, Apr 22, 2022 at 10:19:14PM -0700, Bart Van Assche wrote:
> On 4/22/22 06:21, Manivannan Sadhasivam wrote:
> > The wmb() inside ufshcd_send_command() is added to make sure that the
> > doorbell is committed immediately.
>
> That's not the purpose of the wmb() call so I think the comment is wrong.
>
> > This leads to couple of expectations:
> >
> > 1. The doorbell write should complete before the function return.
> > 2. The doorbell write should not cross the function boundary.
> >
> > 2nd expectation is fullfilled by the Linux memory model as there is a
> > guarantee that the critical section won't cross the unlock (release)
> > operation.
>
> I think you meant that the writel() won't cross the unlock operation?
>
yes!
Thanks,
Mani
> > diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
> > index 9349557b8a01..ec514a6c5393 100644
> > --- a/drivers/scsi/ufs/ufshcd.c
> > +++ b/drivers/scsi/ufs/ufshcd.c
> > @@ -2116,9 +2116,6 @@ void ufshcd_send_command(struct ufs_hba *hba, unsigned int task_tag)
> > __set_bit(task_tag, &hba->outstanding_reqs);
> > ufshcd_writel(hba, 1 << task_tag, REG_UTP_TRANSFER_REQ_DOOR_BELL);
> > spin_unlock_irqrestore(&hba->outstanding_lock, flags);
> > -
> > - /* Make sure that doorbell is committed immediately */
> > - wmb();
> > }
>
> Anyway:
>
> Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2022-04-23 11:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 13:21 [PATCH 0/5] Qcom UFS driver updates Manivannan Sadhasivam
2022-04-22 13:21 ` [PATCH 1/5] scsi: ufs: qcom: Fix acquiring the optional reset control line Manivannan Sadhasivam
2022-04-22 15:40 ` Andrew Halaney
2022-04-23 9:54 ` Manivannan Sadhasivam
2022-04-22 13:21 ` [PATCH 2/5] scsi: ufs: qcom: Simplify handling of devm_phy_get() Manivannan Sadhasivam
2022-04-22 16:51 ` Andrew Halaney
2022-04-22 13:21 ` [PATCH 3/5] scsi: ufs: qcom: Add a readl() to make sure ref_clk gets enabled Manivannan Sadhasivam
2022-04-23 5:03 ` Bart Van Assche
2022-04-23 11:45 ` Manivannan Sadhasivam
2022-04-22 13:21 ` [PATCH 4/5] scsi: ufs: core: Remove redundant wmb() in ufshcd_send_command() Manivannan Sadhasivam
2022-04-23 5:19 ` Bart Van Assche
2022-04-23 11:46 ` Manivannan Sadhasivam [this message]
2022-04-22 13:21 ` [PATCH 5/5] scsi: ufs: qcom: Enable RPM_AUTOSUSPEND for runtime PM 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=20220423114635.GC374560@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bjorn.andersson@linaro.org \
--cc=bvanassche@acm.org \
--cc=jejb@linux.ibm.com \
--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_asutoshd@quicinc.com \
--cc=quic_cang@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;
as well as URLs for NNTP newsgroup(s).