From: Manasi Navare <manasi.d.navare@intel.com>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dp: Reset link params on connector disconnect
Date: Thu, 4 Jun 2020 12:40:20 -0700 [thread overview]
Message-ID: <20200604194020.GE3922@intel.com> (raw)
In-Reply-To: <20200604192340.GF15427@ideak-desk.fi.intel.com>
On Thu, Jun 04, 2020 at 10:23:40PM +0300, Imre Deak wrote:
> On Thu, Jun 04, 2020 at 10:08:58PM +0300, Imre Deak wrote:
> > On Thu, Jun 04, 2020 at 10:01:40PM +0300, Ville Syrjälä wrote:
> > > [...]
> > > > > Then we get this hpd, in this case if we dont reset the param to max values, prev triggered modeset continues
> > > > > with fallback values but since connector probe doesnt happen again through IGT, it tries the same mode
> > > > > with fallback values and return encoder config failure.
> > > >
> > > > If the link training failed then clearly the sink didn't like us anymore
> > > > anyway. So feels like resetting these here is just shifting some race
> > > > window around a bit, but it could still fail if the sink still doesn't
> > > > like us.
> > > >
> > > > Would be good if someone was able to figure out why the sink goes bad in
> > > > the first place.
> > >
> > > Oh, and don't we now have Imre's "weird hpd happened in the middle of
> > > the test, don't trust the results" thing in igt?
> >
> > An LG and IIyama monitor this happens on disconnect and reconnect after
> > waking from an idle state when modesetting them, not sure if it's the
> > same case.
>
> Manasi, could you try if a modeset on the monitor after it has been
> disabled for a while always results in a long HPD pulse a few seconds
> after the modeset? If so does this also happen when you just modeset in
> a sequence from one mode to the other not letting the monitor idle? The
> same monitor should be also tested then with the above sequences on
> older platforms if it behaves the same on those too.
>
This test has been passing on older ICL platforms. But on TGL
we do see these AUX E timeouts once in a while which recover on their
own for the next modeset. Any idea why these spurious AUX timeouts and how I can possibly
rootcause why these timeouts are seen only with AUX E?
Manasi
> >
> > --Imre
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-06-04 19:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 0:23 [Intel-gfx] [PATCH] drm/i915/dp: Reset link params on connector disconnect Manasi Navare
2020-06-04 0:49 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-06-04 1:19 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-06-04 15:25 ` [Intel-gfx] [PATCH] " Ville Syrjälä
2020-06-04 18:35 ` Manasi Navare
2020-06-04 18:38 ` Ville Syrjälä
2020-06-04 18:52 ` Manasi Navare
2020-06-04 18:58 ` Ville Syrjälä
2020-06-04 19:01 ` Ville Syrjälä
2020-06-04 19:08 ` Imre Deak
2020-06-04 19:20 ` Manasi Navare
2020-06-04 19:23 ` Imre Deak
2020-06-04 19:40 ` Manasi Navare [this message]
2020-06-04 19:49 ` Imre Deak
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=20200604194020.GE3922@intel.com \
--to=manasi.d.navare@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.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