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 5/5] drm/msm: mdss: Add SM7250 support
Date: Sat, 31 Oct 2026 08:10:33 +0000 [thread overview]
Message-ID: <sashiko-outbox-191820@kernel.org> (raw)
In-Reply-To: <20261031-dpu-sm7250-v1-5-159f403ec405@brar.si>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] drm/msm: mdss: missing qcom,sm7250 UBWC config breaks msm_mdss_init()
--
commit 0057475d95677bf9a33c044b3beaf8c21ba53ed1
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[]
to enable MDSS support on SM7250 platforms.
> diff --git a/drivers/gpu/drm/msm/msm_mdss.c b/drivers/gpu/drm/msm/msm_mdss.c
> index e69b122f2687a..f619052bbb463 100644
> --- a/drivers/gpu/drm/msm/msm_mdss.c
> +++ b/drivers/gpu/drm/msm/msm_mdss.c
> @@ -562,6 +562,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 },
[Severity: High]
Will mdss_probe() and dpu_kms_hw_init() fail with -EINVAL on SM7250 because
qcom,sm7250 is missing from qcom_ubwc_configs[]?
During probe, mdss_probe() -> msm_mdss_init() requires a valid UBWC
configuration:
drivers/gpu/drm/msm/msm_mdss.c:msm_mdss_init() {
...
msm_mdss->mdss_data = qcom_ubwc_config_get_data();
if (IS_ERR(msm_mdss->mdss_data))
return ERR_CAST(msm_mdss->mdss_data);
...
}
Similarly, dpu_kms_hw_init() in drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
calls qcom_ubwc_config_get_data() and aborts on error:
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c:dpu_kms_hw_init() {
...
dpu_kms->mdss = qcom_ubwc_config_get_data();
if (IS_ERR(dpu_kms->mdss)) {
rc = PTR_ERR(dpu_kms->mdss);
DPU_ERROR("failed to get UBWC config data: %d\n", rc);
goto err_pm_put;
}
...
}
Because DRM_MSM selects QCOM_UBWC_CONFIG, qcom_ubwc_config_get_data() in
drivers/soc/qcom/ubwc_config.c matches the root machine compatible against
qcom_ubwc_configs[] via of_machine_get_match_data() and returns
ERR_PTR(-EINVAL) when no entry is found.
Currently, qcom_ubwc_configs[] only contains entries for qcom,sm7125,
qcom,sm7150, qcom,sm7225, and qcom,sm7325 in the SM7xxx family:
drivers/soc/qcom/ubwc_config.c:
{ .compatible = "qcom,sm7150", .data = &ubwc_2_0_hbb14, },
{ .compatible = "qcom,sm7225", .data = &ubwc_2_0_hbb14, },
{ .compatible = "qcom,sm7325", .data = &ubwc_3_1_hbb14, },
Does qcom_ubwc_configs[] also need a qcom,sm7250 entry so that MDSS and DPU
initialization can succeed on SM7250?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261031-dpu-sm7250-v1-0-159f403ec405@brar.si?part=5
prev parent reply other threads:[~2026-10-31 8:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 7:53 [PATCH 0/5] drm/msm/dpu: Add SM7250 display support Ishu Brar
2026-10-31 7:53 ` Ishu Brar via B4 Relay
2026-10-31 7:53 ` [PATCH 1/5] dt-bindings: display/msm: dsi-controller-main: Add SM7250 Ishu Brar
2026-10-31 7:53 ` Ishu Brar via B4 Relay
2026-10-31 7:53 ` [PATCH 2/5] dt-bindings: display/msm: dpu: Document SM7250 Ishu Brar
2026-10-31 7:53 ` Ishu Brar via B4 Relay
2026-10-31 7:53 ` [PATCH 3/5] dt-bindings: display/msm: Add SM7250 MDSS Ishu Brar
2026-10-31 7:53 ` Ishu Brar via B4 Relay
2026-10-31 7:53 ` [PATCH 4/5] drm/msm/dpu: Add SM7250 support Ishu Brar
2026-10-31 7:53 ` Ishu Brar via B4 Relay
2026-10-31 8:16 ` sashiko-bot
2026-10-31 7:53 ` [PATCH 5/5] drm/msm: mdss: " Ishu Brar
2026-10-31 7:53 ` Ishu Brar via B4 Relay
2026-10-31 8:10 ` 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-191820@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.