From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 8/8] drm/i915: Pimp the FBC debugfs output
Date: Wed, 21 Apr 2021 16:59:57 +0300 [thread overview]
Message-ID: <875z0f91r6.fsf@intel.com> (raw)
In-Reply-To: <20210414022309.30898-9-ville.syrjala@linux.intel.com>
On Wed, 14 Apr 2021, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Now that each pipe tracks its own no_fbc_reason we can print that
> out in debugfs, and we can also show which pipe is currently
> selected for FBC duty.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> .../drm/i915/display/intel_display_debugfs.c | 50 +++++++++++++------
> 1 file changed, 36 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_debugfs.c b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> index 183c414d554a..26317e66cb95 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> @@ -38,15 +38,36 @@ static int i915_frontbuffer_tracking(struct seq_file *m, void *unused)
> return 0;
> }
>
> +static bool i915_fbc_is_compressing(struct drm_i915_private *dev_priv)
> +{
> + if (!intel_fbc_is_active(dev_priv))
> + return false;
> +
> + if (DISPLAY_VER(dev_priv) >= 8)
> + return intel_de_read(dev_priv, IVB_FBC_STATUS2) & BDW_FBC_COMP_SEG_MASK;
> + else if (DISPLAY_VER(dev_priv) >= 7)
> + return intel_de_read(dev_priv, IVB_FBC_STATUS2) & IVB_FBC_COMP_SEG_MASK;
> + else if (DISPLAY_VER(dev_priv) >= 5)
> + return intel_de_read(dev_priv, ILK_DPFC_STATUS) & ILK_DPFC_COMP_SEG_MASK;
> + else if (IS_G4X(dev_priv))
> + return intel_de_read(dev_priv, DPFC_STATUS) & DPFC_COMP_SEG_MASK;
> + else
> + return intel_de_read(dev_priv, FBC_STATUS) &
> + (FBC_STAT_COMPRESSING | FBC_STAT_COMPRESSED);
> +}
I wouldn't mind moving debugfs helpers like this to files by feature,
e.g. intel_fbc.[ch] in this case. This one could just return bool like
here; in some cases I'm starting to think passing struct seq_file * and
having the helper print there would make sense.
BR,
Jani.
> +
> static int i915_fbc_status(struct seq_file *m, void *unused)
> {
> struct drm_i915_private *dev_priv = node_to_i915(m->private);
> struct intel_fbc *fbc = &dev_priv->fbc;
> + struct intel_crtc *crtc;
> intel_wakeref_t wakeref;
>
> if (!HAS_FBC(dev_priv))
> return -ENODEV;
>
> + drm_modeset_lock_all(&dev_priv->drm);
> +
> wakeref = intel_runtime_pm_get(&dev_priv->runtime_pm);
> mutex_lock(&fbc->lock);
>
> @@ -55,27 +76,28 @@ static int i915_fbc_status(struct seq_file *m, void *unused)
> else
> seq_printf(m, "FBC disabled: %s\n", fbc->no_fbc_reason);
>
> - if (intel_fbc_is_active(dev_priv)) {
> - u32 mask;
> + seq_printf(m, "Compressing: %s\n", yesno(i915_fbc_is_compressing(dev_priv)));
>
> - if (DISPLAY_VER(dev_priv) >= 8)
> - mask = intel_de_read(dev_priv, IVB_FBC_STATUS2) & BDW_FBC_COMP_SEG_MASK;
> - else if (DISPLAY_VER(dev_priv) >= 7)
> - mask = intel_de_read(dev_priv, IVB_FBC_STATUS2) & IVB_FBC_COMP_SEG_MASK;
> - else if (DISPLAY_VER(dev_priv) >= 5)
> - mask = intel_de_read(dev_priv, ILK_DPFC_STATUS) & ILK_DPFC_COMP_SEG_MASK;
> - else if (IS_G4X(dev_priv))
> - mask = intel_de_read(dev_priv, DPFC_STATUS) & DPFC_COMP_SEG_MASK;
> - else
> - mask = intel_de_read(dev_priv, FBC_STATUS) &
> - (FBC_STAT_COMPRESSING | FBC_STAT_COMPRESSED);
> + for_each_intel_crtc(&dev_priv->drm, crtc) {
> + struct intel_plane *plane = to_intel_plane(crtc->base.primary);
> + const struct intel_crtc_state *crtc_state =
> + to_intel_crtc_state(crtc->base.state);
>
> - seq_printf(m, "Compressing: %s\n", yesno(mask));
> + if (!plane->has_fbc)
> + continue;
> +
> + seq_printf(m, "%c [CRTC:%d:%s]/[PLANE:%d:%s]: %s\n",
> + fbc->crtc == crtc ? '*' : ' ',
> + crtc->base.base.id, crtc->base.name,
> + plane->base.base.id, plane->base.name,
> + crtc_state->no_fbc_reason ?: "FBC possible");
> }
>
> mutex_unlock(&fbc->lock);
> intel_runtime_pm_put(&dev_priv->runtime_pm, wakeref);
>
> + drm_modeset_unlock_all(&dev_priv->drm);
> +
> return 0;
> }
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-04-21 14:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 2:23 [Intel-gfx] [PATCH 0/8] drm/i915: FBC cleanups Ville Syrjala
2021-04-14 2:23 ` [Intel-gfx] [PATCH 1/8] drm/i915: Add frontbuffer tracking tracepoints Ville Syrjala
2021-04-21 13:01 ` Jani Nikula
2021-04-14 2:23 ` [Intel-gfx] [PATCH 2/8] drm/i915: Rewrite the FBC tiling check a bit Ville Syrjala
2021-04-14 15:09 ` Jani Nikula
2021-04-15 15:34 ` Ville Syrjälä
2021-04-21 13:00 ` Jani Nikula
2021-04-14 2:23 ` [Intel-gfx] [PATCH 3/8] drm/i915: Extract intel_fbc_update() Ville Syrjala
2021-04-21 13:00 ` Jani Nikula
2021-04-14 2:23 ` [Intel-gfx] [PATCH 4/8] drm/i915: Clear no_fbc_reason on activate Ville Syrjala
2021-04-21 13:48 ` Jani Nikula
2021-04-14 2:23 ` [Intel-gfx] [PATCH 5/8] drm/i915: Move the "recompress on activate" to a central place Ville Syrjala
2021-04-21 13:17 ` Jani Nikula
2021-04-14 2:23 ` [Intel-gfx] [PATCH 6/8] drm/i915: Nuke lots of crap from intel_fbc_state_cache Ville Syrjala
2021-04-14 2:23 ` [Intel-gfx] [PATCH 7/8] drm/i915: No FBC+double wide pipe Ville Syrjala
2021-04-14 2:23 ` [Intel-gfx] [PATCH 8/8] drm/i915: Pimp the FBC debugfs output Ville Syrjala
2021-04-21 13:59 ` Jani Nikula [this message]
2021-04-14 3:08 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: FBC cleanups Patchwork
2021-04-14 3:10 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-04-14 3:13 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2021-04-14 3:38 ` [Intel-gfx] ✗ 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=875z0f91r6.fsf@intel.com \
--to=jani.nikula@linux.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