From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Populate primary_disabled in intel_modeset_readout_hw_state()
Date: Thu, 10 Oct 2013 11:27:58 +0300 [thread overview]
Message-ID: <20131010082758.GG13047@intel.com> (raw)
In-Reply-To: <1381328698-5924-1-git-send-email-ville.syrjala@linux.intel.com>
On Wed, Oct 09, 2013 at 05:24:57PM +0300, ville.syrjala@linux.intel.com wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Make sure our primary_disabled matches our expectations after driver
> init.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=70270
> Tested-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Also
Tested-by: shui yangwei <yangweix.shui@intel.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 1816c46..debbd06 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -10702,6 +10702,7 @@ static void intel_modeset_readout_hw_state(struct drm_device *dev)
> &crtc->config);
>
> crtc->base.enabled = crtc->active;
> + crtc->primary_disabled = !crtc->active;
>
> DRM_DEBUG_KMS("[CRTC:%d] hw state readout: %s\n",
> crtc->base.base.id,
> --
> 1.8.1.5
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
prev parent reply other threads:[~2013-10-10 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 14:24 [PATCH 1/2] drm/i915: Populate primary_disabled in intel_modeset_readout_hw_state() ville.syrjala
2013-10-09 14:24 ` [PATCH 2/2] drm/i915: Rename primary_disabled to primary_enabled ville.syrjala
2013-10-10 8:35 ` Jani Nikula
2013-10-10 8:57 ` Daniel Vetter
2013-10-10 8:27 ` Ville Syrjälä [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=20131010082758.GG13047@intel.com \
--to=ville.syrjala@linux.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