From: Lyude Paul <lyude@redhat.com>
To: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com, manasi.d.navare@intel.com,
jani.saarinen@intel.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/2] Add DP MST DSC support to i915
Date: Wed, 10 Aug 2022 16:02:08 -0400 [thread overview]
Message-ID: <419bcc405fa4b298acb3f167316217bcca9f7c07.camel@redhat.com> (raw)
In-Reply-To: <20220810081753.12075-1-stanislav.lisovskiy@intel.com>
Btw, what's the plan for this? Figured I'd ask since I noticed this on the ML,
nd I'm now finishing up getting the atomic only MST patches I've been working
on merged :)
On Wed, 2022-08-10 at 11:17 +0300, Stanislav Lisovskiy wrote:
> Currently we have only DSC support for DP SST.
>
> Stanislav Lisovskiy (2):
> drm: Add missing DP DSC extended capability definitions.
> drm/i915: Add DSC support to MST path
>
> drivers/gpu/drm/i915/display/intel_dp.c | 76 +++++-----
> drivers/gpu/drm/i915/display/intel_dp.h | 17 +++
> drivers/gpu/drm/i915/display/intel_dp_mst.c | 145 ++++++++++++++++++++
> include/drm/display/drm_dp.h | 10 +-
> 4 files changed, 203 insertions(+), 45 deletions(-)
>
--
Cheers,
Lyude Paul (she/her)
Software Engineer at Red Hat
next prev parent reply other threads:[~2022-08-10 20:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 8:17 [PATCH 0/2] Add DP MST DSC support to i915 Stanislav Lisovskiy
2022-08-10 8:17 ` [PATCH 1/2] drm: Add missing DP DSC extended capability definitions Stanislav Lisovskiy
2022-08-10 8:17 ` [PATCH 2/2] drm/i915: Add DSC support to MST path Stanislav Lisovskiy
2022-08-10 20:02 ` Lyude Paul [this message]
2022-08-11 7:33 ` [PATCH 0/2] Add DP MST DSC support to i915 Lisovskiy, Stanislav
2022-08-11 18:11 ` Navare, Manasi
2022-08-11 19:54 ` Lyude Paul
-- strict thread matches above, loose matches on Subject: below --
2022-08-22 9:40 Stanislav Lisovskiy
2022-08-15 17:35 Stanislav Lisovskiy
2022-04-11 16:25 Stanislav Lisovskiy
2022-03-21 9:10 Stanislav Lisovskiy
2022-03-17 16:33 Stanislav Lisovskiy
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=419bcc405fa4b298acb3f167316217bcca9f7c07.camel@redhat.com \
--to=lyude@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jani.saarinen@intel.com \
--cc=manasi.d.navare@intel.com \
--cc=stanislav.lisovskiy@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;
as well as URLs for NNTP newsgroup(s).