Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org,
	Ben Widawsky <benjamin.widawsky@intel.com>
Subject: Re: [PATCH] drm/i915: IS_GEN6 && IS_GEN7 - is unpossible
Date: Sat, 7 Apr 2012 13:58:11 -0700	[thread overview]
Message-ID: <20120407135811.2ff0d99d@bwidawsk.net> (raw)
In-Reply-To: <60a83a21-3cdd-4005-9f0c-ede909955bef@email.android.com>

On Sat, 07 Apr 2012 13:48:30 -0700
Jesse Barnes <jbarnes@virtuousgeek.org> wrote:

> Ben Widawsky <ben@bwidawsk.net> wrote:
> 
> >Imagine my surprise when tracking something down, I bisected to a VLV
> >commit.
> >
> >CC: Jesse Barnes <jbarnes@virtuousgeek.org>
> >Signed-off-by: Ben Widawsky <benjamin.widawsky@intel.com>
> >---
> > drivers/gpu/drm/i915/intel_display.c |    2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >diff --git a/drivers/gpu/drm/i915/intel_display.c
> >b/drivers/gpu/drm/i915/intel_display.c
> >index 3abebb5..2ce1763 100644
> >--- a/drivers/gpu/drm/i915/intel_display.c
> >+++ b/drivers/gpu/drm/i915/intel_display.c
> >@@ -9537,7 +9537,7 @@ void intel_modeset_init(struct drm_device *dev)
> > 		intel_init_emon(dev);
> > 	}
> > 
> >-	if ((IS_GEN6(dev) && IS_GEN7(dev)) && !IS_VALLEYVIEW(dev)) {
> >+	if ((IS_GEN6(dev) || IS_GEN7(dev)) && !IS_VALLEYVIEW(dev)) {
> > 		gen6_enable_rps(dev_priv);
> > 		gen6_update_ring_freq(dev_priv);
> > 	}
> >-- 
> >1.7.10
> 
> Daniel caught that one too, maybe he hasn't pushed the fix? 

Seems it hasn't been pushed, and I missed the exchange about the issue.
As long as it's known already...`

  reply	other threads:[~2012-04-07 20:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-07 20:27 [PATCH] drm/i915: IS_GEN6 && IS_GEN7 - is unpossible Ben Widawsky
2012-04-07 20:48 ` Jesse Barnes
2012-04-07 20:58   ` Ben Widawsky [this message]
2012-04-09 16:02     ` Daniel Vetter
2012-04-09 16:55       ` Jesse Barnes

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=20120407135811.2ff0d99d@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=benjamin.widawsky@intel.com \
    --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