From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 04/10] drm/i915/psr: Add register definitions for SFF_CTL and CFF_CTL registers
Date: Fri, 20 Dec 2024 11:36:10 +0200 [thread overview]
Message-ID: <Z2U6ij6MggV1iptS@intel.com> (raw)
In-Reply-To: <20241213063528.2759659-5-jouni.hogander@intel.com>
On Fri, Dec 13, 2024 at 08:35:22AM +0200, Jouni Högander wrote:
> Add register definitions for SFF_CTL and CFF_CTL registers. Name them as
> LNL_SFF_CTL and LNL_CFF_CTL.
>
> Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_psr_regs.h | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_psr_regs.h b/drivers/gpu/drm/i915/display/intel_psr_regs.h
> index 9ad7611506e8..a24f4d76c98a 100644
> --- a/drivers/gpu/drm/i915/display/intel_psr_regs.h
> +++ b/drivers/gpu/drm/i915/display/intel_psr_regs.h
> @@ -251,6 +251,14 @@
> #define ADLP_PSR2_MAN_TRK_CTL_SF_SINGLE_FULL_FRAME REG_BIT(14)
> #define ADLP_PSR2_MAN_TRK_CTL_SF_CONTINUOS_FULL_FRAME REG_BIT(13)
>
> +#define _LNL_SFF_CTL_A 0x60918
> +#define LNL_SFF_CTL(dev_priv, tran) _MMIO_TRANS2(dev_priv, tran, _LNL_SFF_CTL_A)
I don't think we have any funky offset transcoders on new
hardware do we? In that case you can just use the simpler
_MMIO_TRANS().
> +#define LNL_SFF_CTL_SF_SINGLE_FULL_FRAME REG_BIT(1)
> +
> +#define _LNL_CFF_CTL_A 0x6091c
> +#define LNL_CFF_CTL(dev_priv, tran) _MMIO_TRANS2(dev_priv, tran, _LNL_CFF_CTL_A)
> +#define LNL_CFF_CTL_SF_CONTINUOUS_FULL_FRAME REG_BIT(1)
> +
> /* PSR2 Early transport */
> #define _PIPE_SRCSZ_ERLY_TPT_A 0x70074
> #define _PIPE_SRCSZ_ERLY_TPT_B 0x71074
> --
> 2.34.1
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2024-12-20 9:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 6:35 [PATCH 00/10] PSR DSB support Jouni Högander
2024-12-13 6:35 ` [PATCH 01/10] drm/i915/psr: Use PSR2_MAN_TRK_CTL CFF bit only to send full update Jouni Högander
2024-12-13 6:35 ` [PATCH 02/10] drm/i915/psr: Rename psr_force_hw_tracking_exit as intel_psr_force_update Jouni Högander
2024-12-13 6:35 ` [PATCH 03/10] drm/i915/psr: Split setting sff and cff bits away from intel_psr_force_update Jouni Högander
2024-12-13 6:35 ` [PATCH 04/10] drm/i915/psr: Add register definitions for SFF_CTL and CFF_CTL registers Jouni Högander
2024-12-20 9:36 ` Ville Syrjälä [this message]
2024-12-13 6:35 ` [PATCH 05/10] drm/i915/psr: Ensure SFF/CFF bits are not written at their sample point Jouni Högander
2024-12-20 9:34 ` Ville Syrjälä
2024-12-31 9:02 ` Hogander, Jouni
2024-12-13 6:35 ` [PATCH 06/10] drm/i915/psr: Use SFF_CTL on invalidate/flush for LunarLake onwards Jouni Högander
2024-12-13 6:35 ` [PATCH 07/10] drm/i915/psr: Allow writing PSR2_MAN_TRK_CTL using DSB Jouni Högander
2024-12-13 6:35 ` [PATCH 08/10] drm/i915/psr: Changes for PSR2_MAN_TRK_CTL handling when DSB is in use Jouni Högander
2024-12-13 6:35 ` [PATCH 09/10] drm/i915/psr: Remove DSB_SKIP_WAITS_EN chicken bit Jouni Högander
2024-12-13 6:35 ` [PATCH 10/10] drm/i915/psr: Allow DSB usage when PSR is enabled Jouni Högander
2024-12-13 7:31 ` ✗ Fi.CI.CHECKPATCH: warning for PSR DSB support Patchwork
2024-12-13 7:31 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-12-13 7:45 ` ✗ i915.CI.BAT: failure " Patchwork
2024-12-13 7:48 ` ✓ CI.Patch_applied: success " Patchwork
2024-12-13 7:48 ` ✗ CI.checkpatch: warning " Patchwork
2024-12-13 7:49 ` ✓ CI.KUnit: success " Patchwork
2024-12-13 8:07 ` ✓ CI.Build: " Patchwork
2024-12-13 8:10 ` ✓ CI.Hooks: " Patchwork
2024-12-13 8:12 ` ✗ CI.checksparse: warning " Patchwork
2024-12-13 9:03 ` ✓ Xe.CI.BAT: success " Patchwork
2024-12-13 13:59 ` ✗ Xe.CI.Full: failure " Patchwork
2024-12-16 5:10 ` ✓ i915.CI.BAT: success " Patchwork
2024-12-16 6:50 ` ✗ i915.CI.Full: 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=Z2U6ij6MggV1iptS@intel.com \
--to=ville.syrjala@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.