Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Chen-Yu Tsai" <wenst@chromium.org>
Cc: krzk+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v4 5/6] regulator: mt6359: Add regulator supply names
Date: Thu, 14 May 2026 18:34:28 +0000	[thread overview]
Message-ID: <20260514183429.5F56DC2BCB3@smtp.kernel.org> (raw)
In-Reply-To: <20260514091520.2718987-6-wenst@chromium.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The supply name for 'vbbck' in 'mt6359p_regulators' was incorrectly set to 'LDO_VIO18' instead of 'VIO18'.
--

commit c863063b2f41de345a843312e3b866262b280224
Author: Chen-Yu Tsai <wenst@chromium.org>

regulator: mt6359: Add regulator supply names

The MT6359 regulator DT binding defines the supply names for the PMIC.
This commit adds support for them by introducing .supply_name field
settings for each regulator. The LDOs share supplies, while buck
regulators have their own supplies related to their names.

> diff --git a/drivers/regulator/mt6359-regulator.c b/drivers/regulator/mt6359-regulator.c
> index bcf9a476a34e1..46cafe93b24e4 100644
> --- a/drivers/regulator/mt6359-regulator.c
> +++ b/drivers/regulator/mt6359-regulator.c
[ ... ]
> @@ -871,11 +879,11 @@ static const struct mt6359_regulator_info mt6359p_regulators[] = {
>  		   MT6359P_RG_LDO_VM18_EN_ADDR, MT6359P_RG_LDO_VM18_EN_SHIFT,
>  		   MT6359P_DA_VM18_B_EN_ADDR, MT6359P_RG_VM18_VOSEL_ADDR,
>  		   MT6359_RG_VM18_VOSEL_MASK << MT6359_RG_VM18_VOSEL_SHIFT,
>  		   1920),
> -	MT6359_LDO("ldo_vbbck", VBBCK, vbbck_voltages,
> +	MT6359_LDO("ldo_vbbck", VBBCK, "LDO_VIO18", vbbck_voltages,

In mt6359p_regulators, the supply name for vbbck was introduced as "LDO_VIO18",
whereas in mt6359_regulators it is set to "VIO18".

Because the descriptor name for vio18 is "VIO18", the condition
strcmp(desc->supply_name, vio18_name) != 0 in mt6359_regulator_probe() will
evaluate to true for the MT6359P variant on every boot.

This discrepancy triggers the fallback execution path inside the probe loop,
performing an unnecessary devm_kzalloc() to allocate a new regulator_desc and
correct the supply name dynamically.

Should this also be "VIO18" to prevent the permanent, unintended memory
allocation on MT6359P platforms?

>  		   MT6359P_RG_LDO_VBBCK_EN_ADDR, MT6359P_RG_LDO_VBBCK_EN_SHIFT,
>  		   MT6359P_DA_VBBCK_B_EN_ADDR, MT6359P_RG_VBBCK_VOSEL_ADDR,
>  		   MT6359P_RG_VBBCK_VOSEL_MASK << MT6359P_RG_VBBCK_VOSEL_SHIFT,
>  		   480),

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260514091520.2718987-1-wenst@chromium.org?part=5

  reply	other threads:[~2026-05-14 18:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14  9:15 [PATCH v4 0/6] regulator: mt6359: cleanup and add supplies Chen-Yu Tsai
2026-05-14  9:15 ` [PATCH v4 1/6] mfd: dt-bindings: mt6397: Add regulator supplies Chen-Yu Tsai
2026-05-14  9:15 ` [PATCH v4 2/6] regulator: dt-bindings: mt6359: Drop regulator-name pattern restrictions Chen-Yu Tsai
2026-05-14  9:15 ` [PATCH v4 3/6] regulator: dt-bindings: mt6359: Deprecate bogus vcn33_[12]_* split regulators Chen-Yu Tsai
2026-05-14  9:15 ` [PATCH v4 4/6] regulator: mt6359: const-ify regulator descriptions Chen-Yu Tsai
2026-05-14  9:15 ` [PATCH v4 5/6] regulator: mt6359: Add regulator supply names Chen-Yu Tsai
2026-05-14 18:34   ` sashiko-bot [this message]
2026-05-14  9:15 ` [PATCH v4 6/6] regulator: mt6359: Add proper ldo_vcn33_[12] regulators Chen-Yu Tsai
2026-05-14 19:13   ` 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=20260514183429.5F56DC2BCB3@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=wenst@chromium.org \
    /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