dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>,
Cc: manasi.d.navare@intel.com, vinod.govindapillai@intel.com,
	dri-devel@lists.freedesktop.org, Stanislav.Lisovskiy@intel.com,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
Subject: Re: [PATCH 0/4] Add DP MST DSC support to i915
Date: Tue, 06 Sep 2022 18:42:31 +0300	[thread overview]
Message-ID: <87v8q08q6w.fsf@intel.com> (raw)
In-Reply-To: <20220905085744.29637-1-stanislav.lisovskiy@intel.com>

On Mon, 05 Sep 2022, Stanislav Lisovskiy <stanislav.lisovskiy@intel.com> wrote:
> Currently we have only DSC support for DP SST.

As discussed elsewhere, the patches were modified while applying to
resolve conflicts, leading to further conflicts in drm-tip rebuild, and
eventually drm-tip build breakage. They would've created further
conflicts in linux-next as well as drm-intel-next feature pull (or
drm-next backmerge to drm-intel-next).

I've gone ahead and reverted the commits from drm-intel-next directly,
with Rodrigo's ack. The conflict resolution would have been messy and
generated a bunch of extra work, and we needed to get drm-tip build back
on track ASAP.

We'll need to have a clean baseline to apply the patches on, i.e.
drm-misc-next pull request to drm-next, and drm-next backmerge to


> Stanislav Lisovskiy (4):
>   drm: Add missing DP DSC extended capability definitions.
>   drm/i915: Fix intel_dp_mst_compute_link_config
>   drm/i915: Extract drm_dp_atomic_find_vcpi_slots cycle to separate
>     function
>   drm/i915: Add DSC support to MST path
>  drivers/gpu/drm/i915/display/intel_dp.c     |  73 ++++----
>  drivers/gpu/drm/i915/display/intel_dp.h     |  17 ++
>  drivers/gpu/drm/i915/display/intel_dp_mst.c | 195 ++++++++++++++++++--
>  include/drm/display/drm_dp.h                |  10 +-
>  4 files changed, 237 insertions(+), 58 deletions(-)

Jani Nikula, Intel Open Source Graphics Center

  parent reply	other threads:[~2022-09-06 15:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05  8:57 [PATCH 0/4] Add DP MST DSC support to i915 Stanislav Lisovskiy
2022-09-05  8:57 ` [PATCH 1/4] drm: Add missing DP DSC extended capability definitions Stanislav Lisovskiy
2022-09-06 14:35   ` Jani Nikula
2022-09-06 14:37     ` Jani Nikula
2022-09-06 15:43     ` Jani Nikula
2022-09-06 16:50       ` Lisovskiy, Stanislav
2022-09-06 17:34         ` Jani Nikula
2022-09-05  8:57 ` [PATCH 2/4] drm/i915: Fix intel_dp_mst_compute_link_config Stanislav Lisovskiy
2022-09-05  8:57 ` [PATCH 3/4] drm/i915: Extract drm_dp_atomic_find_vcpi_slots cycle to separate function Stanislav Lisovskiy
2022-09-05  8:57 ` [PATCH 4/4] drm/i915: Add DSC support to MST path Stanislav Lisovskiy
2022-09-06 15:42 ` Jani Nikula [this message]
2022-09-12  8:48   ` [PATCH 0/4] Add DP MST DSC support to i915 Jani Nikula
  -- strict thread matches above, loose matches on Subject: below --
2022-09-13 14:14 Stanislav Lisovskiy
2022-09-01 10:11 Stanislav Lisovskiy
2022-08-29  9:58 Stanislav Lisovskiy
2022-08-26  9:20 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v8q08q6w.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.saarinen@intel.com \
    --cc=manasi.d.navare@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=stanislav.lisovskiy@intel.com \
    --cc=vinod.govindapillai@intel.com \


* 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).