From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com, dri-devel@lists.freedesktop.org,
rodrigo.vivi@intel.com
Subject: [Intel-gfx] [PATCH v4 0/2] drm/i915: switch DP, HDMI and LVDS to drm_edid
Date: Fri, 1 Jul 2022 11:55:37 +0300 [thread overview]
Message-ID: <cover.1656665533.git.jani.nikula@intel.com> (raw)
The remaining patches to add HF-EEODB support to i915 by switching to
using drm_edid in certain encoders. This depends on the drm_edid work in
drm-misc-next, and either needs to be merged via drm-misc-next, or we'll
need the dependencies merged to drm-intel-next via drm-misc-next pull
request -> drm-next -> backmerge.
Jani Nikula (2):
drm/i915/edid: convert DP, HDMI and LVDS to drm_edid
drm/i915/bios: convert intel_bios_init_panel() to drm_edid
drivers/gpu/drm/i915/display/intel_bios.c | 19 ++---
drivers/gpu/drm/i915/display/intel_bios.h | 4 +-
.../gpu/drm/i915/display/intel_connector.c | 4 +-
.../drm/i915/display/intel_display_types.h | 4 +-
drivers/gpu/drm/i915/display/intel_dp.c | 80 +++++++++++--------
drivers/gpu/drm/i915/display/intel_hdmi.c | 28 ++++---
drivers/gpu/drm/i915/display/intel_lvds.c | 37 +++++----
7 files changed, 99 insertions(+), 77 deletions(-)
--
2.30.2
next reply other threads:[~2022-07-01 8:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 8:55 Jani Nikula [this message]
2022-07-01 8:55 ` [Intel-gfx] [PATCH v4 1/2] drm/i915/edid: convert DP, HDMI and LVDS to drm_edid Jani Nikula
2022-07-01 9:01 ` Jani Nikula
2022-07-01 12:57 ` Ville Syrjälä
2022-07-01 8:55 ` [Intel-gfx] [PATCH v4 2/2] drm/i915/bios: convert intel_bios_init_panel() " Jani Nikula
2022-07-01 9:38 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: switch DP, HDMI and LVDS " Patchwork
2022-07-01 9:59 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-07-02 2:04 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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.1656665533.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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