mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nabige Aala <nabige.aala@oss.qualcomm.com>
To: Mahadevan P <mahadevan.p@oss.qualcomm.com>,
	Rob Clark <robin.clark@oss.qualcomm.com>,
	Dmitry Baryshkov <lumag@kernel.org>,
	Abhinav Kumar <abhinav.kumar@linux.dev>,
	Jessica Zhang <jesszhan0024@gmail.com>,
	Sean Paul <sean@poorly.run>,
	Marijn Suijten <marijn.suijten@somainline.org>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/msm/dpu: advertise linear-only modifiers on platforms without UBWC
Date: Mon, 24 Aug 2026 13:01:26 +0530	[thread overview]
Message-ID: <672f91dd-749a-4448-ab32-50ac064a4b98@oss.qualcomm.com> (raw)
In-Reply-To: <20260819-remove_ubwc-v1-1-5357d5cc517f@oss.qualcomm.com>


On 8/19/2026 4:53 PM, Mahadevan P wrote:
> Certain Qualcomm targets like QCM2290 and Shikra do not have UBWC
> support. On such targets, advertising DRM_FORMAT_MOD_QCOM_COMPRESSED
> in the supported modifier list causes userspace to attempt UBWC
> allocations that the kernel rejects:
>
>    msm_dpu: [drm] *ERROR* unsupported format modifier 500000000000003
>    msm_dpu: [drm] *ERROR* unsupported pixel format: AR24 little-endian
>
> On platforms without UBWC, only advertise DRM_FORMAT_MOD_LINEAR to
> avoid exposing formats that the hardware cannot handle.
>
> Fixes: 71c5c23be874 ("drm/msm/dpu: check ubwc support before adding compressed formats")
> Signed-off-by: Mahadevan P <mahadevan.p@oss.qualcomm.com>
> ---
>   drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c | 10 +++++++++-
>   1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c
> index 7b92082d35a6..c8bd034690cb 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c
> @@ -94,6 +94,11 @@ static const uint64_t supported_format_modifiers[] = {
>   	DRM_FORMAT_MOD_INVALID
>   };
>   
> +static const uint64_t supported_format_modifiers_no_ubwc[] = {
> +	DRM_FORMAT_MOD_LINEAR,
> +	DRM_FORMAT_MOD_INVALID
> +};
> +
>   #define to_dpu_plane(x) container_of(x, struct dpu_plane, base)
>   
>   static struct dpu_kms *_dpu_plane_get_kms(struct drm_plane *plane)
> @@ -1836,7 +1841,10 @@ static struct drm_plane *dpu_plane_init_common(struct drm_device *dev,
>   	pdpu = drmm_universal_plane_alloc(dev, struct dpu_plane, base,
>   				0xff, &dpu_plane_funcs,
>   				format_list, num_formats,
> -				supported_format_modifiers, type, NULL);
> +				(kms->mdss->ubwc_enc_version == 0) ?
> +					supported_format_modifiers_no_ubwc :
> +					supported_format_modifiers,

Can we just pass the NULL here in case no ubwc modifer are supported 
instead of "supported_format_modifier_no_ubwc"?

would not it automatically handled in this function 
__drm_universal_plane_init as default_modifier?

Thanks,

Nabige

> +				type, NULL);
>   	if (IS_ERR(pdpu))
>   		return ERR_CAST(pdpu);
>   
>
> ---
> base-commit: e6664f2b33db9b6811eb4cec109f06cb2b4f458d
> change-id: 20260819-remove_ubwc-0180dfb2908c
>
> Best regards,

  reply	other threads:[~2026-08-24  7:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19 11:23 Mahadevan P
2026-08-24  7:31 ` Nabige Aala [this message]
2026-08-25 15:10   ` Mahadevan P

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=672f91dd-749a-4448-ab32-50ac064a4b98@oss.qualcomm.com \
    --to=nabige.aala@oss.qualcomm.com \
    --cc=abhinav.kumar@linux.dev \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=jesszhan0024@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=mahadevan.p@oss.qualcomm.com \
    --cc=marijn.suijten@somainline.org \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=sean@poorly.run \
    --cc=simona@ffwll.ch \
    /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

all inboxes | Powered by JetHome®