From: Jani Nikula <jani.nikula@linux.intel.com>
To: Animesh Manna <animesh.manna@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/4] drm/i915/panelreplay: dpcd register definition for panelreplay
Date: Fri, 11 Nov 2022 11:37:24 +0200 [thread overview]
Message-ID: <87fsep6dd7.fsf@intel.com> (raw)
In-Reply-To: <20221110150307.3366-2-animesh.manna@intel.com>
On Thu, 10 Nov 2022, Animesh Manna <animesh.manna@intel.com> wrote:
> DPCD register definition added to check and enable panel replay
> capability of the sink.
This patch is not i915 specific like the subject claims.
Please always Cc: dri-devel for drm changes.
BR,
Jani.
>
> Cc: Jouni Högander <jouni.hogander@intel.com>
> Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> ---
> include/drm/display/drm_dp.h | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/include/drm/display/drm_dp.h b/include/drm/display/drm_dp.h
> index e934aab357be..40995f8c2c2f 100644
> --- a/include/drm/display/drm_dp.h
> +++ b/include/drm/display/drm_dp.h
> @@ -537,6 +537,10 @@
> /* DFP Capability Extension */
> #define DP_DFP_CAPABILITY_EXTENSION_SUPPORT 0x0a3 /* 2.0 */
>
> +#define DP_PANEL_REPLAY_CAP 0x0b0
> +# define DP_PANEL_REPLAY_SUPPORT (1 << 0)
> +# define DP_PR_SELECTIVE_UPDATE_SUPPORT (1 << 1)
> +
> /* Link Configuration */
> #define DP_LINK_BW_SET 0x100
> # define DP_LINK_RATE_TABLE 0x00 /* eDP 1.4 */
> @@ -706,6 +710,13 @@
> #define DP_BRANCH_DEVICE_CTRL 0x1a1
> # define DP_BRANCH_DEVICE_IRQ_HPD (1 << 0)
>
> +#define PANEL_REPLAY_CONFIG 0x1b0
> +# define DP_PANEL_REPLAY_ENABLE (1 << 0)
> +# define DP_PR_UNRECOVERABLE_ERROR (1 << 3)
> +# define DP_PR_RFB_STORAGE_ERROR (1 << 4)
> +# define DP_PR_ACTIVE_FRAME_CRC_ERROR (1 << 5)
> +# define DP_PR_SELECTIVE_UPDATE_ENABLE (1 << 6)
> +
> #define DP_PAYLOAD_ALLOCATE_SET 0x1c0
> #define DP_PAYLOAD_ALLOCATE_START_TIME_SLOT 0x1c1
> #define DP_PAYLOAD_ALLOCATE_TIME_SLOT_COUNT 0x1c2
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-11-11 9:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 15:03 [Intel-gfx] [PATCH 0/4] Panel replay phase1 implementation Animesh Manna
2022-11-10 15:03 ` [Intel-gfx] [PATCH 1/4] drm/i915/panelreplay: dpcd register definition for panelreplay Animesh Manna
2022-11-11 9:37 ` Jani Nikula [this message]
2023-07-14 4:06 ` Murthy, Arun R
2023-07-18 9:24 ` Manna, Animesh
2022-11-10 15:03 ` [Intel-gfx] [PATCH 2/4] drm/i915/panelreplay: Added HAS_PANEL_REPLAY() macro Animesh Manna
2023-07-14 4:16 ` Murthy, Arun R
2023-07-18 9:30 ` Manna, Animesh
2022-11-10 15:03 ` [Intel-gfx] [PATCH 3/4] drm/i915/panelreplay: Initializaton and compute config for panel replay Animesh Manna
2022-11-11 4:04 ` kernel test robot
2022-11-11 9:46 ` Jani Nikula
2023-07-14 4:35 ` Murthy, Arun R
2023-07-18 9:35 ` Manna, Animesh
2022-11-10 15:03 ` [Intel-gfx] [PATCH 4/4] drm/i915/panelreplay: enable/disable " Animesh Manna
2023-07-14 4:47 ` Murthy, Arun R
2023-07-18 9:48 ` Manna, Animesh
2022-11-11 3:16 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Panel replay phase1 implementation (rev4) Patchwork
2022-11-11 3:16 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-11-11 4:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-11-11 19:42 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=87fsep6dd7.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=animesh.manna@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