dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: Thierry Reding <thierry.reding@avionic-design.de>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: Don't generate invalid AVI infoframes for CEA modes
Date: Mon, 5 Aug 2013 21:40:05 +0300	[thread overview]
Message-ID: <20130805184005.GD5004@intel.com> (raw)
In-Reply-To: <20130805181827.GB19851@strange.amr.corp.intel.com>

On Mon, Aug 05, 2013 at 07:18:27PM +0100, Damien Lespiau wrote:
> On Mon, Aug 05, 2013 at 09:07:05PM +0300, Ville Syrjälä wrote:
> > On Mon, Aug 05, 2013 at 02:36:47PM +0100, Damien Lespiau wrote:
> > > >From CEA-861:
> > > 
> > >   Data Byte 1, bit A0 indicates whether Active Format Data is present in
> > >   Data Byte 2 bits R3 through R0. A source device shall set A0=1 when
> > >   any of the AFD bits are set.
> > > 
> > > ie. if we want to set active_aspect, we need to set the
> > > active_info_valid bit to 1 as well.
> > > 
> > > Cc: Thierry Reding <thierry.reding@avionic-design.de>
> > > Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
> > > ---
> > >  drivers/gpu/drm/drm_edid.c | 1 +
> > >  1 file changed, 1 insertion(+)
> > > 
> > > diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
> > > index 95d6f4b..8d1139f 100644
> > > --- a/drivers/gpu/drm/drm_edid.c
> > > +++ b/drivers/gpu/drm/drm_edid.c
> > > @@ -3107,6 +3107,7 @@ drm_hdmi_avi_infoframe_from_display_mode(struct hdmi_avi_infoframe *frame,
> > >  		return 0;
> > 
> > Nothing to do with this patch, but I just spotted this return here. So
> > we're not populating the aspect ratio stuff if VIC=0. Doesn't really
> > make sense to me. Who will tell me what this is trying to achieve?
> 
> I wondered about that to. The intent seems to not set those bits when
> we're not setting a CEA mode. I guess the author thought that only CEA
> modes can understand the infoframes described in CEA-861. I haven't
> found any evidence of that, but made some sense to me.

Perhaps. I'm leaning towards just killing that check though.

-- 
Ville Syrjälä
Intel OTC

      reply	other threads:[~2013-08-05 18:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-05 13:36 [PATCH] drm: Don't generate invalid AVI infoframes for CEA modes Damien Lespiau
2013-08-05 13:54 ` Ville Syrjälä
2013-08-05 14:13   ` Damien Lespiau
2013-08-05 18:07 ` Ville Syrjälä
2013-08-05 18:18   ` Damien Lespiau
2013-08-05 18:40     ` Ville Syrjälä [this message]

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=20130805184005.GD5004@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=damien.lespiau@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=thierry.reding@avionic-design.de \
    /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;
as well as URLs for NNTP newsgroup(s).