All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Ishu Brar" <patches@brar.si>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 6/6] drm/msm: mdss: Add SM7250 support
Date: Thu, 12 Nov 2026 04:50:13 +0000	[thread overview]
Message-ID: <sashiko-outbox-210396@kernel.org> (raw)
In-Reply-To: <20261112-dpu-sm7250-v2-6-8e925a3a8a7d@brar.si>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [High] drm/msm: mdss: missing qcom,sm7250 UBWC config breaks
  msm_mdss_init()
--

commit d4f3819a63c8f3f76b2bc3a988c5686bff7ac892
Author: Ishu Brar <patches@brar.si>

drm/msm: mdss: Add SM7250 support

This commit adds the qcom,sm7250-mdss compatible entry to mdss_dt_match.

> diff --git a/drivers/gpu/drm/msm/msm_mdss.c b/drivers/gpu/drm/msm/msm_mdss.c
> index 259d362475c81..8097e8f9144e4 100644
> --- a/drivers/gpu/drm/msm/msm_mdss.c
> +++ b/drivers/gpu/drm/msm/msm_mdss.c
> @@ -563,6 +563,7 @@ static const struct of_device_id mdss_dt_match[] = {
>  	{ .compatible = "qcom,sm6350-mdss", .data = &data_76k8 },
>  	{ .compatible = "qcom,sm6375-mdss", .data = &data_76k8 },
>  	{ .compatible = "qcom,sm7150-mdss", .data = &data_76k8 },
> +	{ .compatible = "qcom,sm7250-mdss", .data = &data_76k8 },
>  	{ .compatible = "qcom,sm8150-mdss", .data = &data_76k8 },
>  	{ .compatible = "qcom,sm8250-mdss", .data = &data_76k8 },
>  	{ .compatible = "qcom,sm8350-mdss", .data = &data_74k },

[Severity: High]
Does qcom_ubwc_configs in drivers/soc/qcom/ubwc_config.c also need a
qcom,sm7250 entry?

Both mdss_probe() -> msm_mdss_init() and dpu_kms_hw_init() call
qcom_ubwc_config_get_data() and abort on error.  Because qcom_ubwc_configs
has no entry for qcom,sm7250, of_machine_get_match_data() returns NULL and
qcom_ubwc_config_get_data() fails with -EINVAL, preventing MDSS and DPU from
probing on SM7250.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261112-dpu-sm7250-v2-0-8e925a3a8a7d@brar.si?part=6

      reply	other threads:[~2026-11-12  4:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12  4:36 [PATCH v2 0/6] drm/msm/dpu: Add SM7250 display support Ishu Brar via B4 Relay
2026-11-12  4:36 ` Ishu Brar
2026-11-12  4:36 ` [PATCH v2 1/6] dt-bindings: display/msm: dsi-controller-main: Add SM7250 Ishu Brar via B4 Relay
2026-11-12  4:36   ` Ishu Brar
2026-11-12  4:36 ` [PATCH v2 2/6] dt-bindings: display/msm: dpu: Document SM7250 Ishu Brar via B4 Relay
2026-11-12  4:36   ` Ishu Brar
2026-11-12  4:36 ` [PATCH v2 3/6] dt-bindings: display/msm: dp-controller: Add SM7250 Ishu Brar via B4 Relay
2026-11-12  4:36   ` Ishu Brar
2026-11-12 11:12   ` Krzysztof Kozlowski
2026-11-12  4:36 ` [PATCH v2 4/6] dt-bindings: display/msm: Add SM7250 MDSS Ishu Brar via B4 Relay
2026-11-12  4:36   ` Ishu Brar
2026-11-12 11:13   ` Krzysztof Kozlowski
2026-11-12  4:36 ` [PATCH v2 5/6] drm/msm/dpu: Add SM7250 support Ishu Brar via B4 Relay
2026-11-12  4:36   ` Ishu Brar
2026-11-12  4:54   ` sashiko-bot
2026-11-12  4:36 ` [PATCH v2 6/6] drm/msm: mdss: " Ishu Brar via B4 Relay
2026-11-12  4:36   ` Ishu Brar
2026-11-12  4:50   ` sashiko-bot [this message]

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=sashiko-outbox-210396@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=patches@brar.si \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.