From: Karthik B S <karthik.b.s@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: michel@daenzer.net, igt-dev@lists.freedesktop.org,
daniel.vetter@intel.com, petri.latvala@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t v10 2/2] lib/igt_ioctl_wrappers: Add igt_has_drm_cap ioctl wrapper
Date: Fri, 25 Sep 2020 09:55:54 +0530 [thread overview]
Message-ID: <b10c3caa-52d2-29bc-acca-862dd315a3ad@intel.com> (raw)
In-Reply-To: <20200924170951.GM6112@intel.com>
On 9/24/2020 10:39 PM, Ville Syrjälä wrote:
> On Wed, Sep 23, 2020 at 07:32:58PM +0530, Karthik B S wrote:
>> Add a generic helper for DRM_IOCTL_GET_CAP ioctl.
>>
>> v10: -No changes.
>>
>> Signed-off-by: Karthik B S <karthik.b.s@intel.com>
>> ---
>> lib/ioctl_wrappers.c | 15 +++++++++++++++
>> lib/ioctl_wrappers.h | 1 +
>> 2 files changed, 16 insertions(+)
>>
>> diff --git a/lib/ioctl_wrappers.c b/lib/ioctl_wrappers.c
>> index 3781286d..3ea60c61 100644
>> --- a/lib/ioctl_wrappers.c
>> +++ b/lib/ioctl_wrappers.c
>> @@ -1318,3 +1318,18 @@ int __kms_addfb(int fd, uint32_t handle,
>>
>> return ret < 0 ? -errno : ret;
>> }
>> +
>> +/**
>> + * igt_has_drm_cap:
>> + * @fd: Open DRM file descriptor.
>> + * @cap: drm_get_cap structure.
>> + *
>> + * This helper verifies if the passed cap is supported by the kernel
>> + *
>> + * Returns: Whether the cap is supported or not.
>> + */
>> +bool igt_has_drm_cap(int fd, struct drm_get_cap cap)
>
> I don't see why the caller would want to pass in the whole struct.
> Also passing by value is a but nuts. Ie. I'd just the actual cap
> ID and keep the ioctl struct details hidden inside this function.
>
Thanks for the review.
I will make this change.
> The order of the patches looks wrong. 1/2 won't build w/o this AFAICS.
> 'git rebase -x ...' before sending the patches is always a good idea.
>
Sure. I'll fix this. And use 'git rebase -x' from the next time.
Thanks,
Karthik.B.S
>> +{
>> + igt_assert(drmIoctl(fd, DRM_IOCTL_GET_CAP, &cap) == 0);
>> + return cap.value;
>> +}
>> diff --git a/lib/ioctl_wrappers.h b/lib/ioctl_wrappers.h
>> index 870ac8b7..4cf4004d 100644
>> --- a/lib/ioctl_wrappers.h
>> +++ b/lib/ioctl_wrappers.h
>> @@ -196,6 +196,7 @@ struct local_drm_mode_fb_cmd2 {
>>
>> bool igt_has_fb_modifiers(int fd);
>> void igt_require_fb_modifiers(int fd);
>> +bool igt_has_drm_cap(int fd, struct drm_get_cap cap);
>>
>> /**
>> * __kms_addfb:
>> --
>> 2.22.0
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-09-25 4:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 14:02 [igt-dev] [PATCH i-g-t v10 1/2] tests/kms_async_flips: Add test to validate asynchronous flips Karthik B S
2020-09-23 14:02 ` [igt-dev] [PATCH i-g-t v10 2/2] lib/igt_ioctl_wrappers: Add igt_has_drm_cap ioctl wrapper Karthik B S
2020-09-24 17:09 ` Ville Syrjälä
2020-09-25 4:25 ` Karthik B S [this message]
2020-09-23 15:13 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,v10,1/2] tests/kms_async_flips: Add test to validate asynchronous flips Patchwork
2020-09-23 20:56 ` [igt-dev] ✓ 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=b10c3caa-52d2-29bc-acca-862dd315a3ad@intel.com \
--to=karthik.b.s@intel.com \
--cc=daniel.vetter@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=michel@daenzer.net \
--cc=petri.latvala@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