From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Werner Sembach <wse@tuxedocomputers.com>
Cc: <jani.nikula@linux.intel.com>, <joonas.lahtinen@linux.intel.com>,
<tvrtko.ursulin@linux.intel.com>, <airlied@gmail.com>,
<daniel@ffwll.ch>, <jose.souza@intel.com>,
<jouni.hogander@intel.com>, <mika.kahola@intel.com>,
<ville.syrjala@linux.intel.com>, <lucas.demarchi@intel.com>,
<Diego.SantaCruz@spinetix.com>, <intel-gfx@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] [PATCH 2/2] Apply quirk to disable PSR 2 on Tongfang PHxTxX1 and PHxTQx1
Date: Wed, 22 Feb 2023 15:13:24 -0500 [thread overview]
Message-ID: <Y/Z3ZJjYQIKb2LQ0@intel.com> (raw)
In-Reply-To: <20230222141755.1060162-3-wse@tuxedocomputers.com>
On Wed, Feb 22, 2023 at 03:17:55PM +0100, Werner Sembach wrote:
> On these Barebones PSR 2 is recognized as supported but is very buggy:
> - Upper third of screen does sometimes not updated, resulting in
> disappearing cursors or ghosts of already closed Windows saying behind.
> - Approximately 40 px from the bottom edge a 3 pixel wide strip of randomly
> colored pixels is flickering.
>
> PSR 1 is working fine however.
I wonder if this is really about the panel's PSR2 or about the userspace
there not marking the dirtyfb? I know I know... it is not userspace fault...
But I wonder if the case you got here highlights the fact that we have
a substantial bug in the i915 itself in regards to PSR2 API.
Jose, Jouni, ideas on how to check what could be happening here?
oh, btw, Werner, do we have an open gilab issue for this?
Thanks,
Rodrigo.
>
> Signed-off-by: Werner Sembach <wse@tuxedocomputers.com>
> Cc: <stable@vger.kernel.org>
> ---
> drivers/gpu/drm/i915/display/intel_quirks.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_quirks.c b/drivers/gpu/drm/i915/display/intel_quirks.c
> index ce6d0fe6448f5..eeb32d3189f5c 100644
> --- a/drivers/gpu/drm/i915/display/intel_quirks.c
> +++ b/drivers/gpu/drm/i915/display/intel_quirks.c
> @@ -65,6 +65,10 @@ static void quirk_no_pps_backlight_power_hook(struct drm_i915_private *i915)
> drm_info(&i915->drm, "Applying no pps backlight power quirk\n");
> }
>
> +/*
> + * Tongfang PHxTxX1 and PHxTQx1 devices have support for PSR 2 but it is broken
> + * on Linux. PSR 1 however works just fine.
> + */
> static void quirk_no_psr2(struct drm_i915_private *i915)
> {
> intel_set_quirk(i915, QUIRK_NO_PSR2);
> @@ -205,6 +209,10 @@ static struct intel_quirk intel_quirks[] = {
> /* ECS Liva Q2 */
> { 0x3185, 0x1019, 0xa94d, quirk_increase_ddi_disabled_time },
> { 0x3184, 0x1019, 0xa94d, quirk_increase_ddi_disabled_time },
> +
> + /* Tongfang PHxTxX1 and PHxTQx1/TUXEDO InfinityBook 14 Gen6 */
> + { 0x9a49, 0x1d05, 0x1105, quirk_no_psr2 },
> + { 0x9a49, 0x1d05, 0x114c, quirk_no_psr2 },
> };
>
> void intel_init_quirks(struct drm_i915_private *i915)
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-02-22 20:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 14:17 [PATCH 0/2] Add quirk to disable PSR 2 on Tongfang PHxTxX1 and PHxTQx1 Werner Sembach
2023-02-22 14:17 ` [PATCH 1/2] Add quirk to disable PSR 2 on a per device basis Werner Sembach
2023-02-22 14:17 ` [PATCH 2/2] Apply quirk to disable PSR 2 on Tongfang PHxTxX1 and PHxTQx1 Werner Sembach
2023-02-22 20:13 ` Rodrigo Vivi [this message]
2023-02-23 6:27 ` [Intel-gfx] " Hogander, Jouni
2023-02-23 12:16 ` Werner Sembach
2023-02-22 15:39 ` [PATCH 0/2] Add " Werner Sembach
2023-02-23 18:26 ` Hogander, Jouni
2023-02-23 18:56 ` Werner Sembach
2023-02-23 19:02 ` Werner Sembach
2023-02-24 6:45 ` Hogander, Jouni
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=Y/Z3ZJjYQIKb2LQ0@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=Diego.SantaCruz@spinetix.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=jose.souza@intel.com \
--cc=jouni.hogander@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=mika.kahola@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=ville.syrjala@linux.intel.com \
--cc=wse@tuxedocomputers.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