From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "Manna, Animesh" <animesh.manna@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v4 2/6] drm/i915/panelreplay: Added HAS_PANEL_REPLAY() macro
Date: Thu, 24 Aug 2023 11:20:04 +0000 [thread overview]
Message-ID: <0745a8e13d8a8c07debf89398895e2db3579757b.camel@intel.com> (raw)
In-Reply-To: <20230824040952.186407-3-animesh.manna@intel.com>
On Thu, 2023-08-24 at 09:39 +0530, Animesh Manna wrote:
> Platforms having Display 13 and above will support panel
> replay feature of DP 2.0 monitor. Added a HAS_PANEL_REPLAY()
> macro to check for panel replay capability.
>
> v1: Initial version.
> v2: DISPLAY_VER() removed as HAS_DP20() is having platform check.
> [Jouni]
>
> Cc: Jouni Högander <jouni.hogander@intel.com>
> Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_display_device.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_device.h
> b/drivers/gpu/drm/i915/display/intel_display_device.h
> index 8198401aa5be..ab615a3199da 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_device.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_device.h
> @@ -61,6 +61,7 @@ struct drm_printer;
> #define HAS_MSO(i915) (DISPLAY_VER(i915) >= 12)
> #define HAS_OVERLAY(i915) (DISPLAY_INFO(i915)-
> >has_overlay)
> #define HAS_PSR(i915) (DISPLAY_INFO(i915)->has_psr)
> +#define HAS_PANEL_REPLAY(dev_priv) (HAS_DP20(dev_priv))
I think you can drop this macro and use HAD_DP20 directly.
BR,
Jouni Högander
> #define HAS_PSR_HW_TRACKING(i915) (DISPLAY_INFO(i915)-
> >has_psr_hw_tracking)
> #define HAS_PSR2_SEL_FETCH(i915) (DISPLAY_VER(i915) >= 12)
> #define HAS_SAGV(i915) (DISPLAY_VER(i915) >= 9 &&
> !IS_LP(i915))
next prev parent reply other threads:[~2023-08-24 11:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 4:09 [Intel-gfx] [PATCH v4 0/6] Panel replay phase1 implementation Animesh Manna
2023-08-24 4:09 ` [Intel-gfx] [PATCH v4 1/6] drm/panelreplay: dpcd register definition for panelreplay Animesh Manna
2023-08-24 11:29 ` Jani Nikula
2023-08-25 8:02 ` Manna, Animesh
2023-08-24 4:09 ` [Intel-gfx] [PATCH v4 2/6] drm/i915/panelreplay: Added HAS_PANEL_REPLAY() macro Animesh Manna
2023-08-24 11:20 ` Hogander, Jouni [this message]
2023-08-25 7:59 ` Manna, Animesh
2023-08-24 4:09 ` [Intel-gfx] [PATCH v4 3/6] drm/i915/psr: Move psr specific dpcd init into own function Animesh Manna
2023-08-24 4:09 ` [Intel-gfx] [PATCH v4 4/6] drm/i915/panelreplay: Initializaton and compute config for panel replay Animesh Manna
2023-08-24 11:35 ` Jani Nikula
2023-08-25 8:35 ` Manna, Animesh
2023-08-26 2:05 ` kernel test robot
2023-08-24 4:09 ` [Intel-gfx] [PATCH v4 5/6] drm/i915/panelreplay: Enable panel replay dpcd initialization for DP Animesh Manna
2023-08-24 4:09 ` [Intel-gfx] [PATCH v4 6/6] drm/i915/panelreplay: enable/disable panel replay Animesh Manna
2023-08-24 11:25 ` Hogander, Jouni
2023-08-25 8:01 ` Manna, Animesh
2023-08-24 5:05 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Panel replay phase1 implementation (rev6) Patchwork
2023-08-24 5:05 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-24 5:20 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-08-24 12:30 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=0745a8e13d8a8c07debf89398895e2db3579757b.camel@intel.com \
--to=jouni.hogander@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