[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YuOKNX4mWCb1LUrg@kroah.com>
Date: Fri, 29 Jul 2022 09:20:21 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Bart Van Assche <bvanassche@....org>
Cc: Daniil Lunev <dlunev@...omium.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Alim Akhtar <alim.akhtar@...sung.com>,
Avri Altman <avri.altman@....com>,
Bean Huo <beanhuo@...ron.com>,
Daejun Park <daejun7.park@...sung.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
Sohaib Mohamed <sohaib.amhmd@...il.com>,
Stanley Chu <stanley.chu@...iatek.com>,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH v2] ufs: core: print capabilities in controller's sysfs
node
On Thu, Jul 28, 2022 at 04:23:16PM -0700, Bart Van Assche wrote:
> On 7/28/22 16:05, Daniil Lunev wrote:
> > +What: /sys/bus/platform/drivers/ufshcd/*/caps
> > +What: /sys/bus/platform/devices/*.ufs/caps
> > +Date: July 2022
> > +Contact: Daniil Lunev <dlunev@...omium.org>
> > +Description: Read-only attribute. Enabled capabilities of the UFS driver. The
> > + enabled capabilities are determined by what is supported by the
> > + host controller and the UFS device.
> > + Format: 0x%08llx
>
> This documentation is useless since the meaning of the individual bits has
> not been documented.
Yeah, that's not ok, where are these bits coming from and what userspace
tools will be using them?
thanks,
greg k-h
Powered by blists - more mailing lists