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 5/6] drm/msm/dpu: Add SM7250 support
Date: Thu, 12 Nov 2026 04:54:04 +0000	[thread overview]
Message-ID: <sashiko-outbox-210400@kernel.org> (raw)
In-Reply-To: <20261112-dpu-sm7250-v2-5-8e925a3a8a7d@brar.si>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [High] drm/msm/dpu: missing qcom,sm7250 in qcom_ubwc_configs breaks
  probe
--

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

drm/msm/dpu: Add SM7250 support

This commit adds DPU 6.1 hardware catalog definitions and device tree match
data for the Qualcomm SM7250 platform.

> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
> index 1b6286dccfc00..908d401ec4020 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
> @@ -1506,6 +1506,7 @@ static const struct of_device_id dpu_dt_match[] = {
>  	{ .compatible = "qcom,sm6350-dpu", .data = &dpu_sm6350_cfg, },
>  	{ .compatible = "qcom,sm6375-dpu", .data = &dpu_sm6375_cfg, },
>  	{ .compatible = "qcom,sm7150-dpu", .data = &dpu_sm7150_cfg, },
> +	{ .compatible = "qcom,sm7250-dpu", .data = &dpu_sm7250_cfg, },

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

During probe, msm_mdss_init() and dpu_kms_hw_init() call
qcom_ubwc_config_get_data(), which looks up the machine root compatible in
qcom_ubwc_configs via of_machine_get_match_data().  Without a matching
"qcom,sm7250" entry in qcom_ubwc_configs, qcom_ubwc_config_get_data()
returns ERR_PTR(-EINVAL) and display initialization on SM7250 fails.

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

  reply	other threads:[~2026-11-12  4:54 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
2026-11-12  4:36 ` Ishu Brar via B4 Relay
2026-11-12  4:36 ` [PATCH v2 1/6] dt-bindings: display/msm: dsi-controller-main: Add SM7250 Ishu Brar
2026-11-12  4:36   ` Ishu Brar via B4 Relay
2026-11-12  4:36 ` [PATCH v2 2/6] dt-bindings: display/msm: dpu: Document SM7250 Ishu Brar
2026-11-12  4:36   ` Ishu Brar via B4 Relay
2026-11-12  4:36 ` [PATCH v2 3/6] dt-bindings: display/msm: dp-controller: Add SM7250 Ishu Brar
2026-11-12  4:36   ` Ishu Brar via B4 Relay
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
2026-11-12  4:36   ` Ishu Brar via B4 Relay
2026-11-12 11:13   ` Krzysztof Kozlowski
2026-11-12  4:36 ` [PATCH v2 5/6] drm/msm/dpu: Add SM7250 support Ishu Brar
2026-11-12  4:36   ` Ishu Brar via B4 Relay
2026-11-12  4:54   ` sashiko-bot [this message]
2026-11-12  4:36 ` [PATCH v2 6/6] drm/msm: mdss: " Ishu Brar
2026-11-12  4:36   ` Ishu Brar via B4 Relay
2026-11-12  4:50   ` sashiko-bot

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-210400@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.