Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [V2 0/2] Add crtc i915_pipe debugfs file
Date: Sat, 18 Mar 2023 09:47:02 +0530	[thread overview]
Message-ID: <20230318041704.2714520-1-bhanuprakash.modem@intel.com> (raw)

The pipe may differ from crtc index if pipes are fused off. For testing
purposes, IGT needs to know the pipe.

There's already a I915_GET_PIPE_FROM_CRTC_ID IOCTL for this. However,
the upcoming Xe driver won't have that IOCTL, and going forward, we'll
want a unified interface for testing i915 and Xe, as they share the
display code. Thus add the debugfs for i915 display.

Test-with: 20230317165044.2616573-1-bhanuprakash.modem@intel.com

Jani Nikula (2):
  drm/i915/debugfs: switch crtc debugfs to struct intel_crtc
  drm/i915/debugfs: add crtc i915_pipe debugfs file

 drivers/gpu/drm/i915/display/intel_crtc.c     |  2 +-
 .../drm/i915/display/intel_display_debugfs.c  | 35 +++++++++++++------
 .../drm/i915/display/intel_display_debugfs.h  |  6 ++--
 3 files changed, 29 insertions(+), 14 deletions(-)

--
2.40.0


             reply	other threads:[~2023-03-18  4:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-18  4:17 Bhanuprakash Modem [this message]
2023-03-18  4:17 ` [Intel-gfx] [V2 1/2] drm/i915/debugfs: switch crtc debugfs to struct intel_crtc Bhanuprakash Modem
2023-03-18  4:17 ` [Intel-gfx] [V2 2/2] drm/i915/debugfs: add crtc i915_pipe debugfs file Bhanuprakash Modem
2023-03-18  6:26 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning for Add " Patchwork
2023-03-18  6:26 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: " Patchwork
2023-03-18  6:26 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-03-18  6:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-03-18  8:04 ` [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=20230318041704.2714520-1-bhanuprakash.modem@intel.com \
    --to=bhanuprakash.modem@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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