From: "Kiwoong Kim" <kwmad.kim@samsung.com>
To: "'Avri Altman'" <Avri.Altman@wdc.com>,
<linux-scsi@vger.kernel.org>, <alim.akhtar@samsung.com>,
<jejb@linux.ibm.com>, <martin.petersen@oracle.com>,
<beanhuo@micron.com>, <asutoshd@codeaurora.org>,
<cang@codeaurora.org>, <bvanassche@acm.org>,
<grant.jung@samsung.com>, <sc.suh@samsung.com>,
<hy50.seo@samsung.com>, <sh425.lee@samsung.com>
Subject: RE: [PATCH v2 0/2] skipping manual flush for write booster
Date: Tue, 25 Aug 2020 10:59:55 +0900 [thread overview]
Message-ID: <000401d67a83$6e52e880$4af8b980$@samsung.com> (raw)
In-Reply-To: <BY5PR04MB6705C3DCE1EC1BE863D7406DFC560@BY5PR04MB6705.namprd04.prod.outlook.com>
> > v2 -> v1: enable the quirk in exynos
> >
> > We have two knobs to flush for write booster, i.e.
> > fWriteBoosterEn, fWriteBoosterBufferFlushEn.
> fWriteBoosterBufferFlushDuringHibernate and fWriteBoosterBufferFlushEn.
>
> > However, many product makers uses only fWriteBoosterBufferFlushEn,
> Uses only fWriteBoosterBufferFlushDuringHibernate
> > because this can reportedly cover most scenarios and there have been
> > some reports that flush by fWriteBoosterEn could
> flush by fWriteBoosterBufferFlushEn could
>
> > lead raise power consumption thanks to unexpected internal
> lead to a raise
>
> > operations. So we need a way to enable or disable fWriteBoosterEn.
> operations. For those case, this quirk will allow to avoid manual flush.
It was my mistake and I'll be more careful when writing messages.
Thanks.
Kiwoong Kim
prev parent reply other threads:[~2020-08-25 2:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200824023811epcas2p4915326d30728acff0a721043706e1f3b@epcas2p4.samsung.com>
2020-08-24 2:29 ` [PATCH v2 0/2] skipping manual flush for write booster Kiwoong Kim
2020-08-24 2:29 ` [PATCH v2 1/2] ufs: introduce skipping manual flush for wb Kiwoong Kim
2020-08-24 6:49 ` Avri Altman
2020-08-24 2:29 ` [PATCH v2 2/2] ufs: exynos: enable UFSHCI_QUIRK_SKIP_MANUAL_WB_FLUSH_CTRL Kiwoong Kim
2020-08-24 6:50 ` Avri Altman
2020-08-24 6:46 ` [PATCH v2 0/2] skipping manual flush for write booster Avri Altman
2020-08-25 1:59 ` Kiwoong Kim [this message]
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='000401d67a83$6e52e880$4af8b980$@samsung.com' \
--to=kwmad.kim@samsung.com \
--cc=Avri.Altman@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=grant.jung@samsung.com \
--cc=hy50.seo@samsung.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--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