Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 v3 0/6] Panel replay phase1 implementation
Date: Mon, 31 Jul 2023 06:13:12 +0000	[thread overview]
Message-ID: <4b28c4fc9f2f3507987c360eb9aede976491f8e1.camel@intel.com> (raw)
In-Reply-To: <20230728124609.2911830-1-animesh.manna@intel.com>

On Fri, 2023-07-28 at 18:16 +0530, Animesh Manna wrote:
> > Panel Replay is a power saving feature for DP 2.0 monitor and
> > similar
> > to PSR on EDP.
> > 
> > These patches are basic enablement patches added on top of
> > existing psr framework to enable full-screen live active frame
> > update mode of panel replay. Panel replay also can be enabled
> > in selective update mode which will be enabled in a incremental
> > approach.
> > 
> > As per current design panel replay priority is higher than psr.
> > intel_dp->psr.pr_enabled flag indicate panel replay is enabled.
> > intel_dp->psr.pr_enabled + intel_dp->psr.psr2_enabled indicates
> > panel replay is enabled in selective update mode.
> > intel_dp->psr.pr_enabled + intel_dp->psr.psr2_enabled +
> > intel_psr.selective_fetch enabled indicates panel replay is
> > enabled in selective update mode with selective fetch.
> > PSR replated flags remain same like before.
> > 
> > Note: The patches are not tested due to unavailability of monitor.

Couple of generic comment concerning the whole set:

I see both PR and PANEL_REPLAY being used in your patches. I would
choose either PR or PANEL_REPLAY . Same thought on SU and
SELECTIVE_UDATE. As PANEL_SELF_REFRESH is PSR I don't see why PR should
be PANEL_REPLAY. Also SU is widely already used in psr definitions I
would use it for panel replay definitions as well.

BR,

Jouni Högander

> > Cc: Jouni Högander <jouni.hogander@intel.com>
> > Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> > 
> > Animesh Manna (5):
> >   drm/panelreplay: dpcd register definition for panelreplay
> >   drm/i915/panelreplay: Added HAS_PANEL_REPLAY() macro
> >   drm/i915/panelreplay: Initializaton and compute config for panel
> >     replay
> >   drm/i915/panelreplay: Enable panel replay dpcd initialization for
> > > DP
> >   drm/i915/panelreplay: enable/disable panel replay
> > 
> > Jouni Högander (1):
> >   drm/i915/psr: Move psr specific dpcd init into own function
> > 
> >  .../drm/i915/display/intel_display_device.h   |   1 +
> >  .../drm/i915/display/intel_display_types.h    |   9 +-
> >  drivers/gpu/drm/i915/display/intel_dp.c       |  44 ++++-
> >  drivers/gpu/drm/i915/display/intel_psr.c      | 158 >
> > +++++++++++++-----
> >  include/drm/display/drm_dp.h                  |  11 ++
> >  5 files changed, 168 insertions(+), 55 deletions(-)
> > 



  parent reply	other threads:[~2023-07-31  6:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28 12:46 [Intel-gfx] [PATCH v3 0/6] Panel replay phase1 implementation Animesh Manna
2023-07-28 12:46 ` [Intel-gfx] [PATCH v3 1/6] drm/panelreplay: dpcd register definition for panelreplay Animesh Manna
2023-07-31  6:19   ` Hogander, Jouni
2023-08-01  6:31     ` Manna, Animesh
2023-07-28 12:46 ` [Intel-gfx] [PATCH v3 2/6] drm/i915/panelreplay: Added HAS_PANEL_REPLAY() macro Animesh Manna
2023-07-31  6:26   ` Hogander, Jouni
2023-08-01  6:38     ` Manna, Animesh
2023-07-28 12:46 ` [Intel-gfx] [PATCH v3 3/6] drm/i915/psr: Move psr specific dpcd init into own function Animesh Manna
2023-07-28 12:46 ` [Intel-gfx] [PATCH v3 4/6] drm/i915/panelreplay: Initializaton and compute config for panel replay Animesh Manna
2023-07-28 15:51   ` kernel test robot
2023-07-31  6:47   ` Hogander, Jouni
2023-08-10 11:02   ` Hogander, Jouni
2023-07-28 12:46 ` [Intel-gfx] [PATCH v3 5/6] drm/i915/panelreplay: Enable panel replay dpcd initialization for DP Animesh Manna
2023-07-28 12:46 ` [Intel-gfx] [PATCH v3 6/6] drm/i915/panelreplay: enable/disable panel replay Animesh Manna
2023-08-10 10:59   ` Hogander, Jouni
2023-07-28 13:40 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Panel replay phase1 implementation (rev5) Patchwork
2023-07-28 13:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-07-28 13:53 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-07-28 16:39 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-07-31  6:13 ` Hogander, Jouni [this message]
2023-08-01  6:30   ` [Intel-gfx] [PATCH v3 0/6] Panel replay phase1 implementation Manna, Animesh

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=4b28c4fc9f2f3507987c360eb9aede976491f8e1.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