Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Cc: <suraj.kandpal@intel.com>, <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH 0/4] Use num of pipes in joiner helpers
Date: Wed, 18 Sep 2024 17:40:58 +0530	[thread overview]
Message-ID: <b982c590-ae9c-4930-afa9-cd232290aab5@intel.com> (raw)
In-Reply-To: <20240916102836.2149012-1-ankit.k.nautiyal@intel.com>


On 9/16/2024 3:58 PM, Ankit Nautiyal wrote:
> Currently few joiner helpers pass joiner flag to represent if bigjoiner
> is used. To scale this for ultrajoiner, enhance these helpers to use num
> of pipes instead of joiner flag. This new approach is adaptable to various
> joiner configurations with 1 (no joiner), 2 (big joiner) and forthcoming 4
> (ultrajoiner) pipes.
>
> This patch series is a spin off from original series for ultrajoiner
> basic functionality [1]. Few of the preparatory patches are taken here for
> review and merge before the other core patches of the series.
>
> [1] https://patchwork.freedesktop.org/series/133800/
>
> Rev2:
> -Use intel_crtc_num_joined_pipes early (Ville)
> Rev3:
> -Rebase

Thanks for the reviews, patches pushed to drm-intel-next.

Regards,

Ankit


>
> Ankit Nautiyal (4):
>    drm/i915/display: Simplify intel_joiner_num_pipes and its usage
>    drm/i915/display: Use joined pipes in intel_dp_joiner_needs_dsc
>    drm/i915/display: Use joined pipes in intel_mode_valid_max_plane_size
>    drm/i915/display: Use joined pipes in dsc helpers for slices, bpp
>
>   drivers/gpu/drm/i915/display/intel_display.c | 22 +++++-----
>   drivers/gpu/drm/i915/display/intel_display.h |  3 +-
>   drivers/gpu/drm/i915/display/intel_dp.c      | 42 ++++++++++++--------
>   drivers/gpu/drm/i915/display/intel_dp.h      |  7 ++--
>   drivers/gpu/drm/i915/display/intel_dp_mst.c  | 20 +++++++---
>   drivers/gpu/drm/i915/display/intel_dsi.c     |  2 +-
>   drivers/gpu/drm/i915/display/intel_hdmi.c    |  2 +-
>   7 files changed, 59 insertions(+), 39 deletions(-)
>

  parent reply	other threads:[~2024-09-18 12:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16 10:28 [PATCH 0/4] Use num of pipes in joiner helpers Ankit Nautiyal
2024-09-16 10:28 ` [PATCH 1/4] drm/i915/display: Simplify intel_joiner_num_pipes and its usage Ankit Nautiyal
2024-09-16 10:28 ` [PATCH 2/4] drm/i915/display: Use joined pipes in intel_dp_joiner_needs_dsc Ankit Nautiyal
2024-09-16 10:28 ` [PATCH 3/4] drm/i915/display: Use joined pipes in intel_mode_valid_max_plane_size Ankit Nautiyal
2024-09-16 10:28 ` [PATCH 4/4] drm/i915/display: Use joined pipes in dsc helpers for slices, bpp Ankit Nautiyal
2024-09-16 14:24 ` ✗ Fi.CI.SPARSE: warning for Use num of pipes in joiner helpers (rev3) Patchwork
2024-09-16 14:43 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-09-17  7:08 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-17 13:44 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-09-17 15:01 ` ✓ Fi.CI.IGT: success " Patchwork
2024-09-18 12:10 ` Nautiyal, Ankit K [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-12 11:43 [PATCH 0/4] Use num of pipes in joiner helpers Ankit Nautiyal

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=b982c590-ae9c-4930-afa9-cd232290aab5@intel.com \
    --to=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=suraj.kandpal@intel.com \
    --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