From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [i-g-t] lib/igt_kms: Don't read max dotclock on non-display platforms
Date: Wed, 15 Nov 2023 17:31:47 +0530 [thread overview]
Message-ID: <73973ce7-da93-4085-2dd1-5a2e5188b107@intel.com> (raw)
In-Reply-To: <ZVSmcDIr7pVS_odg@intel.com>
On Wed-15-11-2023 04:37 pm, Ville Syrjälä wrote:
> On Wed, Nov 15, 2023 at 02:36:05PM +0530, Bhanuprakash Modem wrote:
>> On non-display platforms, there is no point in checking for
>> max dotclock.
>>
>> Fixes: https://gitlab.freedesktop.org/drm/intel/-/issues/9672
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
>> ---
>> lib/igt_kms.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/lib/igt_kms.c b/lib/igt_kms.c
>> index 89510ff22..2073fae53 100644
>> --- a/lib/igt_kms.c
>> +++ b/lib/igt_kms.c
>> @@ -6056,7 +6056,8 @@ int igt_get_max_dotclock(int fd)
>> char *s;
>> int dir, res, max_dotclock = 0;
>>
>> - if (!is_intel_device(fd))
>> + /* If there is no display, then no point to check for dotclock. */
>> + if (!is_intel_device(fd) || !drmModeGetResources(fd))
>
> That will leak.
I'm really sorry I couldn't get you. Can you elaborate, please? :-)
- Bhanu
>
>> return max_dotclock;
>>
>> dir = igt_debugfs_dir(fd);
>> --
>> 2.40.0
>
next prev parent reply other threads:[~2023-11-15 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 9:06 [igt-dev] [i-g-t] lib/igt_kms: Don't read max dotclock on non-display platforms Bhanuprakash Modem
2023-11-15 9:59 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-11-15 10:19 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-11-15 11:07 ` [igt-dev] [i-g-t] " Ville Syrjälä
2023-11-15 12:01 ` Modem, Bhanuprakash [this message]
2023-11-17 0:58 ` [igt-dev] ✗ Fi.CI.IGT: failure for " 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=73973ce7-da93-4085-2dd1-5a2e5188b107@intel.com \
--to=bhanuprakash.modem@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--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