From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com, ville.syrjala@linux.intel.com
Subject: [PATCH v2 0/2] drm/i915: fix MSO vs. joiner issue
Date: Fri, 14 Jun 2024 13:16:02 +0300 [thread overview]
Message-ID: <cover.1718360103.git.jani.nikula@intel.com> (raw)
This superseeds and includes [1].
BR,
Jani.
[1] https://lore.kernel.org/r/20240613150424.262567-1-jani.nikula@intel.com
Jani Nikula (2):
drm/i915/mso: using joiner is not possible with eDP MSO
drm/i915/dsc: don't mess up splitter state in joiner or dsc config
drivers/gpu/drm/i915/display/intel_ddi.c | 5 ++---
drivers/gpu/drm/i915/display/intel_display_debugfs.c | 8 ++++++--
drivers/gpu/drm/i915/display/intel_dp.c | 4 ++++
drivers/gpu/drm/i915/display/intel_vdsc.c | 12 +++++++++---
drivers/gpu/drm/i915/display/intel_vdsc_regs.h | 1 +
5 files changed, 22 insertions(+), 8 deletions(-)
--
2.39.2
next reply other threads:[~2024-06-14 10:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 10:16 Jani Nikula [this message]
2024-06-14 10:16 ` [PATCH v2 1/2] drm/i915/mso: using joiner is not possible with eDP MSO Jani Nikula
2024-06-14 11:41 ` Ville Syrjälä
2024-06-14 14:01 ` Jani Nikula
2024-06-14 10:16 ` [PATCH v2 2/2] drm/i915/dsc: don't mess up splitter state in joiner or dsc config Jani Nikula
2024-06-14 11:47 ` Ville Syrjälä
2024-06-14 14:17 ` Jani Nikula
2024-06-14 14:29 ` Ville Syrjälä
2024-06-14 11:16 ` ✓ CI.Patch_applied: success for drm/i915: fix MSO vs. joiner issue Patchwork
2024-06-14 11:16 ` ✗ CI.checkpatch: warning " Patchwork
2024-06-14 11:17 ` ✓ CI.KUnit: success " Patchwork
2024-06-14 11:29 ` ✓ CI.Build: " Patchwork
2024-06-14 11:31 ` ✗ CI.Hooks: failure " Patchwork
2024-06-14 11:33 ` ✗ CI.checksparse: warning " Patchwork
2024-06-14 11:55 ` ✓ CI.BAT: success " Patchwork
2024-06-14 20:11 ` ✓ CI.FULL: " 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.1718360103.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=ville.syrjala@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