[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <de7a1d36-cfb7-4db0-716e-e79dd93b6852@acm.org>
Date: Tue, 6 Sep 2022 10:53:46 -0700
From: Bart Van Assche <bvanassche@....org>
To: Daniil Lunev <dlunev@...omium.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Alim Akhtar <alim.akhtar@...sung.com>,
Avri Altman <avri.altman@....com>,
Bean Huo <beanhuo@...ron.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
Keoseong Park <keosung.park@...sung.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
Sohaib Mohamed <sohaib.amhmd@...il.com>,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH v8] ufs: core: print UFSHCD capabilities in controller's
sysfs node
On 8/28/22 15:18, Daniil Lunev wrote:
> Userspace may want to manually control when the data should go into
> WriteBooster buffer. The control happens via "wb_on" node, but
> presently, there is no simple way to check if WriteBooster is supported
> and enabled. This change exposes the Write Booster and Clock Scaling
> capabilities to be able to determin if the Write Booster is available
> and if its manual control is blocked by Clock Scaling mechanism.
determin -> determine?
Anyway:
Reviewed-by: Bart Van Assche <bvanassche@....org>
Powered by blists - more mailing lists