From: "DooHyun Hwang" <dh0421.hwang@samsung.com>
To: "'Avri Altman'" <Avri.Altman@wdc.com>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<alim.akhtar@samsung.com>, <bvanassche@acm.org>,
<James.Bottomley@HansenPartnership.com>,
<martin.petersen@oracle.com>, <peter.wang@mediatek.com>,
<manivannan.sadhasivam@linaro.org>, <quic_mnaresh@quicinc.com>
Cc: <grant.jung@samsung.com>, <jt77.jang@samsung.com>,
<junwoo80.lee@samsung.com>, <jangsub.yi@samsung.com>,
<sh043.lee@samsung.com>, <cw9316.lee@samsung.com>,
<sh8267.baek@samsung.com>, <wkon.kim@samsung.com>
Subject: RE: [PATCH] scsi: ufs: core: increase the NOP_OUT command timeout
Date: Thu, 16 Jan 2025 18:59:40 +0900 [thread overview]
Message-ID: <425301db67fd$5c27ca60$14775f20$@samsung.com> (raw)
In-Reply-To: <DM6PR04MB6575C2833DD66B847572F53CFC1A2@DM6PR04MB6575.namprd04.prod.outlook.com>
>
> > It is found that is UFS device may take longer than 500ms(50ms *
> > 10times) to respond to NOP_OUT command.
> >
> > The NOP_OUT command timeout was total 500ms that is from a timeout
> > value of 50ms(defined by NOP_OUT_TIMEOUT) with 10 retries(defined by
> > NOP_OUT_RETRIES)
> >
> > This change increase the NOP_OUT command timeout to total 1000ms by
> > changing timeout value to 100ms(NOP_OUT_TIMEOUT)
> >
> > Signed-off-by: DooHyun Hwang <dh0421.hwang@samsung.com>
> Why not edit hba->nop_out_timeout in the .init vop?
> Like some vendors already do.
>
> Thanks,
> Avri
>
Thank you for your suggestion.
I'll fix that in .init vop as you said.
And I'll reject this patch.
BR,
Thank you.
DooHyun Hwang.
> > ---
> > drivers/ufs/core/ufshcd.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/ufs/core/ufshcd.c b/drivers/ufs/core/ufshcd.c
> > index cd404ade48dc..bf5c4620ef6b 100644
> > --- a/drivers/ufs/core/ufshcd.c
> > +++ b/drivers/ufs/core/ufshcd.c
> > @@ -57,8 +57,8 @@ enum {
> > };
> > /* NOP OUT retries waiting for NOP IN response */
> > #define NOP_OUT_RETRIES 10
> > -/* Timeout after 50 msecs if NOP OUT hangs without response */
> > -#define NOP_OUT_TIMEOUT 50 /* msecs */
> > +/* Timeout after 100 msecs if NOP OUT hangs without response */
> > +#define NOP_OUT_TIMEOUT 100 /* msecs */
> >
> > /* Query request retries */
> > #define QUERY_REQ_RETRIES 3
> > --
> > 2.48.0
> >
next prev parent reply other threads:[~2025-01-16 9:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250115022348epcas1p29705c109f51c01e1e91ef227233c7119@epcas1p2.samsung.com>
2025-01-15 2:23 ` [PATCH] scsi: ufs: core: increase the NOP_OUT command timeout DooHyun Hwang
2025-01-15 18:12 ` Bart Van Assche
2025-01-16 2:02 ` DooHyun Hwang(황두현/Device S/W Solution Lab.(MX)/삼성전자)
2025-01-16 14:58 ` Bart Van Assche
2025-01-16 8:38 ` Avri Altman
2025-01-16 9:59 ` DooHyun Hwang [this message]
2025-01-16 16:30 ` Bao D. Nguyen
2025-01-24 6:16 ` DooHyun Hwang
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='425301db67fd$5c27ca60$14775f20$@samsung.com' \
--to=dh0421.hwang@samsung.com \
--cc=Avri.Altman@wdc.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=bvanassche@acm.org \
--cc=cw9316.lee@samsung.com \
--cc=grant.jung@samsung.com \
--cc=jangsub.yi@samsung.com \
--cc=jt77.jang@samsung.com \
--cc=junwoo80.lee@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=martin.petersen@oracle.com \
--cc=peter.wang@mediatek.com \
--cc=quic_mnaresh@quicinc.com \
--cc=sh043.lee@samsung.com \
--cc=sh8267.baek@samsung.com \
--cc=wkon.kim@samsung.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).