Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 4/4] drm/i915: update dpms property in set_mode
Date: Fri, 14 Sep 2012 23:38:59 +0200	[thread overview]
Message-ID: <20120914213859.GI5799@phenom.ffwll.local> (raw)
In-Reply-To: <20120913134201.2ac50cc3@jbarnes-desktop>

On Thu, Sep 13, 2012 at 01:42:01PM -0700, Jesse Barnes wrote:
> On Thu,  6 Sep 2012 22:08:35 +0200
> Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> 
> > Hopefully this makes userspace slightly less confused about us
> > frobbing the dpms state behind its back. Yeah, it would be better
> > to be more careful with not changing the dpms state, but that is
> > quite more invasive.
> > 
> > Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > ---
> >  drivers/gpu/drm/i915/intel_display.c | 6 ++++++
> >  1 file changed, 6 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > index 805324d..bff0936 100644
> > --- a/drivers/gpu/drm/i915/intel_display.c
> > +++ b/drivers/gpu/drm/i915/intel_display.c
> > @@ -6806,7 +6806,13 @@ intel_modeset_update_state(struct drm_device *dev, unsigned prepare_pipes)
> >  		intel_crtc = to_intel_crtc(connector->encoder->crtc);
> >  
> >  		if (prepare_pipes & (1 << intel_crtc->pipe)) {
> > +			struct drm_property *dpms_property =
> > +				dev->mode_config.dpms_property;
> > +
> >  			connector->dpms = DRM_MODE_DPMS_ON;
> > +			drm_connector_property_set_value(connector,
> > +							 dpms_property,
> > +							 DRM_MODE_DPMS_ON);
> >  
> >  			intel_encoder = to_intel_encoder(connector->encoder);
> >  			intel_encoder->connectors_active = true;
> 
> Both this and the last one need lots of testing coming from different
> DPMS states between fbcon and X, especially across different heads and
> connectors.
> 
> Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>

I've merged all four patches for -next, thanks for the review.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2012-09-14 21:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06 20:08 [PATCH 0/4] some follow-up fixlets from the modeset rework Daniel Vetter
2012-09-06 20:08 ` [PATCH 1/4] drm/i915: rip out intel_disable_pch_ports Daniel Vetter
2012-09-13 20:37   ` Jesse Barnes
2012-09-06 20:08 ` [PATCH 2/4] drm/i915: don't disable fdi links harder in ilk_crtc_enable Daniel Vetter
2012-09-13 20:38   ` Jesse Barnes
2012-09-06 20:08 ` [PATCH 3/4] drm/i915: don't call dpms funcs after set_mode Daniel Vetter
2012-09-13 20:41   ` Jesse Barnes
2012-09-06 20:08 ` [PATCH 4/4] drm/i915: update dpms property in set_mode Daniel Vetter
2012-09-13 20:42   ` Jesse Barnes
2012-09-14 21:38     ` Daniel Vetter [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=20120914213859.GI5799@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --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