All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Coelho, Luciano" <luciano.coelho@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: Only check eDP HPD when AUX CH is shared
Date: Mon, 11 Sep 2023 18:17:24 +0300	[thread overview]
Message-ID: <ZP8vhBWuWnihQ1gQ@intel.com> (raw)
In-Reply-To: <f5bf50d3b7c56f46e96d85a227e214f932550160.camel@intel.com>

On Mon, Sep 11, 2023 at 08:19:21AM +0000, Coelho, Luciano wrote:
> On Fri, 2023-09-08 at 08:25 +0300, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > 
> > Apparently Acer Chromebook C740 (BDW-ULT) doesn't have the
> > eDP HPD line properly connected, and thus fails the new
> > HPD check during eDP probe. The result is that we lose the
> > eDP output.
> > 
> > I suspect all such machines would all be Chromebooks or other
> 
> Small duplication here "...all such machines would all...".

Dropped one 'all'. Thanks for the review -> pushed.

> 
> 
> > Linux exclusive systems as the Windows driver likely wouldn't
> > work either. I did check a few other BDW machines here and
> > those do have eDP HPD connected, one of them even is a
> > different Chromebook (Samus).
> > 
> > To account for these funky machines let's skip the HPD check when
> > it looks like the eDP port is the only one using that specific AUX
> > channel. In case of multiple ports sharing the same AUX CH (eg. on
> > Asrock B250M-HDV) we still do the check and thus should correctly
> > ignore the eDP port in favor of the other DP port (usually a DP->VGA
> > converter).
> > 
> > v2: Don't oops during list iteration
> > 
> > Cc: stable@vger.kernel.org
> > Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/9264
> > Fixes: cfe5bdfb27fa ("drm/i915: Check HPD live state during eDP probe")
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> 
> Regardless of the small grammatical issue, LGTM:
> 
> Reviewed-by: Luca Coelho <luciano.coelho@intel.com>
> 
> --
> Cheers,
> Luca.

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2023-09-11 15:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 12:17 [Intel-gfx] [PATCH] drm/i915: Only check eDP HPD when AUX CH is shared Ville Syrjala
2023-09-07 12:17 ` Ville Syrjala
2023-09-07 13:11 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2023-09-08  5:25 ` [Intel-gfx] [PATCH v2] " Ville Syrjala
2023-09-08  5:25   ` Ville Syrjala
2023-09-11  8:19   ` [Intel-gfx] " Coelho, Luciano
2023-09-11 15:17     ` Ville Syrjälä [this message]
2023-09-08  6:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Only check eDP HPD when AUX CH is shared (rev2) Patchwork
2023-09-08 11:37 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=ZP8vhBWuWnihQ1gQ@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=luciano.coelho@intel.com \
    --cc=stable@vger.kernel.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 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.