From: "Kiwoong Kim" <kwmad.kim@samsung.com>
To: "'Avri Altman'" <Avri.Altman@wdc.com>,
<linux-scsi@vger.kernel.org>, <sc.suh@samsung.com>,
<hy50.seo@samsung.com>, <sh425.lee@samsung.com>,
<kwangwon.min@samsung.com>
Subject: RE: [RFC PATCH v1] ufs: poll HCS.UCRDY before issuing a UIC command
Date: Tue, 16 May 2023 12:30:28 +0900 [thread overview]
Message-ID: <012e01d987a6$c2d83350$488899f0$@samsung.com> (raw)
In-Reply-To: <DM6PR04MB6575DFEBFBE75610D9613220FC779@DM6PR04MB6575.namprd04.prod.outlook.com>
> > With auto hibern8 enabled, UIC could be working for a while to process
> > a hibern8 operation and HCI reports UIC not ready for a short term
> > through HCS.UCRDY.
> > And UFS driver can't recognize the operation.
> > UFSHCI spec specifies UCRDY like this:
> > whether the host controller is ready to process UIC COMMAND
> >
> > The 'ready' could be seen as many different meanings. If the meaning
> > includes not processing any request from HCI, processing a hibern8
> > operation can be 'not ready'. In this situation, the driver needs to
> > wait until the operations is completed.
> >
> > Signed-off-by: Kiwoong Kim <kwmad.kim@samsung.com>
> Is this replaces your previous suggestion -
> https://lore.kernel.org/lkml/1682385635-43601-1-git-send-email-
> kwmad.kim@samsung.com/
> Or is it addressing another issue?
>
> Thanks,
> Avri
>
No, they are different. This is about reporting UIC ready and what you mentioned
is about reporting UIC busy in a certain race condition.
next prev parent reply other threads:[~2023-05-16 3:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230509083312epcas2p375f77d18a9026f7d263750baf9c9a5bb@epcas2p3.samsung.com>
2023-05-09 8:24 ` [RFC PATCH v1] ufs: poll HCS.UCRDY before issuing a UIC command Kiwoong Kim
2023-05-10 10:14 ` Avri Altman
2023-05-16 3:30 ` Kiwoong Kim [this message]
2023-05-10 18:53 ` Bart Van Assche
2023-05-10 21:24 ` Bao D. Nguyen
2023-05-10 21:46 ` Bart Van Assche
2023-05-10 23:35 ` Kiwoong Kim
2023-05-16 3:28 ` Kiwoong Kim
2023-05-11 5:22 ` Adrian Hunter
2023-05-12 0:56 ` Kiwoong Kim
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='012e01d987a6$c2d83350$488899f0$@samsung.com' \
--to=kwmad.kim@samsung.com \
--cc=Avri.Altman@wdc.com \
--cc=hy50.seo@samsung.com \
--cc=kwangwon.min@samsung.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sc.suh@samsung.com \
--cc=sh425.lee@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