From: Greg KH <greg@kroah.com>
To: Martin Peres <martin.peres@free.fr>
Cc: Ilia Mirkin <imirkin@alum.mit.edu>,
kernel list <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Ben Skeggs <bskeggs@redhat.com>, Pavel Machek <pavel@ucw.cz>
Subject: Re: unparseable, undocumented /sys/class/drm/.../pstate
Date: Mon, 23 Jun 2014 14:09:37 -0400 [thread overview]
Message-ID: <20140623180937.GB29494@kroah.com> (raw)
In-Reply-To: <53A867DB.90604@free.fr>
On Mon, Jun 23, 2014 at 07:46:03PM +0200, Martin Peres wrote:
> Le 23/06/2014 18:40, Ilia Mirkin a écrit :
> >On Mon, Jun 23, 2014 at 12:36 PM, Greg KH <greg@kroah.com> wrote:
> >>On Mon, Jun 23, 2014 at 12:18:51PM -0400, Ilia Mirkin wrote:
> >>A list of valid "values" that a file can be in is fine if you just then
> >>write one value back to that file. That's the one exception, but a
> >>minor one given the huge number of sysfs files. Other than that, if you
> >
> >Which is pretty much what the pstate file is. Would it make things
> >better if we removed the descriptive info while leaving the pstate
> >file in place?
>
> This means we should also create a new sysfs file per performance level too,
> right? Is there another way for a driver to expose a list in sysfs?
What exactly are you wanting to export to userspace? What will
userspace do with this information? Why export anything at all?
Start with defining that, and go from there.
thanks,
greg k-h
next prev parent reply other threads:[~2014-06-23 18:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-21 18:02 unparseable, undocumented /sys/class/drm/.../pstate Pavel Machek
2014-06-21 18:22 ` Ilia Mirkin
2014-06-21 18:50 ` Pavel Machek
2014-06-21 19:34 ` Ilia Mirkin
2014-06-21 19:45 ` Greg KH
2014-06-23 2:12 ` Ilia Mirkin
2014-06-23 13:02 ` Pavel Machek
2014-06-23 13:29 ` Ilia Mirkin
2014-06-23 20:15 ` Pavel Machek
2014-06-23 20:18 ` Ilia Mirkin
2014-06-23 20:26 ` Greg KH
2014-06-23 20:32 ` Ilia Mirkin
2014-06-24 0:06 ` Ben Skeggs
2014-06-24 16:00 ` Greg KH
2014-06-23 16:07 ` Greg KH
2014-06-23 16:18 ` Ilia Mirkin
2014-06-23 16:36 ` Greg KH
2014-06-23 16:40 ` Ilia Mirkin
2014-06-23 17:46 ` Martin Peres
2014-06-23 17:56 ` Ilia Mirkin
2014-06-23 18:00 ` Martin Peres
2014-06-23 18:05 ` Ilia Mirkin
2014-06-23 18:09 ` Greg KH [this message]
2014-06-23 18:08 ` Greg KH
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=20140623180937.GB29494@kroah.com \
--to=greg@kroah.com \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imirkin@alum.mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.peres@free.fr \
--cc=pavel@ucw.cz \
/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