All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: RE: [PATCH 2/2] drm/i915/debugfs: move PCH type to display caps
Date: Fri, 11 Apr 2025 10:00:42 +0300	[thread overview]
Message-ID: <878qo7uqqt.fsf@intel.com> (raw)
In-Reply-To: <SN7PR11MB6750754539172AEC6845950EE3B62@SN7PR11MB6750.namprd11.prod.outlook.com>

On Fri, 11 Apr 2025, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
>> -----Original Message-----
>> From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of Jani
>> Nikula
>> Sent: Thursday, April 10, 2025 7:54 PM
>> To: intel-gfx@lists.freedesktop.org; intel-xe@lists.freedesktop.org
>> Cc: Nikula, Jani <jani.nikula@intel.com>
>> Subject: [PATCH 2/2] drm/i915/debugfs: move PCH type to display caps
>> 
>> Arguably PCH is more relevant to display. Move the information to display caps
>> debugfs.
>> 
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> LGTM,
> Reviewed-by: Suraj Kandpal <suraj.kandpal@intel.com>

Thanks for the review, both pushed to drm-intel-next.

BR,
Jani.

>
>> ---
>>  drivers/gpu/drm/i915/display/intel_display_debugfs.c | 3 +++
>>  drivers/gpu/drm/i915/i915_debugfs.c                  | 2 --
>>  2 files changed, 3 insertions(+), 2 deletions(-)
>> 
>> diff --git a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
>> b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
>> index d43ae6729f21..4c208fdb9137 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
>> +++ b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
>> @@ -53,8 +53,11 @@ static struct intel_display *node_to_intel_display(struct
>> drm_info_node *node)  static int intel_display_caps(struct seq_file *m, void
>> *data)  {
>>  	struct intel_display *display = node_to_intel_display(m->private);
>> +	struct drm_i915_private *i915 = to_i915(display->drm);
>>  	struct drm_printer p = drm_seq_file_printer(m);
>> 
>> +	drm_printf(&p, "PCH type: %d\n", INTEL_PCH_TYPE(i915));
>> +
>>  	intel_display_device_info_print(DISPLAY_INFO(display),
>>  					DISPLAY_RUNTIME_INFO(display), &p);
>>  	intel_display_params_dump(&display->params, display->drm->driver-
>> >name, &p); diff --git a/drivers/gpu/drm/i915/i915_debugfs.c
>> b/drivers/gpu/drm/i915/i915_debugfs.c
>> index 0d9e263913ff..967c0501e91e 100644
>> --- a/drivers/gpu/drm/i915/i915_debugfs.c
>> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
>> @@ -66,8 +66,6 @@ static int i915_capabilities(struct seq_file *m, void *data)
>>  	struct drm_i915_private *i915 = node_to_i915(m->private);
>>  	struct drm_printer p = drm_seq_file_printer(m);
>> 
>> -	seq_printf(m, "pch: %d\n", INTEL_PCH_TYPE(i915));
>> -
>>  	intel_device_info_print(INTEL_INFO(i915), RUNTIME_INFO(i915), &p);
>>  	i915_print_iommu_status(i915, &p);
>>  	intel_gt_info_print(&to_gt(i915)->info, &p);
>> --
>> 2.39.5
>

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-04-11  7:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-10 14:24 [PATCH 0/2] drm/i915/debugfs: caps cleanups Jani Nikula
2025-04-10 14:24 ` [PATCH 1/2] drm/i915/debugfs: remove i915_display_capabilities Jani Nikula
2025-04-11  5:52   ` Kandpal, Suraj
2025-04-10 14:24 ` [PATCH 2/2] drm/i915/debugfs: move PCH type to display caps Jani Nikula
2025-04-11  5:53   ` Kandpal, Suraj
2025-04-11  7:00     ` Jani Nikula [this message]
2025-04-10 15:23 ` ✓ CI.Patch_applied: success for drm/i915/debugfs: caps cleanups Patchwork
2025-04-10 15:23 ` ✓ CI.checkpatch: " Patchwork
2025-04-10 15:24 ` ✓ CI.KUnit: " Patchwork
2025-04-10 15:27 ` ✓ i915.CI.BAT: " Patchwork
2025-04-10 15:33 ` ✓ CI.Build: " Patchwork
2025-04-10 15:35 ` ✓ CI.Hooks: " Patchwork
2025-04-10 15:36 ` ✓ CI.checksparse: " Patchwork
2025-04-10 15:55 ` ✓ Xe.CI.BAT: " Patchwork
2025-04-10 19:33 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-10 21:03 ` ✓ i915.CI.Full: success " 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=878qo7uqqt.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=suraj.kandpal@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.