From: sashiko-bot@kernel.org
To: "Vincent Jardin" <vjardin@free.fr>
Cc: robh@kernel.org, conor+dt@kernel.org,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v6 2/4] dt-bindings: hwmon: pmbus: add MPS MPQ8646
Date: Wed, 29 Jul 2026 22:01:53 +0000 [thread overview]
Message-ID: <20260729220154.3B6021F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260729-mpq8646_v0-v6-2-98848151cdb4@free.fr>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The newly added compatible string 'mps,mpq8646' lacks driver support in the mpq8785 PMBus driver.
--
--- Patch [2]: [PATCH v6 2/4] dt-bindings: hwmon: pmbus: add MPS MPQ8646 ---
commit 341628a3dba9f658492690f20d45d96084eb12d5
Author: Vincent Jardin <vjardin@free.fr>
dt-bindings: hwmon: pmbus: add MPS MPQ8646
This commit adds the mps,mpq8646 compatible string to the existing MPQ8785
device tree schema. The MPQ8646 step-down converter shares the same
constraints for the mps,vout-fb-divider-ratio-permille property as the
mpq8785.
> diff --git a/Documentation/devicetree/bindings/hwmon/pmbus/mps,mpq8785.yaml b/Documentation/devicetree/bindings/hwmon/pmbus/mps,mpq8785.yaml
> index 90970a0433e95..d7a32fb3b7af6 100644
> --- a/Documentation/devicetree/bindings/hwmon/pmbus/mps,mpq8785.yaml
> +++ b/Documentation/devicetree/bindings/hwmon/pmbus/mps,mpq8785.yaml
> @@ -18,6 +18,7 @@ properties:
> - mps,mpm3695
> - mps,mpm3695-25
> - mps,mpm82504
> + - mps,mpq8646
[Severity: Medium]
Should the corresponding driver (drivers/hwmon/pmbus/mpq8785.c) also be
updated to match this new compatible string?
Because the DT schema specifies the compatible string as an enum rather than
allowing a fallback (e.g. to "mps,mpq8785"), it appears the MPQ8646 device
will fail to probe. The OF match table in mpq8785_of_match currently lacks
an entry for this new hardware:
static const struct of_device_id __maybe_unused mpq8785_of_match[] = {
{ .compatible = "mps,mpm3695", .data = (void *)mpm3695 },
{ .compatible = "mps,mpm3695-25", .data = (void *)mpm3695_25 },
{ .compatible = "mps,mpm82504", .data = (void *)mpm82504 },
{ .compatible = "mps,mpq8785", .data = (void *)mpq8785 },
{ }
};
The I2C ID table in mpq8785_id is similarly missing an "mpq8646" entry.
Without these additions, will a device instantiated via this new standalone
compatible string be completely ignored by the driver?
> - mps,mpq8785
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260729-mpq8646_v0-v6-0-98848151cdb4@free.fr?part=2
next prev parent reply other threads:[~2026-07-29 22:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 21:51 [PATCH v6 0/4] hwmon: pmbus: add MPS MPQ8646 support Vincent Jardin via B4 Relay
2026-07-29 21:51 ` [PATCH v6 1/4] hwmon: (pmbus/core) export pmbus_check_and_notify_faults() Vincent Jardin via B4 Relay
2026-07-29 22:01 ` sashiko-bot
2026-07-29 21:51 ` [PATCH v6 2/4] dt-bindings: hwmon: pmbus: add MPS MPQ8646 Vincent Jardin via B4 Relay
2026-07-29 22:01 ` sashiko-bot [this message]
2026-07-29 21:51 ` [PATCH v6 3/4] hwmon: pmbus: add MPQ8646 driver Vincent Jardin via B4 Relay
2026-07-29 22:05 ` sashiko-bot
2026-07-29 21:51 ` [PATCH v6 4/4] hwmon: pmbus: mpq8646: gate the writes Vincent Jardin via B4 Relay
2026-07-29 22:07 ` 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=20260729220154.3B6021F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vjardin@free.fr \
/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