From: Marius Vlad <marius.c.vlad@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH i-g-t v3 0/3] 4K and audio HDMI EDID injection
Date: Wed, 23 Mar 2016 19:09:35 +0200 [thread overview]
Message-ID: <1458752978-18866-1-git-send-email-marius.c.vlad@intel.com> (raw)
This series adds support for HDMI injection (4K and audio), and it needs
https://lists.freedesktop.org/archives/intel-gfx/2016-March/090698.html.
v3:
- extend kms_force_connector_basic instead of creating a new test.
- upon reloading the driver the number of outputs increases so we need
to make sure we're checking all of them.
v2:
- Use a proper subject.
- Added speaker data block and check that we get indeed a valid ELD for audio
injection, otherwise we can not tell if the audio injection succeeded.
Marius Vlad (3):
lib/igt_kms: Add helpers for injecting 4k HDMI EDID, and HDMI-capable
audio.
lib/igt_kms: Allow forcing HDMI connectors and remove checks against
BDW and HSW.
tests/kms_force_connector_basic: Add HDMI and audio EDID injection.
lib/igt_kms.c | 193 +++++++++++++++++++++++++++++--
lib/igt_kms.h | 2 +
tests/kms_force_connector_basic.c | 236 +++++++++++++++++++++++++++++++++++++-
3 files changed, 417 insertions(+), 14 deletions(-)
--
2.5.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-03-23 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 17:09 Marius Vlad [this message]
2016-03-23 17:09 ` [PATCH i-g-t 1/3] lib/igt_kms: Add helpers for injecting 4k HDMI EDID, and HDMI-capable audio Marius Vlad
2016-03-23 17:09 ` [PATCH i-g-t 2/3] lib/igt_kms: Allow forcing HDMI connectors and remove checks against BDW and HSW Marius Vlad
2016-03-23 17:09 ` [PATCH i-g-t 3/3] tests/kms_force_connector_basic: Add HDMI and audio EDID injection Marius Vlad
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=1458752978-18866-1-git-send-email-marius.c.vlad@intel.com \
--to=marius.c.vlad@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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).