public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Goel, Akash" <akash.goel@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: akash.goel@intel.com
Subject: Re: [PATCH 1/2] drm/i915: Correct the i915_frequency_info debugfs output
Date: Thu, 21 Apr 2016 13:07:19 +0530	[thread overview]
Message-ID: <5718832F.6030400@intel.com> (raw)
In-Reply-To: <20160421065438.GB15733@nuc-i3427.alporthouse.com>



On 4/21/2016 12:24 PM, Chris Wilson wrote:
> On Thu, Apr 21, 2016 at 12:33:40PM +0530, akash.goel@intel.com wrote:
>> From: Akash Goel <akash.goel@intel.com>
>>
>> There are certain registers, which captures the time elapsed in the
>> in current Up/Down EI, for how long GT has been Idle/Busy/Avg in the
>> current Up/Down EI and also in the previous Up/Down EI.
>> These register values are reported by the i915_frequency_info debugfs
>> interface. The Driver prints the 'us' suffix after the values, albeit
>> they are actually in raw form & not in microsecond units.
>> This patch removes the 'us' suffix so that its clear to User that values
>> are indeed in raw form.
>
> Or whilst you are here presenting them as both the raw value and as
> microseconds?

Ok, so need to present them in microseconds unit also (after platform 
specific conversion) apart from raw form.

Best Regards
Akash

> -Chris
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-04-21  7:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21  7:03 [PATCH 1/2] drm/i915: Correct the i915_frequency_info debugfs output akash.goel
2016-04-21  6:54 ` Chris Wilson
2016-04-21  7:37   ` Goel, Akash [this message]
2016-04-22 11:52     ` [PATCH 1/3] drm/i915: Macros to convert PM time interval values to microseconds akash.goel
2016-04-22 11:52       ` [PATCH v2 2/3] drm/i915: Correct the i915_frequency_info debugfs output akash.goel
2016-04-22 12:00         ` Chris Wilson
2016-04-22 11:52       ` [PATCH v2 3/3] drm/i915/bxt: Explicitly clear the Turbo control register akash.goel
2016-04-22 11:58       ` [PATCH 1/3] drm/i915: Macros to convert PM time interval values to microseconds Chris Wilson
2016-04-22 12:56       ` Daniel Vetter
2016-04-21  7:03 ` [PATCH 2/2] drm/i915/bxt: Explicitly clear the Turbo control register akash.goel
2016-04-21  7:37   ` Chris Wilson
2016-04-21  8:30     ` Goel, Akash
2016-04-21 15:27 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Correct the i915_frequency_info debugfs output Patchwork
2016-04-23 13:53 ` ✗ Fi.CI.BAT: warning " Patchwork

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=5718832F.6030400@intel.com \
    --to=akash.goel@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.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