All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Sharma, Swati2" <swati2.sharma@intel.com>,
	igt-dev@lists.freedesktop.org
Cc: Vinod Govindapillai <vinod.govindapillai@intel.com>
Subject: Re: [PATCH i-g-t] lib/dsc: use intel_display_caps instead of i915_display_capabilities
Date: Wed, 26 Mar 2025 11:26:10 +0200	[thread overview]
Message-ID: <878qos87nx.fsf@intel.com> (raw)
In-Reply-To: <48a20710-a884-45f1-8485-ed1f17450741@intel.com>

On Wed, 26 Mar 2025, "Sharma, Swati2" <swati2.sharma@intel.com> wrote:
> Hi Jani,
>
> Have few queries:
> 1. Are we going to remove i915_display_capabilities ?

Yes, hence the patch at hand. Can't remove it before merging this.

intel_display_caps already has more information than
i915_display_capabilities, and I intend to add more.

> 2. Since this new debugfs intel_display_caps, has prefix "intel" whereas 
> all other debugfs still has "i915"
> Are we going to make this change to other display related debugfs too?

Eventually, yes. The xe driver having debugfs files with i915 prefix is
quite confusing.

I think new debugfs files should be prefixed intel_ while any rename
will need more careful consideration. It's quite the flag day change.

This one's easier as i915_display_capabilities and intel_display_caps
already coexist.

BR,
Jani.


>
> On 25-03-2025 06:38 pm, Jani Nikula wrote:
>> Turns out we've added two similar files in kernel. Consolidate on
>> intel_display_caps as the more driver independent name.
>>
>> Cc: Swati Sharma <swati2.sharma@intel.com>
>> Cc: Vinod Govindapillai <vinod.govindapillai@intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>>   lib/igt_dsc.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/lib/igt_dsc.c b/lib/igt_dsc.c
>> index 8d259b7344a6..4caad39db7a9 100644
>> --- a/lib/igt_dsc.c
>> +++ b/lib/igt_dsc.c
>> @@ -56,7 +56,7 @@ bool igt_is_dsc_supported_by_source(int drmfd)
>>   	dir = igt_debugfs_dir(drmfd);
>>   	igt_assert(dir >= 0);
>>   
>> -	res = igt_debugfs_simple_read(dir, "i915_display_capabilities",
>> +	res = igt_debugfs_simple_read(dir, "intel_display_caps",
>>   				      buf, sizeof(buf));
>>   	close(dir);
>>   
>

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-03-26  9:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 13:08 [PATCH i-g-t] lib/dsc: use intel_display_caps instead of i915_display_capabilities Jani Nikula
2025-03-25 18:11 ` Anirban, Sk
2025-03-26  0:53 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-03-26  1:11 ` ✗ i915.CI.BAT: failure " Patchwork
2025-03-26  9:50   ` Jani Nikula
2025-03-26 10:51     ` Saarinen, Jani
2025-03-26  5:54 ` [PATCH i-g-t] " Sharma, Swati2
2025-03-26  9:26   ` Jani Nikula [this message]
2025-03-26  9:30     ` Sharma, Swati2
2025-03-27  7:44       ` Jani Nikula
2025-03-26 12:25 ` ✗ Xe.CI.Full: failure for " Patchwork
2025-03-28  9:43 ` Patchwork
2025-04-06 14:56 ` 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=878qos87nx.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=swati2.sharma@intel.com \
    --cc=vinod.govindapillai@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.