From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t 4/6] tools/intel_watermark: Show whether each plane is enabled
Date: Tue, 29 Jan 2019 15:30:27 +0200 [thread overview]
Message-ID: <20190129133027.GY20097@intel.com> (raw)
In-Reply-To: <0d643f52bd2d12fefac590bb8cf14c22889a33fd.camel@intel.com>
On Mon, Jan 28, 2019 at 10:53:33PM +0000, Souza, Jose wrote:
> On Mon, 2019-01-28 at 22:01 +0200, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > To make it easier to spot errors with watermarks vs. plane
> > being enabled/disabled indicate which planes are actually
> > enabled and which are not.
> >
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > tools/intel_watermark.c | 40 ++++++++++++++++++++++++++++++++++++++-
> > -
> > 1 file changed, 38 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/intel_watermark.c b/tools/intel_watermark.c
> > index 97b769250927..8405d6489628 100644
> > --- a/tools/intel_watermark.c
> > +++ b/tools/intel_watermark.c
> > @@ -180,6 +180,20 @@ static const char *skl_wm_linetime_reg_name(int
> > pipe)
> > return reg_name;
> > }
> >
> > +static const char *skl_plane_ctl_reg_name(int pipe, int plane)
> > +{
> > + static char reg_name[32];
> > +
> > + if (plane == 0)
> > + snprintf(reg_name, sizeof(reg_name), "CUR_CTL_%c",
> > + pipe_name(pipe));
> > + else
> > + snprintf(reg_name, sizeof(reg_name),
> > "PLANE_CTL_%1d_%c",
> > + plane, pipe_name(pipe));
> > +
> > + return reg_name;
> > +}
> > +
> > static const char *skl_wm_reg_name(int pipe, int plane, int level)
> > {
> > static char reg_name[32];
> > @@ -231,6 +245,7 @@ static void skl_wm_dump(void)
> > uint32_t wm[num_levels][num_pipes][max_planes];
> > uint32_t wm_trans[num_pipes][max_planes];
> > uint32_t buf_cfg[num_pipes][max_planes];
> > + uint32_t plane_ctl[num_pipes][max_planes];
> > uint32_t wm_linetime[num_pipes];
> >
> > intel_register_access_init(intel_get_pci_device(), 0, -1);
> > @@ -243,6 +258,7 @@ static void skl_wm_dump(void)
> > for (plane = 0; plane < num_planes; plane++) {
> > addr = base_addr + pipe * 0x1000 + plane *
> > 0x100;
> >
> > + plane_ctl[pipe][plane] = read_reg(addr + 0x80);
> > wm_trans[pipe][plane] = read_reg(addr +
> > 0x00168);
> > buf_cfg[pipe][plane] = read_reg(addr +
> > 0x0017C);
> > for (level = 0; level < num_levels; level++) {
> > @@ -259,6 +275,19 @@ static void skl_wm_dump(void)
> > }
> > printf("\n\n");
> >
> > + for (plane = 0; plane < max_planes; plane++) {
> > + for (pipe = 0; pipe < num_pipes; pipe++) {
> > + if (plane >= skl_num_planes(devid, pipe))
> > + break;
> > +
> > + printf("%18s 0x%08x\t" ,
> > + skl_plane_ctl_reg_name(pipe, plane),
> > + plane_ctl[pipe][plane]);
> > + }
> > + printf("\n");
> > + }
> > + printf("\n");
> > +
> > for (plane = 0; plane < max_planes; plane++) {
> > for (level = 0; level < num_levels; level++) {
> > for (pipe = 0; pipe < num_pipes; pipe++) {
> > @@ -312,8 +341,15 @@ static void skl_wm_dump(void)
> > printf("LINETIME: %d (%.3f usec)\n", linetime,
> > linetime* 0.125f);
> >
> > printf("LEVEL");
> > - for (plane = 0; plane < num_planes; plane++)
> > - printf("%10s", skl_plane_name(pipe, plane));
> > + for (plane = 0; plane < num_planes; plane++) {
> > + if (plane == 0)
> > + enable =
> > REG_DECODE1(plane_ctl[pipe][plane], 0, 3) ||
> > + REG_DECODE1(plane_ctl[pipe][pla
> > ne], 5, 1);
>
> I guess we only enabled ARGB and AND/XOR cursors?! But why not keep it
> simple and check for REG_DECODE1(plane_ctl[pipe][plane], 0, 5)?
Because bits 3 and 4 aren't part of the cursor format. Well, apparently
they are now even though they are always 0. I wonder when that was
respecified... apparently for HSW. OK, been like that for a while then
:)
>
> Other than that LGTM:
>
> Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
>
>
> > + else
> > + enable =
> > REG_DECODE1(plane_ctl[pipe][plane], 31, 1);
> > + printf("%9s%c", skl_plane_name(pipe, plane),
> > + endis_ast(enable));
> > + }
> > printf("\n");
> >
> > for (level = 0; level < num_levels; level++) {
--
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-01-29 13:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 20:01 [igt-dev] [PATCH i-g-t 1/6] tools/intel_watermark: Bump number of planes to 8 for icl Ville Syrjala
2019-01-28 20:01 ` [igt-dev] [PATCH i-g-t 2/6] tools/intel_watermark: More biths for PLANE_BUF_CFG Ville Syrjala
2019-01-28 22:19 ` Souza, Jose
2019-01-28 20:01 ` [igt-dev] [PATCH i-g-t 3/6] tools/intel_watermark: Decode wm blocks correctly Ville Syrjala
2019-01-28 22:30 ` Souza, Jose
2019-01-29 13:23 ` Ville Syrjälä
2019-01-29 20:45 ` Souza, Jose
2019-01-28 20:01 ` [igt-dev] [PATCH i-g-t 4/6] tools/intel_watermark: Show whether each plane is enabled Ville Syrjala
2019-01-28 22:53 ` Souza, Jose
2019-01-29 13:30 ` Ville Syrjälä [this message]
2019-01-28 20:01 ` [igt-dev] [PATCH i-g-t 5/6] tools/intel_watermark: Dump NV12_BUF_CFG Ville Syrjala
2019-02-07 0:19 ` Souza, Jose
2019-01-28 20:01 ` [igt-dev] [PATCH i-g-t 6/6] tools/intel_watermark: Clean up the platform checks in the ilk+ code Ville Syrjala
2019-01-28 22:16 ` Souza, Jose
2019-01-28 20:32 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/6] tools/intel_watermark: Bump number of planes to 8 for icl Patchwork
2019-01-28 22:16 ` [igt-dev] [PATCH i-g-t 1/6] " Souza, Jose
2019-01-29 3:25 ` [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,1/6] " 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=20190129133027.GY20097@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jose.souza@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