All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eugeni Dodonov <eugeni.dodonov@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Ben Widawsky <ben@bwidawsk.net>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: expose energy counter on SNB and IVB
Date: Sun, 24 Jun 2012 20:13:28 -0300	[thread overview]
Message-ID: <4FE79F18.9090705@linux.intel.com> (raw)
In-Reply-To: <20120624100124.GA5087@phenom.ffwll.local>

On 06/24/2012 07:01 AM, Daniel Vetter wrote:
> On Fri, Jun 22, 2012 at 07:04:29PM -0700, Ben Widawsky wrote:
>> On Wed, 20 Jun 2012 14:48:58 -0700
>> Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
>>> +static struct attribute *gt_attrs[] = {
>>> +	&dev_attr_gt_energy_uJ.attr,
>>> +	NULL,
>>> +};
>>
>> I think convention dictates it should be all lowercase. And while on
>> that, gt_energy_uJ is about as descriptive a name as rc6 (what jerk
>> named that anyway?). I think something like consumed_microjoules is
>> better.
> 
> I admit that the uJ makes tons of sense for me - J is the official SI
> abbrev. for joules (I'm a bit unsure about u for \mu, but it seems to be
> customary). Adding consumed makes some sense I think, but otherwise it's
> imo good if we stick with the names vpg ppl have come up. So
> gt_consumed_energy_uJ anyone? I can bikeshed this name while applying ...
> -Daniel

<bikeshed>
I'd vote for gt_energy or gt_consumed_energy, which would provide
results in plain J instead of mJ or uJ. This would result in a smaller
name + power readings which are standardized.
</bikeshed>

But if we settle on uJ values, gt_consumed_energy_uJ seems to be more
self-explainable to me.

Eugeni

  reply	other threads:[~2012-06-24 23:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 21:48 [PATCH] drm/i915: expose energy counter on SNB and IVB Jesse Barnes
2012-06-23  2:04 ` Ben Widawsky
2012-06-24 10:01   ` Daniel Vetter
2012-06-24 23:13     ` Eugeni Dodonov [this message]
2012-06-24 23:06 ` Eugeni Dodonov

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=4FE79F18.9090705@linux.intel.com \
    --to=eugeni.dodonov@linux.intel.com \
    --cc=ben@bwidawsk.net \
    --cc=daniel@ffwll.ch \
    --cc=eugeni.dodonov@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.