public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 4/4] drm/i915/fbc: Register per-crtc debugfs files
Date: Mon, 13 Dec 2021 16:01:15 +0200	[thread overview]
Message-ID: <87ilvs7ges.fsf@intel.com> (raw)
In-Reply-To: <20211213134450.3082-5-ville.syrjala@linux.intel.com>

On Mon, 13 Dec 2021, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Expose FBC debugfs files for each crtc. These may or may not point
> to the same FBC instance depending on the platform.
>
> We leave the old global debugfs files in place until
> igt catches up to the new per-crtc approach.
>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_fbc.c | 31 +++++++++++++++---------
>  1 file changed, 19 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_fbc.c b/drivers/gpu/drm/i915/display/intel_fbc.c
> index 53c93387710c..eafd84e7f058 100644
> --- a/drivers/gpu/drm/i915/display/intel_fbc.c
> +++ b/drivers/gpu/drm/i915/display/intel_fbc.c
> @@ -1798,25 +1798,32 @@ DEFINE_SIMPLE_ATTRIBUTE(intel_fbc_debugfs_false_color_fops,
>  			intel_fbc_debugfs_false_color_set,
>  			"%llu\n");
>  
> -static void intel_fbc_debugfs_add(struct intel_fbc *fbc)
> +static void intel_fbc_debugfs_add(struct intel_fbc *fbc,
> +				  struct dentry *parent)
>  {
> -	struct drm_i915_private *i915 = fbc->i915;
> -	struct drm_minor *minor = i915->drm.primary;
> -
> -	debugfs_create_file("i915_fbc_status", 0444,
> -			    minor->debugfs_root, fbc,
> -			    &intel_fbc_debugfs_status_fops);
> +	debugfs_create_file("i915_fbc_status", 0444, parent,
> +			    fbc, &intel_fbc_debugfs_status_fops);
>  
>  	if (fbc->funcs->set_false_color)
> -		debugfs_create_file("i915_fbc_false_color", 0644,
> -				    minor->debugfs_root, fbc,
> -				    &intel_fbc_debugfs_false_color_fops);
> +		debugfs_create_file("i915_fbc_false_color", 0644, parent,
> +				    fbc, &intel_fbc_debugfs_false_color_fops);
>  }
>  
>  void intel_fbc_debugfs_register(struct drm_i915_private *i915)
>  {
> -	struct intel_fbc *fbc = i915->fbc[INTEL_FBC_A];
> +	struct drm_minor *minor = i915->drm.primary;
> +	struct intel_crtc *crtc;
> +	struct intel_fbc *fbc;
>  
> +	for_each_intel_crtc(&i915->drm, crtc) {
> +		struct intel_plane *plane = to_intel_plane(crtc->base.primary);
> +
> +		if (plane->fbc)
> +			intel_fbc_debugfs_add(plane->fbc, crtc->base.debugfs_entry);
> +	}

I think the per-crtc debugfs files should be registered via
intel_crtc_debugfs_add(). Maybe leave the current
intel_fbc_debugfs_register() function as-is and remove once igt is
fixed.

BR,
Jani.


> +
> +	/* FIXME: remove this once igt is on board with per-crtc stuff */
> +	fbc = i915->fbc[INTEL_FBC_A];
>  	if (fbc)
> -		intel_fbc_debugfs_add(fbc);
> +		intel_fbc_debugfs_add(fbc, minor->debugfs_root);
>  }

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2021-12-13 14:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 13:44 [Intel-gfx] [PATCH v2 0/4] drm/i915/fbc: More multi-FBC refactoring Ville Syrjala
2021-12-13 13:44 ` [Intel-gfx] [PATCH v2 1/4] drm/i915/fbc: Parametrize FBC register offsets Ville Syrjala
2021-12-13 19:54   ` Jani Nikula
2021-12-14 16:25     ` Ville Syrjälä
2021-12-14 17:27       ` Ville Syrjälä
2021-12-15  9:05         ` Sarvela, Tomi P
2021-12-15 13:25           ` Ville Syrjälä
2021-12-15 13:30             ` Sarvela, Tomi P
2021-12-15 14:11               ` Sarvela, Tomi P
2021-12-14 18:34       ` Jani Nikula
2021-12-14 18:46   ` [Intel-gfx] [PATCH v3 1/5] " Ville Syrjala
2021-12-13 13:44 ` [Intel-gfx] [PATCH v2 2/4] drm/i915/fbc: Loop through FBC instances in various places Ville Syrjala
2021-12-13 13:44 ` [Intel-gfx] [PATCH v2 3/4] drm/i915/fbc: Introduce device info fbc_mask Ville Syrjala
2021-12-13 13:44 ` [Intel-gfx] [PATCH v2 4/4] drm/i915/fbc: Register per-crtc debugfs files Ville Syrjala
2021-12-13 14:01   ` Jani Nikula [this message]
2021-12-13 15:04     ` Ville Syrjälä
2021-12-13 15:14   ` [Intel-gfx] [PATCH v3 " Ville Syrjala
2021-12-13 19:09     ` Jani Nikula
2021-12-14 18:44       ` Ville Syrjälä
2021-12-19  1:00     ` Nathan Chancellor
2021-12-21 16:05       ` Ville Syrjälä
2021-12-21 16:48         ` Nathan Chancellor
2021-12-13 18:19 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/fbc: More multi-FBC refactoring (rev3) Patchwork
2021-12-13 18:20 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-12-13 18:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-12-14  0:27 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=87ilvs7ges.fsf@intel.com \
    --to=jani.nikula@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