dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: StanLis <stanislav.lisovskiy@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@linux.intel.com
Subject: [PATCH v2 0/2] Enabling content-type setting for HDMI displays.
Date: Wed, 18 Apr 2018 19:49:02 +0300	[thread overview]
Message-ID: <20180418164904.24145-1-stanislav.lisovskiy@intel.com> (raw)

From: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>

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.

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         |  4 +++
 drivers/gpu/drm/drm_connector.c      | 50 ++++++++++++++++++++++++++++
 drivers/gpu/drm/drm_edid.c           |  1 +
 drivers/gpu/drm/i915/intel_atomic.c  |  1 +
 drivers/gpu/drm/i915/intel_hdmi.c    |  3 ++
 include/drm/drm_connector.h          | 11 ++++++
 include/drm/drm_mode_config.h        |  5 +++
 include/uapi/drm/drm_mode.h          |  5 +++
 9 files changed, 81 insertions(+)

-- 
2.17.0

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-04-18  7:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-18 16:49 StanLis [this message]
2018-04-18 16:49 ` [PATCH v2 1/2] drm: content-type property for HDMI connector StanLis
2018-04-18 11:50   ` Jani Nikula
2018-04-18 12:06     ` Lisovskiy, Stanislav
2018-04-18 16:49 ` [PATCH v2 2/2] i915: " StanLis
  -- strict thread matches above, loose matches on Subject: below --
2018-04-18 16:51 [PATCH v2 0/2] Enabling content-type setting for HDMI displays StanLis

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=20180418164904.24145-1-stanislav.lisovskiy@intel.com \
    --to=stanislav.lisovskiy@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@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