From: "Sharma, Shashank" <shashank.sharma@intel.com>
To: Sean Paul <seanpaul@chromium.org>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 2/4] drm: Add aspect ratio parsing in DRM layer
Date: Thu, 4 Aug 2016 14:52:23 +0530 [thread overview]
Message-ID: <4957e1ac-ccc8-487f-f4fc-3a3f5faf8d61@intel.com> (raw)
In-Reply-To: <CAOw6vbJOa1mZ5t1xwS_xM_g98poHvVQAidtRPutU7=9h8ciKRQ@mail.gmail.com>
Regards
Shashank
On 8/3/2016 11:14 PM, Sean Paul wrote:
> On Wed, Aug 3, 2016 at 6:56 AM, Shashank Sharma
> <shashank.sharma@intel.com> wrote:
>> Current DRM layer functions dont parse aspect ratio information
> s/dont/don't/
Got it.
>
>> while converting a user mode->kernel mode or viceversa. This
> s/viceversa/vice versa/
Got it.
>> causes modeset to pick mode with wrong aspect ratio, eventually
>> cauing failures in HDMI compliance test cases, due to wrong VIC.
> s/cauing/causing/
Ok.
> Sorry for the spelling nits. I originally just found this one, but
> since I was nitpicking one, I figured I should pick at them all.
Thanks for pointing them out. Will fix this.
>> This patch adds aspect ratio information in DRM's mode conversion
>> and mode comparision functions, to make sure kernel picks mode
>> with right aspect ratio (as per the VIC).
>>
>> Signed-off-by: Shashank Sharma <shashank.sharma@intel.com>
>> Signed-off-by: Lin, Jia <lin.a.jia@intel.com>
>> Signed-off-by: Akashdeep Sharma <akashdeep.sharma@intel.com>
>> ---
>> drivers/gpu/drm/drm_modes.c | 31 +++++++++++++++++++++++++++++++
>> 1 file changed, 31 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/drm_modes.c b/drivers/gpu/drm/drm_modes.c
>> index fc5040a..e6029e0 100644
>> --- a/drivers/gpu/drm/drm_modes.c
>> +++ b/drivers/gpu/drm/drm_modes.c
>> @@ -969,6 +969,7 @@ bool drm_mode_equal_no_clocks_no_stereo(const struct drm_display_mode *mode1,
>> mode1->vsync_end == mode2->vsync_end &&
>> mode1->vtotal == mode2->vtotal &&
>> mode1->vscan == mode2->vscan &&
>> + mode1->picture_aspect_ratio == mode2->picture_aspect_ratio &&
>> (mode1->flags & ~DRM_MODE_FLAG_3D_MASK) ==
>> (mode2->flags & ~DRM_MODE_FLAG_3D_MASK))
>> return true;
>> @@ -1471,6 +1472,22 @@ void drm_mode_convert_to_umode(struct drm_mode_modeinfo *out,
>> out->vrefresh = in->vrefresh;
>> out->flags = in->flags;
>> out->type = in->type;
>> + out->flags &= ~DRM_MODE_FLAG_PARMASK;
>> +
>> + switch (in->picture_aspect_ratio) {
>> + case HDMI_PICTURE_ASPECT_4_3:
>> + out->flags |= DRM_MODE_FLAG_PAR4_3;
>> + break;
>> + case HDMI_PICTURE_ASPECT_16_9:
>> + out->flags |= DRM_MODE_FLAG_PAR16_9;
>> + break;
>> + case HDMI_PICTURE_ASPECT_NONE:
>> + case HDMI_PICTURE_ASPECT_RESERVED:
>> + default:
> No need to specify HDMI_PICTURE_ASPECT_NONE &
> HDMI_PICTURE_ASPECT_RESERVED if you use default.
I agree on ASPECT_NONE, but I think we should keep ASPECT_RESERVED, to
maintain the convention, do you think so ?
>> + out->flags |= DRM_MODE_FLAG_PARNONE;
>> + break;
>> + }
>> +
>> strncpy(out->name, in->name, DRM_DISPLAY_MODE_LEN);
>> out->name[DRM_DISPLAY_MODE_LEN-1] = 0;
>> }
>> @@ -1516,6 +1533,20 @@ int drm_mode_convert_umode(struct drm_display_mode *out,
>> strncpy(out->name, in->name, DRM_DISPLAY_MODE_LEN);
>> out->name[DRM_DISPLAY_MODE_LEN-1] = 0;
>>
>> + /* Clearing picture aspect ratio bits from out flags */
>> + out->flags &= ~DRM_MODE_FLAG_PARMASK;
>> +
>> + switch (in->flags & DRM_MODE_FLAG_PARMASK) {
>> + case DRM_MODE_FLAG_PAR4_3:
>> + out->picture_aspect_ratio |= HDMI_PICTURE_ASPECT_4_3;
>> + break;
>> + case DRM_MODE_FLAG_PAR16_9:
>> + out->picture_aspect_ratio |= HDMI_PICTURE_ASPECT_16_9;
>> + break;
>> + default:
>> + out->picture_aspect_ratio = HDMI_PICTURE_ASPECT_NONE;
> For safety,
>
> break;
Sure, Can be done.
Regards
Shashank
>
>> + }
>> +
>> out->status = drm_mode_validate_basic(out);
>> if (out->status != MODE_OK)
>> goto out;
>> --
>> 1.9.1
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-08-04 9:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 10:56 [PATCH 0/4]: Picture aspect ratio support in DRM layer Shashank Sharma
2016-08-03 10:56 ` [PATCH 1/4] drm: add picture aspect ratio flags Shashank Sharma
2016-08-03 17:40 ` Sean Paul
2016-08-04 9:19 ` Sharma, Shashank
2016-08-04 9:42 ` Emil Velikov
2016-08-04 10:16 ` Sharma, Shashank
2016-08-04 10:36 ` [Intel-gfx] " Daniel Vetter
2016-08-04 13:05 ` Sharma, Shashank
2016-08-04 16:04 ` Daniel Vetter
2016-08-04 11:34 ` Emil Velikov
2016-08-04 13:15 ` Sharma, Shashank
2016-08-04 14:31 ` Emil Velikov
2016-08-04 16:09 ` Daniel Vetter
2016-08-05 3:37 ` [Intel-gfx] " Sharma, Shashank
2016-08-09 13:12 ` Jose Abreu
2016-08-09 13:44 ` [Intel-gfx] " Daniel Vetter
2016-08-09 13:57 ` Sharma, Shashank
2016-08-18 10:15 ` Emil Velikov
2016-08-03 10:56 ` [PATCH 2/4] drm: Add aspect ratio parsing in DRM layer Shashank Sharma
2016-08-03 17:44 ` Sean Paul
2016-08-04 9:22 ` Sharma, Shashank [this message]
2016-08-03 10:56 ` [PATCH 3/4] video: Add new aspect ratios for HDMI 2.0 Shashank Sharma
2016-08-03 17:47 ` Sean Paul
2016-08-03 10:56 ` [PATCH 4/4] drm: Add and handle new aspect ratios in DRM layer Shashank Sharma
2016-08-03 17:47 ` [Intel-gfx] " Sean Paul
2016-08-03 11:48 ` [PATCH 0/4]: Picture aspect ratio support " Daniel Vetter
2016-08-03 13:08 ` Jose Abreu
2016-08-03 15:47 ` Sharma, Shashank
2016-08-04 14:16 ` Jose Abreu
2016-08-04 14:29 ` Sharma, Shashank
2016-08-04 15:13 ` Jose Abreu
2016-08-03 15:33 ` Sharma, Shashank
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=4957e1ac-ccc8-487f-f4fc-3a3f5faf8d61@intel.com \
--to=shashank.sharma@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=seanpaul@chromium.org \
/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