From: sashiko-bot@kernel.org
To: "Luca Leonardo Scorcia" <l.scorcia@gmail.com>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
mfd@lists.linux.dev, linux-gpio@vger.kernel.org, robh@kernel.org,
conor+dt@kernel.org, dmitry.torokhov@gmail.com, lee@kernel.org
Subject: Re: [PATCH RESEND v10 9/9] arm64: dts: mediatek: Add MediaTek MT6392 PMIC dtsi
Date: Tue, 20 Oct 2026 17:47:40 +0000 [thread overview]
Message-ID: <sashiko-outbox-179444@kernel.org> (raw)
In-Reply-To: <20261020173556.632798-10-l.scorcia@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] arm64: dts: mediatek: mt6392 pmic fails pwrap_probe() due to missing ID
--
commit 36e8cdb3fad1df2fc1833ecbab6f1f641807e610
Author: Val Packett <val@packett.cool>
arm64: dts: mediatek: Add MediaTek MT6392 PMIC dtsi
This commit adds the mt6392.dtsi device tree include file for the MediaTek
MT6392 PMIC (providing regulator, keys, pinctrl, and RTC nodes) and includes
it in pumpkin-common.dtsi.
> diff --git a/arch/arm64/boot/dts/mediatek/mt6392.dtsi b/arch/arm64/boot/dts/mediatek/mt6392.dtsi
> new file mode 100644
> index 0000000000000..cc4770d70246c
> --- /dev/null
> +++ b/arch/arm64/boot/dts/mediatek/mt6392.dtsi
> @@ -0,0 +1,145 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Copyright (c) 2019 MediaTek Inc.
> + * Copyright (c) 2024 Val Packett <val@packett.cool>
> + * Copyright (c) 2026 Luca Leonardo Scorcia <l.scorcia@gmail.com>
> + */
> +
> +#include <dt-bindings/input/input.h>
> +#include <dt-bindings/regulator/mediatek,mt6392-regulator.h>
> +
> +&pwrap {
> + pmic: pmic {
> + compatible = "mediatek,mt6392";
> + interrupt-controller;
> + #interrupt-cells = <2>;
[Severity: High]
Will pwrap_probe() fail with -EINVAL on boards that include mt6392.dtsi?
In drivers/soc/mediatek/mtk-pmic-wrap.c, pwrap_probe() matches the child PMIC
node of pwrap against of_slave_match_tbl:
drivers/soc/mediatek/mtk-pmic-wrap.c:pwrap_probe() {
...
if (np->child)
of_slave_id = of_match_node(of_slave_match_tbl, np->child);
if (!of_slave_id) {
dev_dbg(&pdev->dev, "slave pmic should be defined in dts\n");
return -EINVAL;
}
...
}
However, of_slave_match_tbl in drivers/soc/mediatek/mtk-pmic-wrap.c only
lists:
static const struct of_device_id of_slave_match_tbl[] = {
{ .compatible = "mediatek,mt6323", .data = &pmic_mt6323 },
{ .compatible = "mediatek,mt6331", .data = &pmic_mt6331 },
{ .compatible = "mediatek,mt6351", .data = &pmic_mt6351 },
{ .compatible = "mediatek,mt6357", .data = &pmic_mt6357 },
{ .compatible = "mediatek,mt6358", .data = &pmic_mt6358 },
{ .compatible = "mediatek,mt6359", .data = &pmic_mt6359 },
{ .compatible = "mediatek,mt6380-regulator", .data = &pmic_mt6380 },
{ .compatible = "mediatek,mt6397", .data = &pmic_mt6397 },
{ /* sentinel */ }
};
Because there is no "mediatek,mt6392" entry in of_slave_match_tbl (and the
pmic node has no fallback compatible string), of_slave_id is NULL and
pwrap_probe() aborts before initializing the regmap or calling
of_platform_populate() for the PMIC and its subdevices.
[ ... ]
> diff --git a/arch/arm64/boot/dts/mediatek/pumpkin-common.dtsi b/arch/arm64/boot/dts/mediatek/pumpkin-common.dtsi
> index 805fb82138a80..b19d5792bd896 100644
> --- a/arch/arm64/boot/dts/mediatek/pumpkin-common.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/pumpkin-common.dtsi
> @@ -6,6 +6,8 @@
>
> #include <dt-bindings/gpio/gpio.h>
>
> +#include "mt6392.dtsi"
> +
> / {
[ ... ]
> @@ -160,6 +162,11 @@ &i2c2 {
> status = "okay";
> };
>
> +&pmic {
> + interrupt-parent = <&pio>;
> + interrupts = <28 IRQ_TYPE_LEVEL_HIGH>;
> +};
> +
> &uart0 {
> status = "okay";
> };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261020173556.632798-1-l.scorcia@gmail.com?part=9
prev parent reply other threads:[~2026-10-20 17:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 17:33 [PATCH RESEND v10 0/9] Add support for MT6392 PMIC Luca Leonardo Scorcia
2026-10-20 17:33 ` [PATCH RESEND v10 1/9] dt-bindings: mfd: mt6397: Add " Luca Leonardo Scorcia
2026-10-21 2:14 ` Rob Herring (Arm)
2026-10-21 2:32 ` Rob Herring
2026-10-21 6:35 ` Luca Leonardo Scorcia
2026-10-21 6:07 ` Krzysztof Kozlowski
2026-10-21 6:42 ` Luca Leonardo Scorcia
2026-10-21 6:45 ` Krzysztof Kozlowski
2026-10-21 7:06 ` Luca Leonardo Scorcia
2026-10-20 17:33 ` [PATCH RESEND v10 2/9] dt-bindings: input: mtk-pmic-keys: Add MT6392 PMIC keys Luca Leonardo Scorcia
2026-10-20 17:33 ` [PATCH RESEND v10 3/9] regulator: dt-bindings: Add MediaTek MT6392 PMIC Luca Leonardo Scorcia
2026-10-20 17:33 ` [PATCH RESEND v10 4/9] mfd: mt6397: Use MFD_CELL_* to describe sub-devices Luca Leonardo Scorcia
2026-10-20 17:33 ` [PATCH RESEND v10 5/9] mfd: mt6397: Add support for MT6392 PMIC Luca Leonardo Scorcia
2026-10-20 17:33 ` [PATCH RESEND v10 6/9] input: keyboard: mtk-pmic-keys: Add MT6392 support Luca Leonardo Scorcia
2026-10-20 17:33 ` [PATCH RESEND v10 7/9] pinctrl: mediatek: mt6397: Add MediaTek MT6392 Luca Leonardo Scorcia
2026-10-20 17:33 ` [PATCH RESEND v10 8/9] regulator: Add MediaTek MT6392 regulator Luca Leonardo Scorcia
2026-10-20 17:48 ` sashiko-bot
2026-10-20 17:33 ` [PATCH RESEND v10 9/9] arm64: dts: mediatek: Add MediaTek MT6392 PMIC dtsi Luca Leonardo Scorcia
2026-10-20 17:47 ` 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-179444@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=l.scorcia@gmail.com \
--cc=lee@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=mfd@lists.linux.dev \
--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