From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: StanLis <stanislav.lisovskiy@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 0/2] Enabling content-type setting for HDMI displays.
Date: Thu, 19 Apr 2018 14:34:47 +0300 [thread overview]
Message-ID: <20180419113447.GE17795@intel.com> (raw)
In-Reply-To: <20180419075846.24117-1-stanislav.lisovskiy@intel.com>
On Thu, Apr 19, 2018 at 10:58:44AM +0300, StanLis wrote:
> From: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
>
> Rev 1:
> Added content type setting property to drm_connector(part 1)
> and enabled transmitting it with HDMI AVI infoframes
> for i915(part 2).
>
> Rev 2:
> Moved helper function which attaches content type property
> to the drm core, as was suggested.
> Removed redundant connector state initialization.
>
> Rev 3:
> Removed caps in drm_content_type_enum_list.
> After some discussion it turned out that HDMI Spec 1.4
> was wrongly assuming that IT Content(itc) bit doesn't affect
> Content type states, however itc bit needs to be manupulated
> as well. In order to not expose additional property for itc,
> for sake of simplicity it was decided to bind those together
> in same "content type" property.
Please put these changelogs into the commit messages themselves.
Plenty of examples of that practice in git log -- drivers/gpu/drm
>
> Stanislav Lisovskiy (2):
> drm: content-type property for HDMI connector
> i915: content-type property for HDMI connector
>
> Documentation/gpu/kms-properties.csv | 1 +
> drivers/gpu/drm/drm_atomic.c | 5 +++
> drivers/gpu/drm/drm_connector.c | 51 ++++++++++++++++++++++++++++
> drivers/gpu/drm/drm_edid.c | 2 ++
> drivers/gpu/drm/i915/intel_atomic.c | 1 +
> drivers/gpu/drm/i915/intel_hdmi.c | 4 +++
> include/drm/drm_connector.h | 17 ++++++++++
> include/drm/drm_mode_config.h | 5 +++
> include/uapi/drm/drm_mode.h | 7 ++++
> 9 files changed, 93 insertions(+)
>
> --
> 2.17.0
--
Ville Syrjälä
Intel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-04-19 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 7:58 [PATCH v3 0/2] Enabling content-type setting for HDMI displays StanLis
2018-04-19 7:58 ` [PATCH v3 1/2] drm: content-type property for HDMI connector StanLis
2018-04-19 7:58 ` [PATCH v3 2/2] i915: " StanLis
2018-04-19 11:34 ` 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=20180419113447.GE17795@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stanislav.lisovskiy@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