From: Daniil Lunev <dlunev@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Bart Van Assche <bvanassche@acm.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>, Bean Huo <beanhuo@micron.com>,
Daejun Park <daejun7.park@samsung.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Sohaib Mohamed <sohaib.amhmd@gmail.com>,
Stanley Chu <stanley.chu@mediatek.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH v2] ufs: core: print capabilities in controller's sysfs node
Date: Fri, 29 Jul 2022 17:47:46 +1000 [thread overview]
Message-ID: <CAONX=-eCX=n_JxHFTPHzLv+eaPpVs+Eqn+RF04FTdFgQzizC7w@mail.gmail.com> (raw)
In-Reply-To: <YuOKNX4mWCb1LUrg@kroah.com>
> Yeah, that's not ok, where are these bits coming from
There has been a few more iterations on the patch, in the latest state only
Clock Scaling and Write Booster are exposed as individual nodes.
> what userspace tools will be using them?
In ChromeOS we want to explicitly control WriteBooster state, but for that
the user space needs to know when it is supported but off, and when it is
not supported at all. On top of it, Clock Scaling complicates the story since
it disables the control via wb_on node. That is something I need to figure
out separately.
--Daniil
prev parent reply other threads:[~2022-07-29 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 23:05 [PATCH v2] ufs: core: print capabilities in controller's sysfs node Daniil Lunev
2022-07-28 23:23 ` Bart Van Assche
2022-07-29 7:20 ` Greg Kroah-Hartman
2022-07-29 7:47 ` Daniil Lunev [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='CAONX=-eCX=n_JxHFTPHzLv+eaPpVs+Eqn+RF04FTdFgQzizC7w@mail.gmail.com' \
--to=dlunev@chromium.org \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=daejun7.park@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mchehab+huawei@kernel.org \
--cc=sohaib.amhmd@gmail.com \
--cc=stanley.chu@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.