Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Souza, Jose" <jose.souza@intel.com>
To: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Deak, Imre" <imre.deak@intel.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fix SEL_FETCH_PLANE_*(PIPE_B+) register addresses
Date: Thu, 21 Apr 2022 16:26:07 +0000	[thread overview]
Message-ID: <dfe47e5aae29f2895baa9d319a7e5d7f6345c4fd.camel@intel.com> (raw)
In-Reply-To: <20220421162221.2261895-1-imre.deak@intel.com>

On Thu, 2022-04-21 at 19:22 +0300, Imre Deak wrote:
> Fix typo in the _SEL_FETCH_PLANE_BASE_1_B register base address.
> 

Reviewed-by: José Roberto de Souza <jose.souza@intel.com>

> Fixes: a5523e2ff074a5 ("drm/i915: Add PSR2 selective fetch registers")
> References: https://gitlab.freedesktop.org/drm/intel/-/issues/5400
> Cc: José Roberto de Souza <jose.souza@intel.com>
> Cc: <stable@vger.kernel.org> # v5.9+
> Signed-off-by: Imre Deak <imre.deak@intel.com>
> ---
>  drivers/gpu/drm/i915/i915_reg.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> index 04d86cb6224fc..0ca6517b4595a 100644
> --- a/drivers/gpu/drm/i915/i915_reg.h
> +++ b/drivers/gpu/drm/i915/i915_reg.h
> @@ -5172,7 +5172,7 @@
>  #define _SEL_FETCH_PLANE_BASE_6_A		0x70940
>  #define _SEL_FETCH_PLANE_BASE_7_A		0x70960
>  #define _SEL_FETCH_PLANE_BASE_CUR_A		0x70880
> -#define _SEL_FETCH_PLANE_BASE_1_B		0x70990
> +#define _SEL_FETCH_PLANE_BASE_1_B		0x71890
>  
>  #define _SEL_FETCH_PLANE_BASE_A(plane) _PICK(plane, \
>  					     _SEL_FETCH_PLANE_BASE_1_A, \


  reply	other threads:[~2022-04-21 16:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21 16:22 [Intel-gfx] [PATCH] drm/i915: Fix SEL_FETCH_PLANE_*(PIPE_B+) register addresses Imre Deak
2022-04-21 16:26 ` Souza, Jose [this message]
2022-04-21 20:37 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-04-21 21:08 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-04-22  9:38   ` Imre Deak
2022-04-25 15:27     ` Vudum, Lakshminarayana
2022-04-22 12:45 ` Patchwork
2022-04-22 13:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-22 14:25 ` Patchwork
2022-04-22 18:48 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-04-25 11:59   ` Imre Deak
2022-04-25 15:22 ` 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=dfe47e5aae29f2895baa9d319a7e5d7f6345c4fd.camel@intel.com \
    --to=jose.souza@intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=stable@vger.kernel.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