From: Luca Coelho <luca@coelho.fi>
To: Jani Nikula <jani.nikula@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915/debugfs: add dedicated intel_display_caps debugfs for display
Date: Thu, 19 Sep 2024 11:29:07 +0300 [thread overview]
Message-ID: <799c3feff78cfbec83fed11d83ee7d1bfde13296.camel@coelho.fi> (raw)
In-Reply-To: <1b825b893dd2d423da167a7b6b21d05e8cd0182c.1726231866.git.jani.nikula@intel.com>
On Fri, 2024-09-13 at 15:51 +0300, Jani Nikula wrote:
> Add dedicated intel_display_caps for display, with device info and
> params. Intentionally prefix the file intel_ instead of i915_. Going
> forward, we should do the same for all debugfs files, making them
> independent of i915 and xe.
>
> Remove display param dumping from i915 specific i915_capabilities
> debugfs.
>
> Note that we don't add node_to_intel_display() functionality in
> to_intel_display(). It's too specific for that.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
Reviewed-by: Luca Coelho <luciano.coelho@intel.com>
--
Cheers,
Luca.
next prev parent reply other threads:[~2024-09-19 9:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 12:51 [PATCH 0/2] drm/i915/debugfs: intel_display_caps Jani Nikula
2024-09-13 12:51 ` [PATCH 1/2] drm/i915/debugfs: remove superfluous kernel_param_lock/unlock Jani Nikula
2024-09-13 20:21 ` Andi Shyti
2024-09-13 12:51 ` [PATCH 2/2] drm/i915/debugfs: add dedicated intel_display_caps debugfs for display Jani Nikula
2024-09-19 8:29 ` Luca Coelho [this message]
2024-09-13 15:56 ` ✓ CI.Patch_applied: success for drm/i915/debugfs: intel_display_caps Patchwork
2024-09-13 15:56 ` ✓ CI.checkpatch: " Patchwork
2024-09-13 15:59 ` ✓ CI.KUnit: " Patchwork
2024-09-13 16:14 ` ✓ CI.Build: " Patchwork
2024-09-13 16:16 ` ✓ CI.Hooks: " Patchwork
2024-09-13 16:18 ` ✗ CI.checksparse: warning " Patchwork
2024-09-13 16:46 ` ✓ CI.BAT: success " Patchwork
2024-09-14 8:56 ` ✗ CI.FULL: failure " Patchwork
2024-09-19 9:48 ` [PATCH 0/2] " Jani Nikula
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=799c3feff78cfbec83fed11d83ee7d1bfde13296.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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