Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>, <jouni.hogander@intel.com>
Subject: Re: [PATCH 13/19] drm/i915: pass dev_priv explicitly to _PSR2_SU_STATUS
Date: Tue, 30 Apr 2024 22:23:08 -0400	[thread overview]
Message-ID: <ZjGnjLGVGQDSTcZb@intel.com> (raw)
In-Reply-To: <dac8c4ab8b34220cdfc9d5f6109299a040ea1b40.1714471597.git.jani.nikula@intel.com>

On Tue, Apr 30, 2024 at 01:10:07PM +0300, Jani Nikula wrote:
> Avoid the implicit dev_priv local variable use, and pass dev_priv
> explicitly to the _PSR2_SU_STATUS register macro.
> 
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>

why aren't we going one level up here already?

> ---
>  drivers/gpu/drm/i915/display/intel_psr_regs.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_psr_regs.h b/drivers/gpu/drm/i915/display/intel_psr_regs.h
> index e6c62512512f..762fc0ad7eb5 100644
> --- a/drivers/gpu/drm/i915/display/intel_psr_regs.h
> +++ b/drivers/gpu/drm/i915/display/intel_psr_regs.h
> @@ -221,8 +221,8 @@
>  
>  #define _PSR2_SU_STATUS_A		0x60914
>  #define _PSR2_SU_STATUS_EDP		0x6f914
> -#define _PSR2_SU_STATUS(tran, index)	_MMIO_TRANS2(dev_priv, tran, _PSR2_SU_STATUS_A + (index) * 4)
> -#define PSR2_SU_STATUS(tran, frame)	(_PSR2_SU_STATUS(tran, (frame) / 3))
> +#define _PSR2_SU_STATUS(dev_priv, tran, index)	_MMIO_TRANS2(dev_priv, tran, _PSR2_SU_STATUS_A + (index) * 4)
> +#define PSR2_SU_STATUS(tran, frame)	(_PSR2_SU_STATUS(dev_priv, tran, (frame) / 3))
>  #define PSR2_SU_STATUS_SHIFT(frame)	(((frame) % 3) * 10)
>  #define PSR2_SU_STATUS_MASK(frame)	(0x3ff << PSR2_SU_STATUS_SHIFT(frame))
>  #define PSR2_SU_STATUS_FRAMES		8
> -- 
> 2.39.2
> 

  reply	other threads:[~2024-05-01  2:23 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30 10:09 [PATCH 00/19] drm/i915/psr: implicit dev_priv removal Jani Nikula
2024-04-30 10:09 ` [PATCH 01/19] drm/i915: pass dev_priv explicitly to TRANS_EXITLINE Jani Nikula
2024-05-01  2:05   ` Rodrigo Vivi
2024-04-30 10:09 ` [PATCH 02/19] drm/i915: pass dev_priv explicitly to EDP_PSR_CTL Jani Nikula
2024-05-01  2:05   ` Rodrigo Vivi
2024-04-30 10:09 ` [PATCH 03/19] drm/i915: pass dev_priv explicitly to TRANS_PSR_IMR Jani Nikula
2024-05-01  2:14   ` Rodrigo Vivi
2024-04-30 10:09 ` [PATCH 04/19] drm/i915: pass dev_priv explicitly to TRANS_PSR_IIR Jani Nikula
2024-05-01  2:15   ` Rodrigo Vivi
2024-04-30 10:09 ` [PATCH 05/19] drm/i915: pass dev_priv explicitly to EDP_PSR_AUX_CTL Jani Nikula
2024-05-01  2:18   ` Rodrigo Vivi
2024-05-02  9:28     ` Jani Nikula
2024-05-02 12:56       ` Rodrigo Vivi
2024-04-30 10:10 ` [PATCH 06/19] drm/i915: pass dev_priv explicitly to EDP_PSR_AUX_DATA Jani Nikula
2024-05-01  2:18   ` Rodrigo Vivi
2024-04-30 10:10 ` [PATCH 07/19] drm/i915: pass dev_priv explicitly to EDP_PSR_STATUS Jani Nikula
2024-05-01  2:19   ` Rodrigo Vivi
2024-04-30 10:10 ` [PATCH 08/19] drm/i915: pass dev_priv explicitly to EDP_PSR_PERF_CNT Jani Nikula
2024-05-01  2:19   ` Rodrigo Vivi
2024-04-30 10:10 ` [PATCH 09/19] drm/i915: pass dev_priv explicitly to EDP_PSR_DEBUG Jani Nikula
2024-05-01  2:19   ` Rodrigo Vivi
2024-04-30 10:10 ` [PATCH 10/19] drm/i915: pass dev_priv explicitly to EDP_PSR2_CTL Jani Nikula
2024-05-01  2:20   ` Rodrigo Vivi
2024-04-30 10:10 ` [PATCH 11/19] drm/i915: pass dev_priv explicitly to PSR_EVENT Jani Nikula
2024-05-01  2:20   ` Rodrigo Vivi
2024-04-30 10:10 ` [PATCH 12/19] drm/i915: pass dev_priv explicitly to EDP_PSR2_STATUS Jani Nikula
2024-05-01  2:21   ` Rodrigo Vivi
2024-04-30 10:10 ` [PATCH 13/19] drm/i915: pass dev_priv explicitly to _PSR2_SU_STATUS Jani Nikula
2024-05-01  2:23   ` Rodrigo Vivi [this message]
2024-05-02  9:30     ` Jani Nikula
2024-05-02 10:39   ` [PATCH v2] drm/i915: pass dev_priv explicitly to PSR2_SU_STATUS Jani Nikula
2024-05-02 12:55     ` Rodrigo Vivi
2024-04-30 10:10 ` [PATCH 14/19] drm/i915: pass dev_priv explicitly to PSR2_MAN_TRK_CTL Jani Nikula
2024-05-01  2:23   ` Rodrigo Vivi
2024-04-30 10:10 ` [PATCH 15/19] drm/i915: pass dev_priv explicitly to PIPE_SRCSZ_ERLY_TPT Jani Nikula
2024-05-01  2:24   ` Rodrigo Vivi
2024-04-30 10:10 ` [PATCH 16/19] drm/i915: pass dev_priv explicitly to ALPM_CTL Jani Nikula
2024-05-01  2:24   ` Rodrigo Vivi
2024-04-30 10:10 ` [PATCH 17/19] drm/i915: pass dev_priv explicitly to ALPM_CTL2 Jani Nikula
2024-05-01  2:25   ` Rodrigo Vivi
2024-05-02 10:40     ` Jani Nikula
2024-05-06  7:34       ` Hogander, Jouni
2024-05-06  8:28         ` Jani Nikula
2024-04-30 10:10 ` [PATCH 18/19] drm/i915: pass dev_priv explicitly to PORT_ALPM_CTL Jani Nikula
2024-05-01  2:26   ` Rodrigo Vivi
2024-04-30 10:10 ` [PATCH 19/19] drm/i915: pass dev_priv explicitly to PORT_ALPM_LFPS_CTL Jani Nikula
2024-05-01  2:26   ` Rodrigo Vivi
2024-04-30 12:09 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/psr: implicit dev_priv removal Patchwork
2024-04-30 12:09 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-04-30 12:16 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-30 16:31 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-05-02 11:36 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/psr: implicit dev_priv removal (rev2) Patchwork
2024-05-02 11:40 ` ✗ Fi.CI.BAT: 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=ZjGnjLGVGQDSTcZb@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --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