All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ander Conselvan De Oliveira <conselvan2@gmail.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Use pipe_config's cpu_transcoder for	reading dp_mst hw state
Date: Fri, 30 Jan 2015 12:23:39 +0200	[thread overview]
Message-ID: <1422613419.3935.3.camel@gmail.com> (raw)
In-Reply-To: <87egqcy3po.fsf@intel.com>

On pe, 2015-01-30 at 12:15 +0200, Jani Nikula wrote:
> On Fri, 30 Jan 2015, Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com> wrote:
> > On the hardware state readout path, using crtc->config happens to work
> > since the proper value is written to it before encoder->get_config() is
> > called. However, in the check_crtc() path, the state will be read from
> > the cpu_transcoder in the software tracking, instead of the one just
> > read out from hw. Using the field in the supplied intel_crtc_state
> > should do the right thing in both cases.
> >
> > Signed-off-by: Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com>
> > ---
> >
> > I noticed this while reading the code. Patch is only compiled tested.

I did a quick search, but I didn't find anything that seems related.
This shouldn't fix anything but a hypothetical WARN() after modeset, due
to the state tracked in software being different from what is read out
off the hardware.

Ander

> 
> There might be a bug for this.
> 
> BR,
> Jani.
> 
> >
> > ---
> >  drivers/gpu/drm/i915/intel_dp_mst.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_dp_mst.c b/drivers/gpu/drm/i915/intel_dp_mst.c
> > index 2856b0b..9f67a37 100644
> > --- a/drivers/gpu/drm/i915/intel_dp_mst.c
> > +++ b/drivers/gpu/drm/i915/intel_dp_mst.c
> > @@ -226,7 +226,7 @@ static void intel_dp_mst_enc_get_config(struct intel_encoder *encoder,
> >  	struct intel_crtc *crtc = to_intel_crtc(encoder->base.crtc);
> >  	struct drm_device *dev = encoder->base.dev;
> >  	struct drm_i915_private *dev_priv = dev->dev_private;
> > -	enum transcoder cpu_transcoder = crtc->config->cpu_transcoder;
> > +	enum transcoder cpu_transcoder = pipe_config->cpu_transcoder;
> >  	u32 temp, flags = 0;
> >  
> >  	pipe_config->has_dp_encoder = true;
> > -- 
> > 2.1.0
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-01-30 10:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30  9:50 [PATCH] drm/i915: Use pipe_config's cpu_transcoder for reading dp_mst hw state Ander Conselvan de Oliveira
2015-01-30 10:15 ` Jani Nikula
2015-01-30 10:23   ` Ander Conselvan De Oliveira [this message]
2015-01-30 10:17 ` [PATCH v2] drm/i915: Use pipe_config's cpu_transcoder for reading encoder " Ander Conselvan de Oliveira
2015-01-30 16:38   ` Daniel Vetter
2015-02-01 20:45   ` shuang.he
2015-02-01  6:12 ` [PATCH] drm/i915: Use pipe_config's cpu_transcoder for reading dp_mst " shuang.he

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=1422613419.3935.3.camel@gmail.com \
    --to=conselvan2@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.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.