public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
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 4/7] drm/i915/psr: Add new macro for accessing cached PSR DPCD registers
Date: Wed, 08 Apr 2026 17:04:22 +0300	[thread overview]
Message-ID: <dcb80b09f5fe72f11f4aaea59f1ed2c3495563f8@intel.com> (raw)
In-Reply-To: <20260408140059.252067-5-jouni.hogander@intel.com>

On Wed, 08 Apr 2026, Jouni Högander <jouni.hogander@intel.com> wrote:
> Add new macro to ease accessing cached PSR DPCD registers.
>
> Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_display_types.h | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_types.h b/drivers/gpu/drm/i915/display/intel_display_types.h
> index e2496db1642a..7d04867e3053 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_types.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_types.h
> @@ -584,6 +584,7 @@ struct intel_connector {
>  
>  		struct {
>  			u8 dpcd[EDP_PSR_RECEIVER_CAP_SIZE];
> +#define INTEL_PSR_DPCD_INDEX(psr_dpcd_register)	((psr_dpcd_register) - DP_PSR_SUPPORT)

Dunno, feels like maybe this should be in intel_psr.c. The point being,
that the whole member should basically be off-limits outside of
intel_psr.c.

BR,
Jani.

>  
>  			bool support;
>  			bool su_support;

-- 
Jani Nikula, Intel

  reply	other threads:[~2026-04-08 14:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08 14:00 [PATCH 0/6] PSR/Panel Replay/ALPM logging improvements Jouni Högander
2026-04-08 14:00 ` [PATCH 1/7] drm/i915/psr: Improve PSR state information in crtc state dump Jouni Högander
2026-04-08 14:00 ` [PATCH 2/7] drm/i915/alpm: Dump out computed ALPM parameters " Jouni Högander
2026-04-08 14:00 ` [PATCH 3/7] drm/dp: Include PSR2 granularity registers into PSR capability size define Jouni Högander
2026-04-08 14:00 ` [PATCH 4/7] drm/i915/psr: Add new macro for accessing cached PSR DPCD registers Jouni Högander
2026-04-08 14:04   ` Jani Nikula [this message]
2026-04-08 14:00 ` [PATCH 5/7] drm/i915/psr: Read all PSR capability registers at once Jouni Högander
2026-04-08 14:00 ` [PATCH 6/7] drm/i915/psr: Dump out PSR and Panel Replay DPCD registers Jouni Högander
2026-04-08 14:00 ` [PATCH 7/7] drm/i915/alpm: Dump out ALPM capability DPCD register Jouni Högander
2026-04-08 14:09 ` ✗ CI.checkpatch: warning for PSR/Panel Replay/ALPM logging improvements Patchwork
2026-04-08 14:10 ` ✗ CI.KUnit: 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=dcb80b09f5fe72f11f4aaea59f1ed2c3495563f8@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