All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/8] tools/intel_watermark: Parse WM_DBG to help diagnose watermark issues
Date: Fri, 14 May 2021 12:31:39 +0300	[thread overview]
Message-ID: <20210514093139.GA8606@intel.com> (raw)
In-Reply-To: <20210414022754.31710-2-ville.syrjala@linux.intel.com>

On Wed, Apr 14, 2021 at 05:27:47AM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> WM_DBG has some useful sticky bits which tell us whether the
> hardware has entered specific LP1+ and/or maxfifo modes since
> those bits were last cleared. Let's dump those out.
> 
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Reviewed-by: Stanislav Lisovskiy <stanislav.lisovskiy@gmail.com>

> ---
>  tools/intel_watermark.c | 33 +++++++++++++++++++++++++++++++++
>  1 file changed, 33 insertions(+)
> 
> diff --git a/tools/intel_watermark.c b/tools/intel_watermark.c
> index 14d1ae0d80f7..bc2a46232772 100644
> --- a/tools/intel_watermark.c
> +++ b/tools/intel_watermark.c
> @@ -41,6 +41,11 @@ static uint32_t read_reg(uint32_t addr)
>  	return INREG(display_base + addr);
>  }
>  
> +static void write_reg(uint32_t addr, uint32_t val)
> +{
> +	OUTREG(display_base + addr, val);
> +}
> +
>  struct gmch_wm {
>  	int wm, wm1, dl, fifo, fbc, burst;
>  	bool dl_prec, valid;
> @@ -249,6 +254,7 @@ static void skl_wm_dump(void)
>  	uint32_t nv12_buf_cfg[num_pipes][max_planes];
>  	uint32_t plane_ctl[num_pipes][max_planes];
>  	uint32_t wm_linetime[num_pipes];
> +	uint32_t wm_dbg;
>  
>  	intel_register_access_init(&mmio_data, intel_get_pci_device(), 0, -1);
>  
> @@ -455,6 +461,17 @@ static void skl_wm_dump(void)
>  
>  	printf("* plane watermark enabled\n");
>  	printf("(x) line watermark if enabled\n");
> +
> +	wm_dbg = read_reg(0x45280);
> +	printf("WM_DBG: 0x%08x\n", wm_dbg);
> +	printf(" LP used:");
> +	for (level = 1; level < num_levels; level++) {
> +		if (wm_dbg & (1 << (23 + level)))
> +			printf(" LP%d", level);
> +	}
> +	printf("\n");
> +	/* clear the sticky bits */
> +	write_reg(0x45280, wm_dbg);
>  }
>  
>  static void ilk_wm_dump(void)
> @@ -608,6 +625,22 @@ static void ilk_wm_dump(void)
>  	}
>  	printf("FBC watermark = %s\n",
>  	       endis(!REG_DECODE1(arb_ctl, 15, 1)));
> +
> +	if (IS_BROADWELL(devid) || IS_HASWELL(devid)) {
> +		uint32_t wm_dbg = read_reg(0x45280);
> +		printf("WM_DBG: 0x%08x\n", wm_dbg);
> +		if (wm_dbg & (1 << 31))
> +			printf(" Full maxfifo used\n");
> +		if (wm_dbg & (1 << 30))
> +			printf(" Sprite maxfifo used\n");
> +		printf(" LP used:");
> +		for (i = 1; i < 4; i++) {
> +			if (wm_dbg & (1 << (23+i)))
> +				printf(" LP%d", i);
> +		}
> +		/* clear the sticky bits */
> +		write_reg(0x45280, wm_dbg);
> +	}
>  }
>  
>  static void vlv_wm_dump(void)
> -- 
> 2.26.3
> 
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2021-05-14  9:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14  2:27 [igt-dev] [PATCH i-g-t 0/8] tools/intel_watermark: Support new platofrms Ville Syrjala
2021-04-14  2:27 ` [igt-dev] [PATCH i-g-t 1/8] tools/intel_watermark: Parse WM_DBG to help diagnose watermark issues Ville Syrjala
2021-05-14  9:31   ` Lisovskiy, Stanislav [this message]
2021-04-14  2:27 ` [igt-dev] [PATCH i-g-t 2/8] tools/intel_watermark: Use WM_SR_CNT to observe SR residency Ville Syrjala
2021-05-14  9:36   ` Lisovskiy, Stanislav
2021-04-14  2:27 ` [igt-dev] [PATCH i-g-t 3/8] tools/intel_watermark: Deal with TGL planes Ville Syrjala
2021-05-14  9:47   ` Lisovskiy, Stanislav
2021-04-14  2:27 ` [igt-dev] [PATCH i-g-t 4/8] tools/intel_watermark: Reduce the number of planes for rkl/adls/adlp Ville Syrjala
2021-05-14  9:53   ` Lisovskiy, Stanislav
2021-04-14  2:27 ` [igt-dev] [PATCH i-g-t 5/8] tools/intel_watermark: TGL+ can have 4 pipes Ville Syrjala
2021-05-14  9:53   ` Lisovskiy, Stanislav
2021-04-14  2:27 ` [igt-dev] [PATCH i-g-t 6/8] tools/intel_watermark: Make reg dump section less wide Ville Syrjala
2021-05-14  9:50   ` Lisovskiy, Stanislav
2021-04-14  2:27 ` [igt-dev] [PATCH i-g-t 7/8] tools/intel_watermark: Handle ADL-P dedicated SAGV watermarks Ville Syrjala
2021-05-14  9:51   ` Lisovskiy, Stanislav
2021-04-14  2:27 ` [igt-dev] [PATCH i-g-t 8/8] tools/intel_watermark: Widen register bitfields Ville Syrjala
2021-05-14  9:51   ` Lisovskiy, Stanislav
2021-04-14  3:04 ` [igt-dev] ✓ Fi.CI.BAT: success for tools/intel_watermark: Support new platofrms Patchwork
2021-04-14  4:01 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20210514093139.GA8606@intel.com \
    --to=stanislav.lisovskiy@intel.com \
    --cc=igt-dev@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 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.