From: Jani Nikula <jani.nikula@intel.com>
To: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 2/2] drm/i915/debugfs: add crtc i915_pipe debugfs file
Date: Tue, 21 Mar 2023 12:39:37 +0200 [thread overview]
Message-ID: <87pm928k2e.fsf@intel.com> (raw)
In-Reply-To: <dc5ded98-7cb9-23f9-999b-341ee0e03e54@intel.com>
On Mon, 20 Mar 2023, "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com> wrote:
> On Mon-20-03-2023 06:14 pm, Jani Nikula wrote:
>> 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.
>>
>> v2: User letters for pipe names (Ville)
>>
>> Cc: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
>> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> With IGT [1], this patch is
>
> Tested-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
Thanks, pushed to drm-intel-next. It'll take a moment for that to be
part of the baseline for testing. Please re-run the tests for [1] after
that.
BR,
Jani.
>
> [1]:
> https://patchwork.freedesktop.org/patch/msgid/20230320131342.2980032-1-bhanuprakash.modem@intel.com
>
> - Bhanu
>
>> ---
>> .../gpu/drm/i915/display/intel_display_debugfs.c | 13 +++++++++++++
>> 1 file changed, 13 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_display_debugfs.c b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
>> index 3c76e718b951..cc5026272558 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
>> +++ b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
>> @@ -1383,6 +1383,17 @@ static int i915_current_bpc_show(struct seq_file *m, void *data)
>> }
>> DEFINE_SHOW_ATTRIBUTE(i915_current_bpc);
>>
>> +/* Pipe may differ from crtc index if pipes are fused off */
>> +static int intel_crtc_pipe_show(struct seq_file *m, void *unused)
>> +{
>> + struct intel_crtc *crtc = m->private;
>> +
>> + seq_printf(m, "%c\n", pipe_name(crtc->pipe));
>> +
>> + return 0;
>> +}
>> +DEFINE_SHOW_ATTRIBUTE(intel_crtc_pipe);
>> +
>> /**
>> * intel_connector_debugfs_add - add i915 specific connector debugfs files
>> * @connector: pointer to a registered drm_connector
>> @@ -1453,4 +1464,6 @@ void intel_crtc_debugfs_add(struct intel_crtc *crtc)
>>
>> debugfs_create_file("i915_current_bpc", 0444, root, crtc,
>> &i915_current_bpc_fops);
>> + debugfs_create_file("i915_pipe", 0444, root, crtc,
>> + &intel_crtc_pipe_fops);
>> }
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-03-21 10:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 12:44 [Intel-gfx] [PATCH v2 1/2] drm/i915/debugfs: switch crtc debugfs to struct intel_crtc Jani Nikula
2023-03-20 12:44 ` [Intel-gfx] [PATCH v2 2/2] drm/i915/debugfs: add crtc i915_pipe debugfs file Jani Nikula
2023-03-20 13:26 ` Modem, Bhanuprakash
2023-03-21 10:39 ` Jani Nikula [this message]
2023-03-20 22:42 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning for series starting with [v2,1/2] drm/i915/debugfs: switch crtc debugfs to struct intel_crtc Patchwork
2023-03-20 22:42 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-03-20 23:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-03-21 2:59 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=87pm928k2e.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=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