From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Jason Stubbs <jasonbstubbs@gmail.com>
Cc: Keith Packard <keithp@keithp.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915: fix regression after clock gating init split
Date: Tue, 31 May 2011 09:58:23 -0700 [thread overview]
Message-ID: <20110531095823.4af74109@jbarnes-desktop> (raw)
In-Reply-To: <201105281426.49040.jasonbstubbs@gmail.com>
On Sat, 28 May 2011 14:26:48 +1000
Jason Stubbs <jasonbstubbs@gmail.com> wrote:
> From: Jason Stubbs <jasonbstubbs@gmail.com>
>
> During the refactoring in revision 6067aaeadb5b3df26f27ac827256b1ef01e674f5,
> the intel_enable_clock_gating was split up into several functions that are
> then called indirectly. However, which function to call was not specified for
> the IS_PINEVIEW() case. This patch specifies the correct gating function.
>
> Signed-off-by: Jason Stubbs <jasonbstubbs@gmail.com>
> ---
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index f553ddf..bb1b59b 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -7675,6 +7675,7 @@ static void intel_init_display(struct drm_device *dev)
> dev_priv->display.update_wm = NULL;
> } else
> dev_priv->display.update_wm = pineview_update_wm;
> + dev_priv->display.init_clock_gating = gen3_init_clock_gating;
> } else if (IS_G4X(dev)) {
> dev_priv->display.update_wm = g4x_update_wm;
> dev_priv->display.init_clock_gating = g4x_init_clock_gating;
>
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2011-05-31 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 13:44 Jason Stubbs
2011-05-27 19:44 ` Keith Packard
2011-05-28 4:26 ` Jason Stubbs
2011-05-31 16:57 ` Jesse Barnes
2011-05-28 4:26 ` Jason Stubbs
2011-05-31 16:58 ` Jesse Barnes [this message]
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=20110531095823.4af74109@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=jasonbstubbs@gmail.com \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®