From: Bean Huo <huobean@gmail.com>
To: 高严凯 <gaoyankaigeren@gmail.com>, "Avri Altman" <Avri.Altman@wdc.com>
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
Bart Van Assche <bvanassche@acm.org>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
Bean Huo <beanhuo@micron.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ufs: core: Disable auto h8 before ssu
Date: Wed, 12 Oct 2022 16:25:17 +0200 [thread overview]
Message-ID: <bee1807b7d072b221c44ac8c2ed8064939d33696.camel@gmail.com> (raw)
In-Reply-To: <CAFN68yVajOkV++gCp-y1+SD5VOKLgUeBhfgskrJZOX5dfGi07A@mail.gmail.com>
On Tue, 2022-10-11 at 19:53 +0800, 高严凯 wrote:
> Dear Avri
> Unisoc reports resume fail on UFS(micron FS164) during
> suspend/resume test.
> We check host inserts auto H8 enter/exit event between SSU sleep
> command and H8 enter command in runtime suspend .
> Asfollows: SSU Sleep command --> auto H8 enter --> auto H8 exit -->
> H8 enter --> idle 2ms --> VCC off.
> However device AQL FW can’t enter LPM within 2ms after second H8
> enter command.
> FW already enter LPM after receive auto H8 enter command , Next
> auto
> H8 exit command will trigger FW exit from LPM, it need take over
> 10ms,
> and FW can’t enter
> LPM again after second H8 enter command until device complete exit
> from LPM. So disable auto h8 before ssu is a reasonable solution to
> solve it.
> Hynix also has similar request.
Hi gaoyan,
The above sequence confuses me. UFSHCI has idle time before bringing
Link into hibern8 mode, do you know what the settings are?
Also, if auto-hibern8 is supported, in this case, the host-side SW
should not send manual hibern8. If this is an issue to all UFS or
UFSHCI, we should disable manual hibern8 if auto-hibern8 is enabled. or
let customer to choose one of two.
Kind regards,
Bean
next prev parent reply other threads:[~2022-10-12 14:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 2:16 Ten Gao
2022-10-11 3:39 ` kernel test robot
2022-10-11 7:07 ` Avri Altman
2022-10-11 11:53 ` 高严凯
2022-10-12 6:28 ` Avri Altman
2022-10-12 8:12 ` Avri Altman
2022-10-12 8:49 ` 高严凯
2022-10-12 14:25 ` Bean Huo [this message]
2022-10-14 2:44 ` 高严凯
2022-10-14 5:48 ` Bean Huo
2022-10-14 10:15 ` 高严凯
2022-10-20 5:15 ` 高严凯
2022-10-20 17:47 ` Bart Van Assche
2022-10-11 9:59 ` kernel test robot
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=bee1807b7d072b221c44ac8c2ed8064939d33696.camel@gmail.com \
--to=huobean@gmail.com \
--cc=Avri.Altman@wdc.com \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=gaoyankaigeren@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.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
Powered by JetHome