Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dsi: Always use unconditional msleep() for the panel_on_delay
Date: Mon, 24 Apr 2023 22:02:17 +0300	[thread overview]
Message-ID: <ZEbSORYAjkUbFA8B@intel.com> (raw)
In-Reply-To: <c31b63cf-235a-b8de-438a-bc4adbb9f282@redhat.com>

On Mon, Apr 24, 2023 at 08:54:27PM +0200, Hans de Goede wrote:
> Hi Ville,
> 
> On 4/24/23 20:34, Ville Syrjälä wrote:
> > On Sat, Apr 22, 2023 at 08:43:59PM +0200, Hans de Goede wrote:
> >> The intel_dsi_msleep() helper skips sleeping if the MIPI-sequences have
> >> a version of 3 or newer and the panel is in vid-mode.
> >>
> >> This is based on the big comment around line 730 which starts with
> >> "Panel enable/disable sequences from the VBT spec.", where
> >> the "v3 video mode seq" column does not have any wait t# entries.
> >>
> >> Commit 6fdb335f1c9c ("drm/i915/dsi: Use unconditional msleep for
> >> the panel_on_delay when there is no reset-deassert MIPI-sequence")
> >> switched to a direct msleep() instead of intel_dsi_msleep()
> >> when there is no MIPI_SEQ_DEASSERT_RESET sequence, to fix
> >> the panel on an Acer Aspire Switch 10 E SW3-016 not turning on.
> >>
> >> This was done under the assumption that when there is a v3
> >> MIPI_SEQ_DEASSERT_RESET sequence it will take care of any
> >> necessary delays.
> >>
> >> On the Nextbook Ares 8A (a Cherry Trail device like the Acer SW3-016)
> >> there is a MIPI_SEQ_DEASSERT_RESET sequence, yet panel_on_delay
> >> must still be honored otherwise the panel will not turn on.
> >>
> >> Switch to always using an unconditional msleep() for
> >> the panel_on_delay instead of making this depend on
> >> the presence of a MIPI_SEQ_DEASSERT_RESET sequence.
> > 
> > I just checked what Windows does, and at least for icl+ it
> > always waits for the panel power delays regardless of what
> > the VBT MIPI sequences are doing.
> > 
> > So I suspect we should just get rid of intel_dsi_msleep()
> > entirely and do what the power sequencing delays tell us.
> > Anything else is untested territory. If the VBT actually
> > wanted us to skip the delays then it should really be
> > setting them to zero.
> 
> So I checked and there are only 4 (before this patch) /
> 3 (after this patch) callers of intel_dsi_msleep().
> 
> So just getting rid of it entirely sounds good to me.
> 
> Shall I prepare a v2 patch which does this ?

Please do.

> 
> Regards,
> 
> Hans
> 
> 
> 
> 
> 
> >> Fixes: 6fdb335f1c9c ("drm/i915/dsi: Use unconditional msleep for the panel_on_delay when there is no reset-deassert MIPI-sequence")
> >> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> >> ---
> >>  drivers/gpu/drm/i915/display/vlv_dsi.c | 18 +++---------------
> >>  1 file changed, 3 insertions(+), 15 deletions(-)
> >>
> >> diff --git a/drivers/gpu/drm/i915/display/vlv_dsi.c b/drivers/gpu/drm/i915/display/vlv_dsi.c
> >> index a6d6d8b33f3f..1b87f8f5f7fd 100644
> >> --- a/drivers/gpu/drm/i915/display/vlv_dsi.c
> >> +++ b/drivers/gpu/drm/i915/display/vlv_dsi.c
> >> @@ -788,7 +788,6 @@ static void intel_dsi_pre_enable(struct intel_atomic_state *state,
> >>  {
> >>  	struct intel_dsi *intel_dsi = enc_to_intel_dsi(encoder);
> >>  	struct intel_crtc *crtc = to_intel_crtc(pipe_config->uapi.crtc);
> >> -	struct intel_connector *connector = to_intel_connector(conn_state->connector);
> >>  	struct drm_i915_private *dev_priv = to_i915(crtc->base.dev);
> >>  	enum pipe pipe = crtc->pipe;
> >>  	enum port port;
> >> @@ -836,21 +835,10 @@ static void intel_dsi_pre_enable(struct intel_atomic_state *state,
> >>  	if (!IS_GEMINILAKE(dev_priv))
> >>  		intel_dsi_prepare(encoder, pipe_config);
> >>  
> >> +	/* Give the panel time to power-on and then deassert its reset */
> >>  	intel_dsi_vbt_exec_sequence(intel_dsi, MIPI_SEQ_POWER_ON);
> >> -
> >> -	/*
> >> -	 * Give the panel time to power-on and then deassert its reset.
> >> -	 * Depending on the VBT MIPI sequences version the deassert-seq
> >> -	 * may contain the necessary delay, intel_dsi_msleep() will skip
> >> -	 * the delay in that case. If there is no deassert-seq, then an
> >> -	 * unconditional msleep is used to give the panel time to power-on.
> >> -	 */
> >> -	if (connector->panel.vbt.dsi.sequence[MIPI_SEQ_DEASSERT_RESET]) {
> >> -		intel_dsi_msleep(intel_dsi, intel_dsi->panel_on_delay);
> >> -		intel_dsi_vbt_exec_sequence(intel_dsi, MIPI_SEQ_DEASSERT_RESET);
> >> -	} else {
> >> -		msleep(intel_dsi->panel_on_delay);
> >> -	}
> >> +	msleep(intel_dsi->panel_on_delay);
> >> +	intel_dsi_vbt_exec_sequence(intel_dsi, MIPI_SEQ_DEASSERT_RESET);
> >>  
> >>  	if (IS_GEMINILAKE(dev_priv)) {
> >>  		glk_cold_boot = glk_dsi_enable_io(encoder);
> >> -- 
> >> 2.39.2
> > 

-- 
Ville Syrjälä
Intel

      reply	other threads:[~2023-04-24 19:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-22 18:43 [Intel-gfx] [PATCH] drm/i915/dsi: Always use unconditional msleep() for the panel_on_delay Hans de Goede
2023-04-22 19:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-04-22 20:33 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-04-23  7:56   ` Hans de Goede
2023-04-24 18:34 ` [Intel-gfx] [PATCH] " Ville Syrjälä
2023-04-24 18:54   ` Hans de Goede
2023-04-24 19:02     ` 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=ZEbSORYAjkUbFA8B@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@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