intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: turbo & RC6 support for VLV v6
Date: Fri, 12 Apr 2013 13:18:32 -0700	[thread overview]
Message-ID: <20130412201832.GC27716@bwidawsk.net> (raw)
In-Reply-To: <1365789045-25509-2-git-send-email-jbarnes@virtuousgeek.org>

On Fri, Apr 12, 2013 at 10:50:45AM -0700, Jesse Barnes wrote:
> Uses slightly different interfaces than other platforms.
> 
> v2: track actual set freq, not requested (Rohit)
>     fix debug prints in init code (Jesse)
> v3: don't write sleep reg (Jesse)
>     re-add RC6 wake limit write (Ben)
>     fixup thresholds to match other platforms (Ben)
>     clean up mem freq calculation (Ben)
>     clean up debug prints (Ben)
> v4: move defines from punit patch (Ville)
> v5: remove writes to nonexistent regs (Jesse)
>     put RP and RC regs together (Jesse)
>     fix RC6 enable (Jesse)
> v6: use correct fuse reads from NC (Jesse)
>     split out min/max funcs for use in sysfs (Jesse)
>     add debugfs & sysfs freq controls (Jesse)
> 
> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>

I didn't stare too intently since I had reviewed v4, nothing stood out
immediately though, so: 
Reviewed-by: Ben Widawsky <ben@bwidawsk.net>

[snip]
-- 
Ben Widawsky, Intel Open Source Technology Center

  reply	other threads:[~2013-04-12 20:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12 17:50 [PATCH 1/2] drm/i915: VLV GPU frequency to opcode functions Jesse Barnes
2013-04-12 17:50 ` [PATCH 2/2] drm/i915: turbo & RC6 support for VLV v6 Jesse Barnes
2013-04-12 20:18   ` Ben Widawsky [this message]
2013-04-12 19:03 ` [PATCH 1/2] drm/i915: VLV GPU frequency to opcode functions Ben Widawsky

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=20130412201832.GC27716@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.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;
as well as URLs for NNTP newsgroup(s).