From: Bean Huo <huobean@gmail.com>
To: 高严凯 <gaoyankaigeren@gmail.com>
Cc: Avri Altman <Avri.Altman@wdc.com>,
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: Fri, 14 Oct 2022 07:48:34 +0200 [thread overview]
Message-ID: <8678f69aa94003b357c4c8ef42cd6ce5c7487f8d.camel@gmail.com> (raw)
In-Reply-To: <CAFN68yVdwrECaDvNuok_4V-54UZUJU9+dn5icaiPdj6BXEZuVA@mail.gmail.com>
On Fri, 2022-10-14 at 10:44 +0800, 高严凯 wrote:
> " UFSHCI has idle time before bringing Link into hibern8 mode, " I
> think ufs put the link to h8 during the time
no, it is ufs controller. see the ufshci spec:
"Auto-Hibern8 Idle Timer Value (AH8ITV): This is the timer that UFS
subsystem must be idle before UFS host *controller* may put UniPro link
into Hibernate state autonomously. The idle timer value is multiplied
by the indicated timer scale to yield an absolute timer value. ....
...
Any non-zero value will enable Auto-Hibernate idle timer.
UFS host controller shall put Unipro link out of Hibernate state when
the link communication is required. The mechanism to decide when the
Unipro link needs to become active is host controller specific
implementation, and is transparent to the software."
next prev parent reply other threads:[~2022-10-14 5:48 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
2022-10-14 2:44 ` 高严凯
2022-10-14 5:48 ` Bean Huo [this message]
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=8678f69aa94003b357c4c8ef42cd6ce5c7487f8d.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