From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Sharma, Shashank" <shashank.sharma@intel.com>
Cc: dri-devel@lists.freedesktop.org,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] HDMI 4k modes VIC
Date: Thu, 29 Oct 2015 15:18:23 +0200 [thread overview]
Message-ID: <20151029131823.GT4437@intel.com> (raw)
In-Reply-To: <FF3DDC77922A8A4BB08A3BC48A1EA8CB09A6382C@BGSMSX101.gar.corp.intel.com>
On Thu, Oct 29, 2015 at 08:03:29AM +0000, Sharma, Shashank wrote:
> Actually we should update the cea_modedb in drm layer with 4k modes and appropriate VIC, coz the AVI infoframe functions are
> not getting proper VICs for cea modes. Or while processing alternative cea modes, we should check and return VICs.
That's not surprising since the drm mode lists haven't been updated for 861-F.
IIRC Thierry may already have some patches for that, as well as HDMI 2.0.
>
> I was planning to add 4k@60 modes, I will probably add one patch there, for handling the 4k modes in CEA db.
> As per CEA-861-F compliance, the 4k@30 and 4k@60 modes can come in cea DB as SVD modes. So we should have VICs for them also.
> We will also start upstreaming the patches we added for VLV/CHV, for handling aspect ratio support in libdrm layer as well as kernel.
>
> Regards
> Shashank
> -----Original Message-----
> From: Lespiau, Damien
> Sent: Wednesday, October 28, 2015 10:21 PM
> To: Jani Nikula
> Cc: Sharma, Shashank; intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] HDMI 4k modes VIC
>
> On Wed, Oct 28, 2015 at 06:38:21PM +0200, Jani Nikula wrote:
> > > Are you seeing a bug? it's totally possible, I've never used an
> > > actual conformance tool when I wrote that code, so it's likely buggy
> > > and the VIC in the AVI infoframe may well be wrong.
> >
> > Possibly relevant
> > https://bugs.freedesktop.org/show_bug.cgi?id=92217
>
> That one looks different, we don't do aspect ratio on modes very well, not even exposing them to user space.
>
> --
> Damien
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-10-29 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 13:58 HDMI 4k modes VIC Sharma, Shashank
2015-10-28 14:30 ` Damien Lespiau
2015-10-28 16:38 ` Jani Nikula
2015-10-28 16:50 ` Damien Lespiau
2015-10-29 8:03 ` Sharma, Shashank
2015-10-29 13:18 ` Ville Syrjälä [this message]
2015-10-29 15:06 ` [Intel-gfx] " 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=20151029131823.GT4437@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=shashank.sharma@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