From: sashiko-bot@kernel.org
To: "Muzaffer Kadir" <muzafferkadir@mainlining.org>
Cc: mfd@lists.linux.dev, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org, lee@kernel.org,
dmitry.torokhov@gmail.com, robh@kernel.org,
linux-clk@vger.kernel.org, conor+dt@kernel.org,
linux-input@vger.kernel.org
Subject: Re: [PATCH v2 13/19] drm: msm: mdp5: Add MDP5 configuration for MSM8952
Date: Wed, 16 Sep 2026 14:43:38 +0000 [thread overview]
Message-ID: <20260916144339.104E41F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260916-msm8952-initial-support-v2-13-798c2602dde1@mainlining.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] drm/msm: hardware corruption due to zero-initialized LM3 base address
--
commit f01ed8464ded4b4b827835f9551a26ed60e5dded
Author: Muzaffer Kadir <muzafferkadir@mainlining.org>
drm: msm: mdp5: Add MDP5 configuration for MSM8952
This commit adds the mdp5_cfg_hw entry for MDP5 version v1.12 found on
the MSM8952.
> diff --git a/drivers/gpu/drm/msm/disp/mdp5/mdp5_cfg.c b/drivers/gpu/drm/msm/disp/mdp5/mdp5_cfg.c
> index 7c91fc1915f39..d34c94d6f7e2e 100644
> --- a/drivers/gpu/drm/msm/disp/mdp5/mdp5_cfg.c
> +++ b/drivers/gpu/drm/msm/disp/mdp5/mdp5_cfg.c
> @@ -744,6 +744,86 @@ static const struct mdp5_cfg_hw msm8x76_config = {
> .max_clk = 360000000,
> };
>
> +static const struct mdp5_cfg_hw msm8952_config = {
> + .name = "msm8952",
[ ... ]
> + .lm = {
> + .count = 2,
> + .base = { 0x44000, 0x47000 },
> + .instances = {
> + { .id = 0, .pp = 0, .dspp = 0,
> + .caps = MDP_LM_CAP_DISPLAY, },
> + { .id = 3, .pp = -1, .dspp = -1,
> + .caps = MDP_LM_CAP_WB },
> + },
[Severity: High]
Will this lead to hardware register corruption when LM3 is brought up?
In msm8952_config, the .lm.base array is initialized sequentially as
{ 0x44000, 0x47000 }, which assigns base[0] = 0x44000 and base[1] = 0x47000.
This leaves base[3] implicitly zero-initialized.
However, the second LM instance is defined with .id = 3 (for LM3). When the
driver configures this mixer, it uses lm->id to access the LM registers.
Because base[3] is 0, the driver will mistakenly perform writes to offset 0x0
of the MDP block (which corresponds to top-level registers).
Should designated initializers be used for the base array here, such as
{ [0] = 0x44000, [3] = 0x47000 }?
> + .nb_stages = 8,
> + .max_width = 2048,
> + .max_height = 0xFFFF,
> + },
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260916-msm8952-initial-support-v2-0-798c2602dde1@mainlining.org?part=13
next prev parent reply other threads:[~2026-09-16 14:43 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 14:22 [PATCH v2 00/19] Add Initial Support For MSM8952, Add General Mobile Shamrock Muzaffer Kadir via B4 Relay
2026-09-16 14:22 ` [PATCH v2 01/19] dt-bindings: clock: qcom: Add MSM8952 global clock controller Muzaffer Kadir via B4 Relay
2026-09-16 14:31 ` sashiko-bot
2026-09-18 10:02 ` Krzysztof Kozlowski
[not found] ` <29506e08-9337-487f-af2d-b75f5aa8341e@mainlining.org>
2026-09-18 13:26 ` Krzysztof Kozlowski
2026-09-16 14:22 ` [PATCH v2 02/19] clk: qcom: Add global clock controller driver for MSM8952 Muzaffer Kadir via B4 Relay
2026-09-16 14:44 ` sashiko-bot
2026-09-17 4:19 ` Taniya Das
[not found] ` <a47a1a0e-559b-410c-aa99-9230908c2fe6@mainlining.org>
2026-09-21 8:46 ` Konrad Dybcio
2026-09-16 14:22 ` [PATCH v2 03/19] dt-bindings: nvmem: Add compatible " Muzaffer Kadir via B4 Relay
2026-09-16 14:27 ` sashiko-bot
2026-09-18 10:09 ` Krzysztof Kozlowski
2026-09-16 14:22 ` [PATCH v2 04/19] dt-bindings: power: rpmpd: Add MSM8952 power domains Muzaffer Kadir via B4 Relay
2026-09-16 14:27 ` sashiko-bot
2026-09-16 14:22 ` [PATCH v2 05/19] dt-bindings: mmc: sdhci-msm: Add MSM8952 compatible Muzaffer Kadir via B4 Relay
2026-09-16 14:27 ` sashiko-bot
2026-09-16 14:22 ` [PATCH v2 06/19] dt-bindings: vendor-prefixes: Add General Mobile Muzaffer Kadir via B4 Relay
2026-09-16 14:25 ` sashiko-bot
2026-09-18 10:02 ` Krzysztof Kozlowski
2026-09-16 14:22 ` [PATCH v2 07/19] dt-bindings: arm: qcom: Document MSM8952 SoC binding Muzaffer Kadir via B4 Relay
2026-09-16 14:29 ` sashiko-bot
2026-09-18 10:03 ` Krzysztof Kozlowski
2026-09-16 14:22 ` [PATCH v2 08/19] dt-bindings: iommu: qcom,iommu: Add MSM8952 IOMMU to SMMUv2 compatibles Muzaffer Kadir via B4 Relay
2026-09-16 14:28 ` sashiko-bot
2026-09-16 14:22 ` [PATCH v2 09/19] dt-bindings: mfd: qcom,tcsr: Add compatible for MSM8952 Muzaffer Kadir via B4 Relay
2026-09-16 14:26 ` sashiko-bot
2026-09-24 14:28 ` (subset) " Lee Jones
2026-09-16 14:22 ` [PATCH v2 10/19] dt-bindings: display/msm: qcom, mdp5: Add MSM8952 compatible Muzaffer Kadir via B4 Relay
2026-09-16 14:30 ` sashiko-bot
2026-09-16 14:22 ` [PATCH v2 11/19] dt-bindings: firmware: qcom,scm: Document MSM8952 SCM Muzaffer Kadir via B4 Relay
2026-09-16 14:27 ` sashiko-bot
2026-09-16 14:22 ` [PATCH v2 12/19] dt-bindings: clock: qcom,rpmcc: Add MSM8952 compatible Muzaffer Kadir via B4 Relay
2026-09-16 14:31 ` sashiko-bot
2026-09-16 14:22 ` [PATCH v2 13/19] drm: msm: mdp5: Add MDP5 configuration for MSM8952 Muzaffer Kadir via B4 Relay
2026-09-16 14:43 ` sashiko-bot [this message]
2026-09-16 14:22 ` [PATCH v2 14/19] soc: qcom: ubwc: Add UBWC config " Muzaffer Kadir via B4 Relay
2026-09-16 14:27 ` sashiko-bot
2026-09-16 14:22 ` [PATCH v2 15/19] dt-bindings: thermal: tsens: Add MSM8952 Muzaffer Kadir via B4 Relay
2026-09-16 14:31 ` sashiko-bot
2026-09-16 14:22 ` [PATCH v2 16/19] thermal: qcom: tsens: Add support for MSM8952 tsens Muzaffer Kadir via B4 Relay
2026-09-16 14:34 ` sashiko-bot
2026-09-16 14:22 ` [PATCH v2 17/19] arm64: dts: qcom: Add initial support for MSM8952 Muzaffer Kadir via B4 Relay
2026-09-16 14:49 ` sashiko-bot
2026-09-16 14:22 ` [PATCH v2 18/19] dt-bindings: input: touchscreen: goodix: Add binding for GT970 Muzaffer Kadir via B4 Relay
2026-09-16 14:29 ` sashiko-bot
2026-09-16 14:22 ` [PATCH v2 19/19] arm64: dts: qcom: generalmobile-shamrock: new device Muzaffer Kadir via B4 Relay
2026-09-16 14:37 ` sashiko-bot
2026-09-18 10:06 ` Krzysztof Kozlowski
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=20260916144339.104E41F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=lee@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=mfd@lists.linux.dev \
--cc=muzafferkadir@mainlining.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox