Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ander Conselvan De Oliveira <conselvan2@gmail.com>
To: "Chauhan, Madhav" <madhav.chauhan@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: Deepak M <m.deepak@intel.com>,
	"Nikula, Jani" <jani.nikula@intel.com>,
	"drm-intel-fixes@lists.freedesktop.org"
	<drm-intel-fixes@lists.freedesktop.org>,
	"Vetter, Daniel" <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm/i915/glk: Fix DSI "*ERROR* ULPS is still active" messages
Date: Fri, 28 Apr 2017 11:57:57 +0300	[thread overview]
Message-ID: <1493369877.4634.3.camel@gmail.com> (raw)
In-Reply-To: <FDE0F82259988449BC0C053E4EF090C94804EC7D@BGSMSX104.gar.corp.intel.com>

On Fri, 2017-04-28 at 08:50 +0000, Chauhan, Madhav wrote:
> > -----Original Message-----
> > From: Conselvan De Oliveira, Ander
> > Sent: Friday, April 28, 2017 1:32 PM
> > To: intel-gfx@lists.freedesktop.org
> > Cc: Conselvan De Oliveira, Ander <ander.conselvan.de.oliveira@intel.com>;
> > Deepak M <m.deepak@intel.com>; Chauhan, Madhav
> > <madhav.chauhan@intel.com>; Nikula, Jani <jani.nikula@intel.com>; Vetter,
> > Daniel <daniel.vetter@intel.com>; Jani Nikula <jani.nikula@linux.intel.com>;
> > drm-intel-fixes@lists.freedesktop.org
> > Subject: [PATCH] drm/i915/glk: Fix DSI "*ERROR* ULPS is still active"
> > messages
> > 
> > The sequence in glk_dsi_device_ready() enters ULPS then waits until it is
> > *not* active to then disable it. The correct sequence according to the spec is
> > to enter ULPS then wait until the GLK_ULPS_NOT_ACTIVE bit is zero, i.e., ULPS
> > is active, and then disable ULPS.
> > 
> > Fixing the codition gets rid of the following spurious error messages:
> 
> Please correct the typo error to "condition", otherwise looks good.
> Thanks for catching this.

If you upgrade the above statement to a Reviewed-by, I can fix the typo while
merging?

Ander

> 
> > 
> > [drm:glk_dsi_device_ready [i915]] *ERROR* ULPS is still active
> > 
> > Fixes: 4644848369c0 ("drm/i915/glk: Add MIPIIO Enable/disable sequence")
> > Cc: Deepak M <m.deepak@intel.com>
> > Cc: Madhav Chauhan <madhav.chauhan@intel.com>
> > Cc: Jani Nikula <jani.nikula@intel.com>
> > Cc: Daniel Vetter <daniel.vetter@intel.com>
> > Cc: Jani Nikula <jani.nikula@linux.intel.com>
> > Cc: intel-gfx@lists.freedesktop.org
> > Cc: <drm-intel-fixes@lists.freedesktop.org>
> > Signed-off-by: Ander Conselvan de Oliveira
> > <ander.conselvan.de.oliveira@intel.com>
> > ---
> >  drivers/gpu/drm/i915/intel_dsi.c | 7 +++----
> >  1 file changed, 3 insertions(+), 4 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_dsi.c
> > b/drivers/gpu/drm/i915/intel_dsi.c
> > index 3ffe8b1..fc0ef49 100644
> > --- a/drivers/gpu/drm/i915/intel_dsi.c
> > +++ b/drivers/gpu/drm/i915/intel_dsi.c
> > @@ -410,11 +410,10 @@ static void glk_dsi_device_ready(struct
> > intel_encoder *encoder)
> >  		val |= (ULPS_STATE_ENTER | DEVICE_READY);
> >  		I915_WRITE(MIPI_DEVICE_READY(port), val);
> > 
> > -		/* Wait for ULPS Not active */
> > +		/* Wait for ULPS active */
> >  		if (intel_wait_for_register(dev_priv,
> > -				MIPI_CTRL(port), GLK_ULPS_NOT_ACTIVE,
> > -				GLK_ULPS_NOT_ACTIVE, 20))
> > -			DRM_ERROR("ULPS is still active\n");
> > +				MIPI_CTRL(port), GLK_ULPS_NOT_ACTIVE, 0,
> > 20))
> > +			DRM_ERROR("ULPS not active\n");
> > 
> >  		/* Exit ULPS */
> >  		val = I915_READ(MIPI_DEVICE_READY(port));
> > --
> > 2.9.3
> 
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-04-28  8:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28  8:02 [PATCH] drm/i915/glk: Fix DSI "*ERROR* ULPS is still active" messages Ander Conselvan de Oliveira
2017-04-28  8:50 ` Chauhan, Madhav
2017-04-28  8:57   ` Ander Conselvan De Oliveira [this message]
2017-04-28 12:44     ` Chauhan, Madhav
2017-04-28 14:16       ` Ander Conselvan De Oliveira
2017-04-28 11:02 ` ✓ Fi.CI.BAT: success for " Patchwork

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=1493369877.4634.3.camel@gmail.com \
    --to=conselvan2@gmail.com \
    --cc=daniel.vetter@intel.com \
    --cc=drm-intel-fixes@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=m.deepak@intel.com \
    --cc=madhav.chauhan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox