Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 3/5] drm/i915/psr: Add the latency reporting chicken bit for pipe D
Date: Mon, 30 Jan 2023 07:18:25 +0000	[thread overview]
Message-ID: <34ef080a7ad44d6c337956ca28d96bb7653f2c45.camel@intel.com> (raw)
In-Reply-To: <20221222120048.8740-4-ville.syrjala@linux.intel.com>

On Thu, 2022-12-22 at 14:00 +0200, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> Pipe D has a chicken bit for the latency reporting override
> thing as well. Add it.
> 

This is already taken care in this patch, which is now merged:

https://patchwork.freedesktop.org/patch/517030/?series=112430&rev=2

> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_psr.c | 2 ++
>  drivers/gpu/drm/i915/i915_reg.h          | 1 +
>  2 files changed, 3 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_psr.c
> b/drivers/gpu/drm/i915/display/intel_psr.c
> index 70bd4e69834c..a233510b2162 100644
> --- a/drivers/gpu/drm/i915/display/intel_psr.c
> +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> @@ -1112,6 +1112,8 @@ static u32 wa_16013835468_bit_get(struct
> intel_dp *intel_dp)
>                 return LATENCY_REPORTING_REMOVED_PIPE_B;
>         case PIPE_C:
>                 return LATENCY_REPORTING_REMOVED_PIPE_C;
> +       case PIPE_D:
> +               return LATENCY_REPORTING_REMOVED_PIPE_D;
>         default:
>                 MISSING_CASE(intel_dp->psr.pipe);
>                 return 0;
> diff --git a/drivers/gpu/drm/i915/i915_reg.h
> b/drivers/gpu/drm/i915/i915_reg.h
> index 8b2cf980f323..b0b3b511e19f 100644
> --- a/drivers/gpu/drm/i915/i915_reg.h
> +++ b/drivers/gpu/drm/i915/i915_reg.h
> @@ -5737,6 +5737,7 @@
>  #define  RESET_PCH_HANDSHAKE_ENABLE    REG_BIT(4)
>  
>  #define GEN8_CHICKEN_DCPR_1                    _MMIO(0x46430)
> +#define   LATENCY_REPORTING_REMOVED_PIPE_D     REG_BIT(31)
>  #define   SKL_SELECT_ALTERNATE_DC_EXIT         REG_BIT(30)
>  #define   LATENCY_REPORTING_REMOVED_PIPE_C     REG_BIT(25)
>  #define   LATENCY_REPORTING_REMOVED_PIPE_B     REG_BIT(24)


  reply	other threads:[~2023-01-30  7:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 12:00 [Intel-gfx] [PATCH 0/5] drm/i915: vblank stuff Ville Syrjala
2022-12-22 12:00 ` [Intel-gfx] [PATCH 1/5] drm/i915/vrr: Fix "window2" handling Ville Syrjala
2022-12-22 12:00 ` [Intel-gfx] [PATCH 2/5] drm/i915/psr: Fix the delayed vblank w/a Ville Syrjala
2023-01-30  7:15   ` Hogander, Jouni
2022-12-22 12:00 ` [Intel-gfx] [PATCH 3/5] drm/i915/psr: Add the latency reporting chicken bit for pipe D Ville Syrjala
2023-01-30  7:18   ` Hogander, Jouni [this message]
2022-12-22 12:00 ` [Intel-gfx] [PATCH 4/5] drm/i915: Extract skl_wm_latency() Ville Syrjala
2022-12-22 12:00 ` [Intel-gfx] [PATCH 5/5] drm/i915: Reject wm levels that exceed vblank time Ville Syrjala
2022-12-22 20:02 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: vblank stuff 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=34ef080a7ad44d6c337956ca28d96bb7653f2c45.camel@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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