From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: don't check for i830 in vlv specific code
Date: Fri, 22 Aug 2014 15:44:30 +0300 [thread overview]
Message-ID: <20140822124430.GV4193@intel.com> (raw)
In-Reply-To: <1408709195-21974-1-git-send-email-jani.nikula@intel.com>
On Fri, Aug 22, 2014 at 03:06:35PM +0300, Jani Nikula wrote:
> Signed-off-by: Jani Nikula <jani.nikula@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 51b4cd29f932..83eabd758ed9 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -1546,7 +1546,7 @@ static void vlv_enable_pll(struct intel_crtc *crtc)
> BUG_ON(!IS_VALLEYVIEW(dev_priv->dev));
>
> /* PLL is protected by panel, make sure we can write it */
> - if (IS_MOBILE(dev_priv->dev) && !IS_I830(dev_priv->dev))
> + if (IS_MOBILE(dev_priv->dev))
> assert_panel_unlocked(dev_priv, crtc->pipe);
My gut feeling is that the IS_MOBILE check could also be dropped. Not
quite sure though since VLV_D is not mentioned anywhere in the docs
AFAICS.
Anyway dropping the 830 check definitely makes sense so:
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> I915_WRITE(reg, dpll);
> --
> 1.9.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-08-22 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 12:06 [PATCH] drm/i915: don't check for i830 in vlv specific code Jani Nikula
2014-08-22 12:44 ` Ville Syrjälä [this message]
2014-08-26 6:48 ` Daniel Vetter
[not found] ` <32504_1408711479_53F73B37_32504_3103_1_20140822124430.GV4193@intel.com>
2014-08-25 13:13 ` Ping: Status of the i830 code? Thomas Richter
2014-08-26 6:49 ` 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=20140822124430.GV4193@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
/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.