Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>,
	Albert Astals Cid <aacid@kde.org>
Cc: Matteo Iervasi <matteoiervasi@gmail.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Emanuele Panigati <ilpanich@gmail.com>
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure
Date: Tue, 11 May 2021 15:57:48 +0300	[thread overview]
Message-ID: <874kf9v35f.fsf@intel.com> (raw)
In-Reply-To: <CAAd53p4ZTBtV0KhmvnoJ1abp0b6xx2hC-grGzr2tx+AURQoOmQ@mail.gmail.com>

On Tue, 11 May 2021, Kai-Heng Feng <kai.heng.feng@canonical.com> wrote:
> On Tue, May 11, 2021 at 2:06 AM Albert Astals Cid <aacid@kde.org> wrote:
>>
>> Yes, I also have the same.
>>
>> I git bisected that and found this to be the cause, i started a new email thread because i couldn't find this email ^_^
>
> Should be fixed by
> https://cgit.freedesktop.org/drm-tip/commit/?id=acca7762eb71bc05a8f28d29320d193150051f79

I've picked up acca7762eb71 ("drm/i915/dp: Use slow and wide link
training for everything") to drm-intel-fixes, and it should find itself
in v5.13-rc2 and subsequently v5.12 stable in the coming weeks.

BR,
Jani.


>
> Kai-Heng
>
>>
>> Cheers,
>>   Albert
>>
>> El dilluns, 10 de maig de 2021, a les 10:07:33 (CEST), Emanuele Panigati va escriure:
>> > Hi,
>> >   on my Dell XPS 15 9570 laptop I might have a regression with Arch Linux
>> > (kernel 5.12.2-arch1-1: during boot the laptop monitor goes black while
>> > external monitors still works...
>> >
>> >
>> > Panich
>> >
>> >
>> > Il giorno lun 11 gen 2021 alle ore 19:28 Ville Syrjälä <
>> > ville.syrjala@linux.intel.com> ha scritto:
>> >
>> > > On Thu, Jan 07, 2021 at 08:20:25PM +0200, Ville Syrjala wrote:
>> > > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> > > >
>> > > > Some new eDP panels don't like to operate at the max parameters, and
>> > > > instead we need to go for an optimal confiugration. That unfortunately
>> > > > doesn't work with older eDP panels which are generally only guaranteed
>> > > > to work at the max parameters.
>> > > >
>> > > > To solve these two conflicting requirements let's start with the optimal
>> > > > setup, and if that fails we start again with the max parameters. The
>> > > > downside is probably an extra modeset when we switch strategies but
>> > > > I don't see a good way to avoid that.
>> > > >
>> > > > For a bit of history we first tried to go for the fast+narrow in
>> > > > commit 7769db588384 ("drm/i915/dp: optimize eDP 1.4+ link config
>> > > > fast and narrow"). but that had to be reverted due to regression
>> > > > on older panels in commit f11cb1c19ad0 ("drm/i915/dp: revert back
>> > > > to max link rate and lane count on eDP"). So now we try to get
>> > > > the best of both worlds by using both strategies.
>> > >
>> > > Pushed. Fingers crossed for no regressions...
>> > >
>> > > --
>> > > Ville Syrjälä
>> > > Intel
>> > >
>> >
>>
>>
>>
>>

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2021-05-11 12:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07 18:20 [Intel-gfx] [PATCH 1/2] drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure Ville Syrjala
2021-01-07 18:20 ` [Intel-gfx] [PATCH 2/2] drm: Refactor intel_dp_compute_link_config_*() Ville Syrjala
2021-01-07 19:38 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/2] drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure Patchwork
2021-01-07 20:06 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-01-08  1:25 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-01-11 18:28 ` [Intel-gfx] [PATCH 1/2] " Ville Syrjälä
2021-05-10  8:07   ` Emanuele Panigati
2021-05-10 18:06     ` Albert Astals Cid
2021-05-11  3:29       ` Kai-Heng Feng
2021-05-11 12:57         ` Jani Nikula [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=874kf9v35f.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=aacid@kde.org \
    --cc=ilpanich@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kai.heng.feng@canonical.com \
    --cc=matteoiervasi@gmail.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