From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: jani.nikula@intel.com, intel-gfx@lists.freedesktop.org,
Iaroslav Boliukin <iam@lach.pw>,
Dmitry Osipenko <dmitry.osipenko@collabora.com>
Subject: [Intel-gfx] [PATCH 0/4] drm/displayid: use primary use case to figure out non-desktop
Date: Thu, 16 Feb 2023 22:44:57 +0200 [thread overview]
Message-ID: <cover.1676580180.git.jani.nikula@intel.com> (raw)
Mostly this is prep work and plumbing for easier use of displayid
structure version and primary use case for parsing the displayid blocks,
but it can be nicely used for figuring out non-desktop too.
Completely untested. :)
BR,
Jani.
Cc: Iaroslav Boliukin <iam@lach.pw>
Cc: Dmitry Osipenko <dmitry.osipenko@collabora.com>
Jani Nikula (4):
drm/displayid: add displayid_get_header() and check bounds better
drm/displayid: return struct displayid_header from
validate_displayid()
drm/displayid: provide access to DisplayID version and primary use
case
drm/edid: update non-desktop use also from DisplayID
drivers/gpu/drm/drm_displayid.c | 62 ++++++++++++++++++++++++++++-----
drivers/gpu/drm/drm_edid.c | 25 +++++++++++++
include/drm/drm_displayid.h | 12 ++++++-
3 files changed, 89 insertions(+), 10 deletions(-)
--
2.34.1
next reply other threads:[~2023-02-16 20:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 20:44 Jani Nikula [this message]
2023-02-16 20:44 ` [Intel-gfx] [PATCH 1/4] drm/displayid: add displayid_get_header() and check bounds better Jani Nikula
2023-02-21 16:27 ` Dmitry Osipenko
2023-02-16 20:44 ` [Intel-gfx] [PATCH 2/4] drm/displayid: return struct displayid_header from validate_displayid() Jani Nikula
2023-02-21 16:27 ` Dmitry Osipenko
2023-02-16 20:45 ` [Intel-gfx] [PATCH 3/4] drm/displayid: provide access to DisplayID version and primary use case Jani Nikula
2023-02-21 16:27 ` Dmitry Osipenko
2023-02-16 20:45 ` [Intel-gfx] [PATCH 4/4] drm/edid: update non-desktop use also from DisplayID Jani Nikula
2023-02-21 16:27 ` Dmitry Osipenko
2023-02-16 23:30 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/displayid: use primary use case to figure out non-desktop Patchwork
2023-02-16 23:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-02-17 10:46 ` [Intel-gfx] [PATCH 5/4] drm/edid: parse Tiled Display Topology Data Block for DisplayID 2.0 Jani Nikula
2023-02-21 16:28 ` Dmitry Osipenko
2023-02-17 13:39 ` [Intel-gfx] ✓ Fi.CI.IGT: success for drm/displayid: use primary use case to figure out non-desktop Patchwork
2023-02-20 15:44 ` [Intel-gfx] [PATCH 0/4] " Dmitry Osipenko
2023-02-21 16:29 ` Dmitry Osipenko
2023-02-27 0:03 ` Dmitry Osipenko
2023-02-27 14:57 ` Jani Nikula
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=cover.1676580180.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=dmitry.osipenko@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=iam@lach.pw \
--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