lkml.org 
[lkml]   [2014]   [Jun]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subjectunparseable, undocumented /sys/class/drm/.../pstate
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


\
 
 \ /
  Last update: 2014-06-21 20:41    [W:0.064 / U:4.132 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site