From: Jani Nikula <jani.nikula@linux.intel.com>
To: Nemesa Garg <nemesa.garg@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Nemesa Garg <nemesa.garg@intel.com>
Subject: Re: [PATCH] drm/i915/display: Disable casf with joiner
Date: Mon, 05 Jan 2026 11:23:10 +0200 [thread overview]
Message-ID: <d3e9a0decf1667eff15ab8d663a61a146ae13f02@intel.com> (raw)
In-Reply-To: <20260105091202.203926-1-nemesa.garg@intel.com>
On Mon, 05 Jan 2026, Nemesa Garg <nemesa.garg@intel.com> wrote:
> Currently pipe scaling is not supported with the
> joiner. As casf requires pipe scaling, fail the
> atomic commit whenever joiner comes into picture.
>
> Signed-off-by: Nemesa Garg <nemesa.garg@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_casf.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_casf.c b/drivers/gpu/drm/i915/display/intel_casf.c
> index 95339b496f24..259bc50d5ed8 100644
> --- a/drivers/gpu/drm/i915/display/intel_casf.c
> +++ b/drivers/gpu/drm/i915/display/intel_casf.c
> @@ -116,6 +116,11 @@ int intel_casf_compute_config(struct intel_crtc_state *crtc_state)
> return 0;
> }
>
> + if (crtc_state->joiner_pipes) {
> + drm_WARN(display->drm, 0, "CASF not supported with joiner\n");
With a backtrace?!
> + return -EINVAL;
> + }
> +
> crtc_state->hw.casf_params.casf_enable = true;
>
> /*
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-01-05 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 9:12 [PATCH] drm/i915/display: Disable casf with joiner Nemesa Garg
2026-01-05 9:23 ` Jani Nikula [this message]
2026-01-05 12:19 ` Garg, Nemesa
2026-01-05 9:42 ` ✓ CI.KUnit: success for " Patchwork
2026-01-05 10:16 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-05 11:11 ` ✓ Xe.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=d3e9a0decf1667eff15ab8d663a61a146ae13f02@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=nemesa.garg@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