From: sashiko-bot@kernel.org
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-media@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v7 1/2] arm64: dts: qcom: sm8250: sort out Iris power domains
Date: Thu, 04 Jun 2026 16:42:10 +0000 [thread overview]
Message-ID: <20260604164210.B7B9F1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260604-iris-venus-fix-sm8250-v7-1-7bd2f0e5bae8@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] The newly added 'mmcx' power domain is ignored by the 'venus' and 'iris' drivers, leaving MMCX unvoted and incorrectly lowering the MX domain voltage vote.
- [Low] Adding 'mmcx' to the 'power-domains' array without updating the dt-bindings schema causes a validation error.
--
commit 3e49b17a27a634436ceefec5a26bbe9a8584818e
Author: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
arm64: dts: qcom: sm8250: sort out Iris power domains
This commit adds the MMCX power domain and required-opps to the venus
device node for the SM8250 platform.
> diff --git a/arch/arm64/boot/dts/qcom/sm8250.dtsi b/arch/arm64/boot/dts/qcom/sm8250.dtsi
> index 7076720413ab2..6150380795b81 100644
> --- a/arch/arm64/boot/dts/qcom/sm8250.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8250.dtsi
> @@ -4326,8 +4326,12 @@ venus: video-codec@aa00000 {
> interrupts = <GIC_SPI 174 IRQ_TYPE_LEVEL_HIGH>;
> power-domains = <&videocc MVS0C_GDSC>,
> <&videocc MVS0_GDSC>,
> - <&rpmhpd RPMHPD_MX>;
> - power-domain-names = "venus", "vcodec0", "mx";
> + <&rpmhpd RPMHPD_MX>,
> + <&rpmhpd RPMHPD_MMCX>;
> + power-domain-names = "venus",
> + "vcodec0",
> + "mx",
> + "mmcx";
[Severity: Low]
Does adding mmcx here cause a dt-bindings validation error?
Looking at Documentation/devicetree/bindings/media/qcom,sm8250-venus.yaml,
the schema strictly enforces maxItems: 3 for power-domains and requires
exact matches for power-domain-names (venus, vcodec0, mx).
[ ... ]
> @@ -4353,22 +4357,26 @@ venus_opp_table: opp-table {
>
> opp-720000000 {
> opp-hz = /bits/ 64 <720000000>;
> - required-opps = <&rpmhpd_opp_low_svs>;
> + required-opps = <&rpmhpd_opp_svs>,
> + <&rpmhpd_opp_low_svs>;
> };
[Severity: High]
Will this result in MMCX remaining unvoted and MX receiving a lowered
voltage vote?
The venus and iris drivers both hardcode their OPP power domains to only
request mx:
drivers/media/platform/qcom/venus/core.c:sm8250_res
.opp_pmdomain = (const char *[]) { "mx" },
drivers/media/platform/qcom/iris/iris_platform_gen1.c:sm8250_opp_pd_table
static const char * const sm8250_opp_pd_table[] = { "mx" };
Because mmcx is never requested via devm_pm_domain_attach_list(), the OPP
framework assigns the first required-opps entry to mx, and silently skips
the second entry since it maps to an unattached device.
This appears to leave MMCX unmanaged while incorrectly lowering the MX
domain vote.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260604-iris-venus-fix-sm8250-v7-0-7bd2f0e5bae8@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-06-04 16:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 16:22 [PATCH v7 0/2] arm64: dts: qcom: fix power domain handling on SM8250 Dmitry Baryshkov
2026-06-04 16:22 ` [PATCH v7 1/2] arm64: dts: qcom: sm8250: sort out Iris power domains Dmitry Baryshkov
2026-06-04 16:42 ` sashiko-bot [this message]
2026-06-09 6:00 ` Vishnu Reddy
2026-06-10 12:20 ` Konrad Dybcio
2026-06-10 12:24 ` Konrad Dybcio
2026-06-10 13:34 ` Dmitry Baryshkov
2026-06-10 13:52 ` Konrad Dybcio
2026-06-12 7:55 ` Dmitry Baryshkov
2026-06-16 11:52 ` Konrad Dybcio
2026-06-04 16:22 ` [PATCH v7 2/2] arm64: dts: qcom: sm8250: correct frequencies in the Iris OPP table Dmitry Baryshkov
2026-06-09 5:47 ` Vishnu Reddy
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=20260604164210.B7B9F1F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=linux-media@vger.kernel.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