<div dir="ltr"><br><div class="gmail_extra">On Thu, Jun 19, 2014 at 3:10 PM, Chris Healy <span dir="ltr"><<a href="mailto:cphealy@gmail.com" target="_blank">cphealy@gmail.com</a>></span> wrote:<br><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi Robert,<br><br></div>This information is helpful. I am able to query the frequencies as you mentioned. My primary interest though is in getting support added to intel_gpu_top. It seems to me that intel_gpu_top has been coded to support providing clock frequency data for a subset of Intel GPUs and that the mobile Ivy Bridge GT2 chipset is not supported. Would you agree with this? </div>
</blockquote><div><br>That looks right, yep.<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">If so, I'd like to fix this but don't know where to look for the bit descriptions for the necessary registers. Can you point me to the appropriate document?<br>
</div></blockquote><div><br></div><div>I'm afraid it looks like that the i915_debugfs.c code may be the best reference a.t.m; though maybe someone who's worked on that code (not me) can give you a better answer.<br>
<br></div><div>That said though; it could make sense to update intel_gpu_top to query debugfs for this information anyway; considering that it's more up to date and that way the logic doesn't need to be duplicated. For example if you take a look at overlay/gpu-freq.c in the intel_gpu_tools repo it looks like there's already some precedent for doing just that. It also looks like the utility code in overlay/debugfs.c can be used to make sure debugfs is mounted.<br>
<br></div><div>Sorry I couldn't point you at good documentation for this; but hopefully that's still of some help to you.<br><br>--<br></div><div>Regards,<br></div><div>Robert<br></div><div><br><br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<br>Regards,<br><br>Chris <br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 17, 2014 at 7:43 PM, Bragg, Robert <span dir="ltr"><<a href="mailto:robert.bragg@intel.com" target="_blank">robert.bragg@intel.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi Chris,<br><br></div><div>You can query the nominal and maximum frequency of your GPU via debugfs, in case that is good enough for your needs. Depending on what kernel version you have you can try to cat /sys/kernel/debug/dri/0/i915_cur_delayinfo or with more recent versions, /sys/kernel/debug/dri/0/i915_frequency_info<br>
<br></div><div>If you are curious about more details then it may be best to look at the drm driver code in drivers/gpu/drm/i915/i915_debugfs.c:i915_frequency_info().<br></div><br>--<br></div>Regards,<br></div>Robert<br><div>
<div><div><div><div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Wed, Jun 18, 2014 at 1:55 AM, He, Shuang <span dir="ltr"><<a href="mailto:shuang.he@intel.com" target="_blank">shuang.he@intel.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div>
<div link="#0563C1" vlink="#954F72" lang="ZH-CN">
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)" lang="EN-US">Hi, Chris<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)" lang="EN-US"> Let’s put you to the correct Mailing list for this topic first<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)" lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)" lang="EN-US">Thanks<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)" lang="EN-US"> --Shuang<u></u><u></u></span></p>
<div style="border-width:medium medium medium 1.5pt;border-style:none none none solid;border-color:-moz-use-text-color -moz-use-text-color -moz-use-text-color blue;padding:0cm 0cm 0cm 4pt">
<div>
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(225,225,225) -moz-use-text-color -moz-use-text-color;padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:11pt;font-family:"Calibri","sans-serif"" lang="EN-US">From:</span></b><span style="font-size:11pt;font-family:"Calibri","sans-serif"" lang="EN-US"> Chris Healy [mailto:<a href="mailto:cphealy@gmail.com" target="_blank">cphealy@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, June 18, 2014 1:15 AM<br>
<b>To:</b> Eric Anholt; He, Shuang<br>
<b>Subject:</b> intel_gpu_top missing clocks<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt"><span lang="EN-US">Eric, Shuang,<u></u><u></u></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12pt"><span lang="EN-US">I couldn't find an appropriate mailing list to report this on, so I'm mailing the two of you as you've both touched the clock code in intel_gpu_top.<u></u><u></u></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12pt"><span lang="EN-US">I'm running an Ivy Bridge Mobile chipset and trying to use intel_gpu_top and intel_stepping to see the GPU clock frequencies. In both cases, the clocks are "unknown".<br>
<br>
When I look at the code, it seems that there's just no code path to handle this devid, though I'm not sure as I'm not very good at understanding code. I see in intel_chipset.h that device id 0x0166 = PCI_CHIP_IVYBRIDGE_M_GT2 and that none of the "if's" in
print_clock_info ultimately point to this device type.<u></u><u></u></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12pt"><span lang="EN-US">Do either of you know why this would be? Is it just a case of coding for the majority of chipset configurations?<u></u><u></u></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12pt"><span lang="EN-US">If it's just the case of it not yet being handled, I'd be open to trying to add support for it if you could point me to the necessary chip documentation.<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US">Regards,<br>
<br>
Chris<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<br></div></div>_______________________________________________<br>
Intel-gfx mailing list<br>
<a href="mailto:Intel-gfx@lists.freedesktop.org" target="_blank">Intel-gfx@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/intel-gfx" target="_blank">http://lists.freedesktop.org/mailman/listinfo/intel-gfx</a><br>
<br></blockquote></div><br></div></div></div></div></div></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>