From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"j@metarealtyinc.ca" <j@metarealtyinc.ca>
Cc: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
"Nikula, Jani" <jani.nikula@intel.com>,
"Manna, Animesh" <animesh.manna@intel.com>
Subject: Re: [PATCH v3] drm/i915/alpm: Add a quirk to keep the fast wake ahead of the IO buffer wake
Date: Fri, 4 Sep 2026 12:51:00 +0000 [thread overview]
Message-ID: <9bcfbb0aee505ca2fda77dbe386a7569290619ae.camel@intel.com> (raw)
In-Reply-To: <20260904114835.483057-1-j@metarealtyinc.ca>
On Fri, 2026-09-04 at 07:48 -0400, Jake Steinman wrote:
> On Thu, 2026-09-04 Jouni Högander wrote:
> > This patch doesn't help much ATM because we wont get rid of the
> > quirk
> > disabling selective fetch anyways.
>
> Understood. Which quirk is that? As of yesterday's drm-tip this
> machine
> only has the Panel Replay quirk; PSR2 with selective fetch is
> enabled,
> and that is where these CRC errors show up. If selective fetch is
> going
> to be quirked off for the DA16260 as well, then agreed, this can wait
> until the SU problem is understood.
Ok, I understood wrong.
I think PSR2 was working on that setup at the point when I introduced
that quirk
cb8d155b0806 drm/i915/psr: Disable Panel Replay on Dell XPS 16 DA16260
as a quirk
See https://gitlab.freedesktop.org/drm/xe/kernel/-/work_items/7682
Maybe this is actually matter of bisection?
BR,
Jouni Högander
>
> The SU problem is
> https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/9119.
> I'd much rather see that fixed than another quirk on this machine,
> and
> I can test whatever you want on it, same day.
>
> Jake
next prev parent reply other threads:[~2026-09-04 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 16:25 [PATCH] drm/i915/alpm: Keep the extended fast wake ahead of the IO buffer wake Jake Steinman
2026-09-03 4:11 ` Hogander, Jouni
2026-09-03 13:14 ` Jake Steinman
2026-09-03 13:17 ` [PATCH v2] drm/i915/alpm: Add a quirk to keep the " Jake Steinman
2026-09-03 16:14 ` sashiko-bot
[not found] ` <20260904004308.185788-1-j@metarealtyinc.ca>
2026-09-04 4:47 ` [PATCH v3] " Hogander, Jouni
[not found] ` <20260904114835.483057-1-j@metarealtyinc.ca>
2026-09-04 12:51 ` Hogander, Jouni [this message]
2026-09-03 16:09 ` ✗ LGCI.VerificationFailed: failure for drm/i915/alpm: Keep the extended fast wake ahead of the IO buffer wake (rev2) 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=9bcfbb0aee505ca2fda77dbe386a7569290619ae.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=animesh.manna@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=j@metarealtyinc.ca \
--cc=jani.nikula@intel.com \
--cc=ville.syrjala@linux.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