Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: deepak.s@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/vlv: Add VLV specific force wake routines.
Date: Tue, 19 Nov 2013 10:05:41 -0800	[thread overview]
Message-ID: <20131119100541.5ece956a@jbarnes-desktop> (raw)
In-Reply-To: <1384435935-13571-1-git-send-email-deepak.s@intel.com>

On Thu, 14 Nov 2013 19:02:15 +0530
deepak.s@intel.com wrote:

> From: Deepak S <deepak.s@intel.com>
> 
> Added media/render/common well VLV force wake routines to help
> bring up the WELLS before access the register
> - Refactor current vlv_forcewake get/put and added MEDIA or
>   RENDER specific Forcewake.
> - Added VLV Check to bring up MEDIA and RENDER WELL base
>   on the register accessed in vlv_read##x (in intel_uncore.c)

This patch is pretty big and so a bit hard to review.  A couple of
questions:
  - why not use the callback to __vlv_force_wake_* from
    gen6_gt_force_wake_*?  i.e. why is VLV special here?
  - having a new gen7_media_force_wake function may be better than
    passing an engine around, and would touch fewer pieces of code
  - have you done measurements on this?  given how infrequently we
    ought to be waking the wells when they're idle, and how long we
    generally keep them awake, is this a real power win?

Thanks,
Jesse

  reply	other threads:[~2013-11-19 18:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-14 13:32 [PATCH] drm/i915/vlv: Add VLV specific force wake routines deepak.s
2013-11-19 18:05 ` Jesse Barnes [this message]
2013-11-20  6:00   ` S, Deepak
2013-11-20 16:05     ` Jesse Barnes
2013-11-20 16:33       ` S, Deepak
2013-11-22 21:12         ` Jesse Barnes
2013-11-23  4:56           ` S, Deepak
2013-11-20 16:16     ` Daniel Vetter

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=20131119100541.5ece956a@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=deepak.s@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox