From: Nathan Chancellor <nathan@kernel.org>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v3 4/4] drm/i915/fbc: Register per-crtc debugfs files
Date: Tue, 21 Dec 2021 09:48:46 -0700 [thread overview]
Message-ID: <YcIFbqLsMGPxJqAX@archlinux-ax161> (raw)
In-Reply-To: <YcH7Tn9pOh4N43cL@intel.com>
On Tue, Dec 21, 2021 at 06:05:34PM +0200, Ville Syrjälä wrote:
> On Sat, Dec 18, 2021 at 06:00:47PM -0700, Nathan Chancellor wrote:
> > Hi Ville,
> >
> > On Mon, Dec 13, 2021 at 05:14:35PM +0200, Ville Syrjala 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.
> > >
> > > v2: Take a trip via intel_crtc_debugfs_add() (Jani)
> > >
> > > Cc: Jani Nikula <jani.nikula@intel.com>
> > > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Apologies if this has already been reported and fixed, I have not seen
> > anything on lore.kernel.org or drm-intel about it.
> >
> > This patch as commit e74c6aa955ca ("drm/i915/fbc: Register per-crtc
> > debugfs files") breaks the build when CONFIG_DEBUG_FS is disabled.
> >
> > drivers/gpu/drm/i915/display/intel_fbc.c: In function ‘intel_fbc_crtc_debugfs_add’:
> > drivers/gpu/drm/i915/display/intel_fbc.c:1817:61: error: ‘struct drm_crtc’ has no member named ‘debugfs_entry’
> > 1817 | intel_fbc_debugfs_add(plane->fbc, crtc->base.debugfs_entry);
> > | ^
>
> Doh. I guess I didn't actually build test the final version with
> DEBUGFS=n.
>
> Does this fix it for you?
Yes, it does.
Tested-by: Nathan Chancellor <nathan@kernel.org>
> diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h
> index 13eeba2a750a..4d01b4d89775 100644
> --- a/include/drm/drm_crtc.h
> +++ b/include/drm/drm_crtc.h
> @@ -1135,14 +1135,12 @@ struct drm_crtc {
> */
> spinlock_t commit_lock;
>
> -#ifdef CONFIG_DEBUG_FS
> /**
> * @debugfs_entry:
> *
> * Debugfs directory for this CRTC.
> */
> struct dentry *debugfs_entry;
> -#endif
>
> /**
> * @crc:
> --
> 2.32.0
>
> --
> Ville Syrjälä
> Intel
next prev parent reply other threads:[~2022-01-10 13:25 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
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 [this message]
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=YcIFbqLsMGPxJqAX@archlinux-ax161 \
--to=nathan@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--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