mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
	bskeggs@redhat.com, Greg KH <greg@kroah.com>,
	acourbot@nvidia.com, airlied@linux.ie,
	dri-devel@lists.freedesktop.org
Subject: unparseable, undocumented /sys/class/drm/.../pstate
Date: Sat, 21 Jun 2014 20:02:01 +0200	[thread overview]
Message-ID: <20140621180201.GA4621@amd.pavel.ucw.cz> (raw)

Hi!

AFAICT, pstate file will contain something like

07: core 100 MHz memory 123 MHz *
08: core 100-200 MHz memory 123 MHz

...which does not look exactly like one-value-per-file, and I'm pretty
sure userspace will get it wrong if it tries to parse it. Plus, I
don't see required documentation in Documentation/ABI.

Should we disable it for now, so that userspace does not start
depending on it and we'll not have to maintain it forever?

I guess better interface would be something like

pstate/07/core_clock_min
          core_clock_max
	  memory_clock_min
	  memory_clock_max

and then pstate/active containing just the number of active state?

Thanks,
								Pavel

PS: I have no nvidia, got the news at

http://www.phoronix.com/scan.php?page=article&item=nouveau_try_linux316&num=2
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

             reply	other threads:[~2014-06-21 18:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-21 18:02 Pavel Machek [this message]
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
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=20140621180201.GA4621@amd.pavel.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=acourbot@nvidia.com \
    --cc=airlied@linux.ie \
    --cc=bskeggs@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    /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
all inboxes | Powered by JetHome®