From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>
Cc: "daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v7 1/2] drm: content-type property for HDMI connector
Date: Mon, 30 Apr 2018 06:28:08 +0000 [thread overview]
Message-ID: <537186c3f7011a27b083d4dd035b6fe18241f32e.camel@intel.com> (raw)
In-Reply-To: <20180427194000.GD23723@intel.com>
On Fri, 2018-04-27 at 22:40 +0300, Ville Syrjälä wrote:
> > +
> > +/**
> > + * DOC: HDMI connector properties
> > + *
> > + * content type (HDMI specific):
> > + * Indicates content type setting to be used in HDMI
> > infoframes to indicate
> > + * content type for the external device, so that it adjusts
> > it's display
> > + * settings accordingly.
> > + *
> > + * The value of this property can be one of the following:
> > + *
> > + * - DRM_MODE_CONTENT_TYPE_NO_DATA = 0
> > + * Content type is unknown, it content(itc) bit is
> > cleared.
> > + * - DRM_MODE_CONTENT_TYPE_GRAPHICS = 4
> > + * Content type is graphics, it content(itc) bit is
> > set.
> > + * - DRM_MODE_CONTENT_TYPE_PHOTO = 5
> > + * Content type is photo, itc bit is set.
> > + * - DRM_MODE_CONTENT_TYPE_CINEMA = 6
> > + * Content type is cinema, itc bit is set.
> > + * - DRM_MODE_CONTENT_TYPE_GAME = 7
> > + * Content type is game, itc bit is set.
>
> I wonder if we're trying to document the uabi or the internals here.
> If we are interested in the uabi, then we should document the enum
> value strings here. If on the other hand we're trying to document the
> internal details then we should keep the DRM_CONTENT_TYPE_* stuff.
> Maybe we want both? The raw numbers I think we should just throw out.
> While they do have some specific meaning in the case (matching the
> bits
> in the infoframe), I'm not sure that's important enough to include in
> the docs. We could add a comment next to the DRM_MODE_CONTENT_TYPE_*
> definitions.
>
> Looks like the content protection prop is documenting the internals
> only
> as well. Hmm. Actually it looks like those things are defined in the
> uapi
> header. Oh and the scaling mode prop also does that. This is all
> setting
> a rather bad example for userspace. Or maybe we've given up on the
> "the
> string is the uabi" notion entirely?
>
I can just throw away the numbers from that doc, but add a bit of more
clarification in the definition itself. If this is fine with everybody.
--
Best Regards,
Lisovskiy Stanislav
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-04-30 6:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 7:34 [PATCH v7 0/2] Enabling content-type setting for HDMI displays StanLis
2018-04-23 7:34 ` [PATCH v7 1/2] drm: content-type property for HDMI connector StanLis
2018-04-23 13:45 ` Lisovskiy, Stanislav
2018-04-27 10:42 ` [Intel-gfx] " Lisovskiy, Stanislav
2018-04-27 19:40 ` Ville Syrjälä
2018-04-30 6:28 ` Lisovskiy, Stanislav [this message]
2018-04-30 15:00 ` Daniel Vetter
2018-05-02 8:09 ` Lisovskiy, Stanislav
2018-05-02 8:15 ` Daniel Vetter
2018-05-02 9:08 ` Lisovskiy, Stanislav
2018-05-02 11:08 ` Daniel Vetter
2018-05-02 11:19 ` Lisovskiy, Stanislav
2018-04-23 7:34 ` [PATCH v7 2/2] i915: " StanLis
2018-04-25 8:02 ` [PATCH v7 0/2] Enabling content-type setting for HDMI displays Lisovskiy, Stanislav
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=537186c3f7011a27b083d4dd035b6fe18241f32e.camel@intel.com \
--to=stanislav.lisovskiy@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--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