From: "Michel Dänzer" <michel.daenzer@mailbox.org>
To: "Murthy, Arun R" <arun.r.murthy@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>,
"G M, Adarsh" <adarsh.g.m@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH libdrm 2/2] tests/crtclist: add utility to inspect CRTC usage
Date: Tue, 22 Sep 2026 16:16:54 +0200 [thread overview]
Message-ID: <737a7039-9b77-416f-a331-698a9cd980a2@mailbox.org> (raw)
In-Reply-To: <IA0PR11MB7307D575C550CFF4AB2866BCBA842@IA0PR11MB7307.namprd11.prod.outlook.com>
On 9/21/26 16:07, Murthy, Arun R wrote:
>> From: Murthy, Arun R <arun.r.murthy@intel.com>
>>
>> Add a small diagnostic utility built on the new drmModeGetCrtcList() API. It
>> prints the total number of CRTCs, how many are free vs in use, and a per-CRTC
>> line with state, scanout framebuffer and active mode.
>>
>> Built like the other tests/ utilities (drmdevice, modeprint); it is a human-facing
>> tool and is intentionally not registered as a meson test, since correctness is
>> covered by the drmmode_crtc_list_ult suite.
>>
> ULT is removed from this patch, as this utility itself should suffice.
> This paragraph will be removed in the next version.
Note that we use gitlab MRs for libdrm: https://gitlab.freedesktop.org/mesa/libdrm/-/merge_requests
--
Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer
https://redhat.com \ Libre software enthusiast
next prev parent reply other threads:[~2026-09-22 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 13:07 [PATCH libdrm 0/2] Get active crtc list Arun R Murthy
2026-09-21 13:07 ` [PATCH libdrm 1/2] xf86drmMode: add drmModeGetCrtcList() to enumerate available CRTCs Arun R Murthy
2026-09-21 13:07 ` [PATCH libdrm 2/2] tests/crtclist: add utility to inspect CRTC usage Arun R Murthy
2026-09-21 14:07 ` Murthy, Arun R
2026-09-22 14:16 ` Michel Dänzer [this message]
2026-09-23 4:22 ` Murthy, Arun R
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=737a7039-9b77-416f-a331-698a9cd980a2@mailbox.org \
--to=michel.daenzer@mailbox.org \
--cc=adarsh.g.m@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=ville.syrjala@linux.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