From: "Sharma, Shashank" <shashank.sharma@intel.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
ML dri-devel <dri-devel@lists.freedesktop.org>,
"Vetter, Daniel" <daniel.vetter@intel.com>
Subject: Re: [PATCH 1/4] drm: add picture aspect ratio flags
Date: Thu, 4 Aug 2016 18:45:43 +0530 [thread overview]
Message-ID: <00744cc7-fee7-950b-6ae2-1dae1bbf6210@intel.com> (raw)
In-Reply-To: <CACvgo50fU8GjeXvwC6StPdtV3=c=ZhJ7PQ7=dNCw7xJdgUtcyQ@mail.gmail.com>
Regards
Shashank
On 8/4/2016 5:04 PM, Emil Velikov wrote:
> On 4 August 2016 at 11:16, Sharma, Shashank <shashank.sharma@intel.com> wrote:
>> Hello Emil,
>>
>> Thanks for your time.
>>
>> I have got mixed opinion on this.
>>
>> IMHO we should expose them to userspace too, as UI agents like Hardware
>> composer/X/Wayland must know what does these
>>
>> flags means, so that they can display them on the end user screen (like
>> settings menu)
>>
>> But few people even think thats its too complex to be exposed to userspace
>> agents.
>>
> If we want these/such flags passed between kernel and user space one must:
> - Provide a kernel interface how to do that
> - Provide a userspace (acked by respective developers/maintainers)
> that the approach is sane and proves useful.
>
> Since the above can take some time, I'd suggest dropping those from
> the UAPI header(s)... for now.
>
> -Emil
Please guide me a bit more on this problem, Emil, Daniel.
The reason why I want to pass this to userspace is, so that, HWC/X/any
other UI manager, can send a modeset
which is accurate upto aspect ratio.
Please think of this complete scenario:
- HDMI compliance testing is going on, and we need to apply a CEA mode
(for example, VIC=3, mode - 720x480@60Hz aspect 16:9)
- But HWC doesnt pass the aspect ratio information, and passed only
720x480@60Hz
- Kernel gets the first matching mode, from edid_cea_modes, which is
VIC=2 720x480@60Hz (aspect 4:3)
- Kernel does the modeset of VIC = 2, and AVI IF contain VIC=2
- Compliance equipment expects VIC = 3, so fails the test case.
In this case, its essential that the userspace, which is triggering the
modeset, must know about the aspect ratio field too.
So does this make it a reason to pass this information to usp ?
Regards
Shashank
_______________________________________________
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 13:15 UTC|newest]
Thread overview: 33+ 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 [this message]
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
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:08 ` ✗ Ro.CI.BAT: failure for : Picture aspect ratio support " Patchwork
2016-08-03 11:48 ` [PATCH 0/4]: " 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=00744cc7-fee7-950b-6ae2-1dae1bbf6210@intel.com \
--to=shashank.sharma@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=intel-gfx@lists.freedesktop.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