intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: jani.saarinen@intel.com, ville.syrjala@linux.intel.com
Subject: Re: [PATCH 1/4] drm/i915: Add some essential functionality for joiners
Date: Wed, 26 Jun 2024 13:23:40 +0300	[thread overview]
Message-ID: <87le2sc89f.fsf@intel.com> (raw)
In-Reply-To: <20240626081842.10614-2-stanislav.lisovskiy@intel.com>

On Wed, 26 Jun 2024, Stanislav Lisovskiy <stanislav.lisovskiy@intel.com> wrote:
> diff --git a/drivers/gpu/drm/i915/display/intel_display.h b/drivers/gpu/drm/i915/display/intel_display.h
> index b0cf6ca70952..bac81b7ab764 100644
> --- a/drivers/gpu/drm/i915/display/intel_display.h
> +++ b/drivers/gpu/drm/i915/display/intel_display.h
> @@ -423,10 +423,14 @@ enum phy intel_port_to_phy(struct drm_i915_private *i915, enum port port);
>  bool is_trans_port_sync_mode(const struct intel_crtc_state *state);
>  bool is_trans_port_sync_master(const struct intel_crtc_state *state);
>  u8 intel_crtc_joined_pipe_mask(const struct intel_crtc_state *crtc_state);
> -bool intel_crtc_is_joiner_secondary(const struct intel_crtc_state *crtc_state);
>  bool intel_crtc_is_joiner_primary(const struct intel_crtc_state *crtc_state);
> +bool intel_crtc_is_joiner_secondary(const struct intel_crtc_state *crtc_state);
> +bool intel_crtc_is_bigjoiner_primary(const struct intel_crtc_state *crtc_state);
> +bool intel_crtc_is_bigjoiner_secondary(const struct intel_crtc_state *crtc_state);
> +bool intel_crtc_is_ultrajoiner(const struct intel_crtc_state *crtc_state);
> +bool intel_crtc_is_ultrajoiner_primary(const struct intel_crtc_state *crtc_state);
>  u8 intel_crtc_joiner_secondary_pipes(const struct intel_crtc_state *crtc_state);
> -struct intel_crtc *intel_primary_crtc(const struct intel_crtc_state *crtc_state);
> +struct intel_crtc *intel_joiner_primary_crtc(const struct intel_crtc_state *crtc_state);
>  bool intel_crtc_get_pipe_config(struct intel_crtc_state *crtc_state);
>  bool intel_pipe_config_compare(const struct intel_crtc_state *current_config,
>  			       const struct intel_crtc_state *pipe_config,

Makes you wonder why most of the joiner stuff has ended up in
intel_display.[ch].

Maybe we should have a dedicated file for the stream splitter/joiner,
with the related things (uncompressed joiner, etc.) moved there from
intel_vdsc.c, leaving that purely for compression.

BR,
Jani.

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-06-26 10:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26  8:18 [PATCH 0/4] Ultrajoiner basic functionality series Stanislav Lisovskiy
2024-06-26  8:18 ` [PATCH 1/4] drm/i915: Add some essential functionality for joiners Stanislav Lisovskiy
2024-06-26 10:23   ` Jani Nikula [this message]
2024-06-26  8:18 ` [PATCH 2/4] drm/i915: Implement hw state readout for ultrajoiner Stanislav Lisovskiy
2024-07-01 19:17   ` Ville Syrjälä
2024-06-26  8:18 ` [PATCH 3/4] drm/i915: Compute config and mode valid changes " Stanislav Lisovskiy
2024-07-03  8:51   ` Nautiyal, Ankit K
2024-07-03 10:02     ` Lisovskiy, Stanislav
2024-07-10  8:37     ` Lisovskiy, Stanislav
2024-07-10 13:28       ` Nautiyal, Ankit K
2024-07-11  8:12         ` Lisovskiy, Stanislav
2024-07-03  8:59   ` Nautiyal, Ankit K
2024-06-26  8:18 ` [PATCH 4/4] drm/i915: Add new abstraction layer to handle pipe order for different joiners Stanislav Lisovskiy
2024-06-26  8:58 ` ✗ Fi.CI.CHECKPATCH: warning for Ultrajoiner basic functionality series (rev4) Patchwork
2024-06-26  9:06 ` ✗ Fi.CI.BAT: 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=87le2sc89f.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.saarinen@intel.com \
    --cc=stanislav.lisovskiy@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;
as well as URLs for NNTP newsgroup(s).