> The general opinion appears to be "communicating the least possible". In > my opinion this means we shouldn't communicate shader speeds, voltages > and fan speeds. Assuming each GPU clock speed is unique (eg. not 2 equal > GPU speeds with different memory clock speeds) we could even suffice > with just the GPU speed (like scaling_available_frequencies in CPUFreq). > This can be done, as said, like cpufreq in sysfs. When GPU is not > unique, it's also possible to communicate those separated by a slash > ("135/150") or anything. Any other thoughts on this, either from Nouveau > or Radeon/Intel developers?
W.r.t showing the current state, I don't have much opinion. But w.r.t what can be changed via sysfs, I agree there should just be very few settings: performance and powersave (where I'd expect powersave to use an ondemand strategy since it's usually the most efficient power-wise, tho if needed we could have an extra one for "ondemand"). Stefan ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel