Message ID | cover.1598236010.git.kwmad.kim@samsung.com (mailing list archive) |
---|---|
Headers | show |
Series | skipping manual flush for write booster | expand |
> > 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.
> > 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