From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: "Jouni Högander" <jouni.hogander@intel.com>
Subject: Re: [PATCH 1/4] drm/i915/psr: Add defininitions for INTEL_WA_REGISTER_CAPS DPCD register
Date: Wed, 15 Apr 2026 10:28:35 +0300 [thread overview]
Message-ID: <a91669ef2dd6464cc4d73b82a59cc26a54539f42@intel.com> (raw)
In-Reply-To: <20260415054000.400070-2-jouni.hogander@intel.com>
On Wed, 15 Apr 2026, Jouni Högander <jouni.hogander@intel.com> wrote:
> EDP specification says:
>
> "If either VSC SDP is unable to be transmitted 100 ns before the SU region,
> the Source device may optionally transmit the VSC SDP during the prior
> video scan line’s HBlank period There is a Intel specific drm dp register
> currently containing bits related how TCON can support PSR2 with SDP on
> prior line."
>
> Unfortunately many panels are having problems in implementing this. So
> there is a custom Intel specific DPCD register (INTEL_WA_REGISTER_CAPS) to
> figure out if this is properly implemented on a panel or if panel doesn't
> require that 100 ns delay before the SU region. Here are the definitions in
> this custom DPCD address:
>
> 0 = Panel doesn't support SDP on prior line
> 1 = Panel supports SDP on prior line
> 2 = Panel doesn't have 100ns requirement
> 3 = Reserved
>
> Add definitions for this new register and it's values into new header
> intel_dpcd.h.
>
> Bspec: 74741
> Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dpcd.h | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
> create mode 100644 drivers/gpu/drm/i915/display/intel_dpcd.h
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dpcd.h b/drivers/gpu/drm/i915/display/intel_dpcd.h
> new file mode 100644
> index 000000000000..670513ff5552
> --- /dev/null
> +++ b/drivers/gpu/drm/i915/display/intel_dpcd.h
> @@ -0,0 +1,15 @@
> +/* SPDX-License-Identifier: MIT */
> +/*
> + * Copyright © 2026 Intel Corporation
> + */
> +
> +#ifndef __INTEL_DPCD_H__
> +#define __INTEL_DPCD_H__
> +
> +#define INTEL_WA_REGISTER_CAPS 0x3f0
> +# define INTEL_WA_REGISTER_CAPS_PSR2_EARLYSCANLINE_SDP_SUPPORT_MASK REG_GENMASK(1, 0)
> +# define INTEL_WA_REGISTER_CAPS_FALL_BACK_TO_PSR1 0
> +# define INTEL_WA_REGISTER_CAPS_PSR2_WITH_EARLY_SCANLINE 1
> +# define INTEL_WA_REGISTER_CAPS_PSR2_WITHOUT_EARLY_SCANLINE 2
It does get long, but INTEL_DPCD_ prefix?
> +
> +#endif /* __INTEL_DPCD_H__ */
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-04-15 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 5:39 [PATCH 0/4] PSR2 SDP on Prior Scanline workarounds Jouni Högander
2026-04-15 5:39 ` [PATCH 1/4] drm/i915/psr: Add defininitions for INTEL_WA_REGISTER_CAPS DPCD register Jouni Högander
2026-04-15 7:28 ` Jani Nikula [this message]
2026-04-15 5:39 ` [PATCH 2/4] drm/i915/psr: Read Intel DPCD workaround register Jouni Högander
2026-04-15 5:39 ` [PATCH 3/4] drm/i915/psr: Apply Intel DPCD workaround when SDP on prior line used Jouni Högander
2026-04-15 5:40 ` [PATCH 4/4] drm/i915/psr: Apply SDP on prior scanline workaround for NVL Jouni Högander
2026-04-15 5:49 ` ✗ CI.checkpatch: warning for PSR2 SDP on Prior Scanline workarounds Patchwork
2026-04-15 5:50 ` ✓ CI.KUnit: success " Patchwork
2026-04-15 6:54 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-15 7:40 ` ✓ Xe.CI.FULL: " 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=a91669ef2dd6464cc4d73b82a59cc26a54539f42@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jouni.hogander@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