From: Damien Lespiau <damien.lespiau@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.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 15:13:07 +0100 [thread overview]
Message-ID: <20130805141307.GA31470@strange.config> (raw)
In-Reply-To: <20130805135406.GU5004@intel.com>
On Mon, Aug 05, 2013 at 04:54:06PM +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>
>
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> But why don't we just kill active_info_valid and instead just
> check active_aspect in hdmi_avi_infoframe_pack()?
Right, so I thought about that, I'd love to have an API that doesn't
allow its user to do something wrong. My reflections so far:
1/ I did not want to depend on a fix that was outside of the drm/
directory for people that pull that directory between different
kernels, they will end up missing the patch in video/hdmi.c.
On the other hand, we could just tell people to sync
drivers/video/hdmi.c and include/linux/hdmi.h along with drm/.
2/ I was thinking that killing the _valid bits in the
hdmi_avi_infoframe struct would not allow an _unpack() function that
can check if the infoframe was valid.
Probably thinking too much though...
--
Damien
next prev parent reply other threads:[~2013-08-05 14:13 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 [this message]
2013-08-05 18:07 ` Ville Syrjälä
2013-08-05 18:18 ` Damien Lespiau
2013-08-05 18:40 ` Ville Syrjälä
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=20130805141307.GA31470@strange.config \
--to=damien.lespiau@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=thierry.reding@avionic-design.de \
--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;
as well as URLs for NNTP newsgroup(s).