From: sashiko-bot@kernel.org
To: "Chen-Yu Tsai" <wenst@chromium.org>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
krzk+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 1/6] mfd: dt-bindings: mt6397: Add regulator supplies
Date: Wed, 13 May 2026 19:37:43 +0000 [thread overview]
Message-ID: <20260513193743.CE91BC19425@smtp.kernel.org> (raw)
In-Reply-To: <20260512085358.1693208-2-wenst@chromium.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The LDO regulator `va09` is documented as being powered by two different, independent supply pins in the DT bindings.
--
commit 91d90b748e83ee395e8498f7028062225c991970
Author: Chen-Yu Tsai <wenst@chromium.org>
mfd: dt-bindings: mt6397: Add regulator supplies
On the MT6397 family each buck regulator has a separate supply, and LDOs are
split into various groups with independent supplies. This commit adds
descriptions for all of the MT6359 supplies.
> diff --git a/Documentation/devicetree/bindings/mfd/mediatek,mt6397.yaml b/Documentation/devicetree/bindings/mfd/mediatek,mt6397.yaml
> index 05c121b0cb3d8..9e60536779819 100644
> --- a/Documentation/devicetree/bindings/mfd/mediatek,mt6397.yaml
> +++ b/Documentation/devicetree/bindings/mfd/mediatek,mt6397.yaml
[ ... ]
> @@ -225,12 +225,62 @@ properties:
[ ... ]
> +allOf:
> + - if:
> + properties:
> + "compatible":
> + contains:
> + const: mediatek,mt6359
> + then:
> + properties:
> + vsys-ldo1-supply:
> + description: Supply for LDOs vcn33_[12], vio28, vfe28, vibr
> + vsys-ldo2-supply:
> + description: Supply for LDOs va09, vaux18, vbif28, vxo22, vrfck, vrfck_1,
> + vemc, vsim1, vsim2, vusb
Is it expected for the va09 LDO regulator to be supplied by two different
pins? It is listed here under vsys-ldo2-supply.
[ ... ]
> + vs2-ldo1-supply:
> + description:
> + Supply for LDOs vsram_proc1, vsram_proc2, vsram_others, vsram_md
> + vs2-ldo2-supply:
> + description: Supply for LDOs va09, va12, vcn13, vrf12
It is also listed here under vs2-ldo2-supply.
Subsequent patches in the series (specifically commit regulator: mt6359:
Add regulator supply names) clarify that ldo_va09 is exclusively supplied
by vs2-ldo2. Does this mean the reference to va09 should be removed from
vsys-ldo2-supply?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260512085358.1693208-1-wenst@chromium.org?part=1
next prev parent reply other threads:[~2026-05-13 19:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 8:53 [PATCH v3 0/6] regulator: mt6359: cleanup and add supplies Chen-Yu Tsai
2026-05-12 8:53 ` [PATCH v3 1/6] mfd: dt-bindings: mt6397: Add regulator supplies Chen-Yu Tsai
2026-05-13 19:37 ` sashiko-bot [this message]
2026-05-12 8:53 ` [PATCH v3 2/6] regulator: dt-bindings: mt6359: Drop regulator-name pattern restrictions Chen-Yu Tsai
2026-05-12 8:53 ` [PATCH v3 3/6] regulator: dt-bindings: mt6359: Deprecate bogus vcn33_[12]_* split regulators Chen-Yu Tsai
2026-05-13 19:52 ` sashiko-bot
2026-05-12 8:53 ` [PATCH v3 4/6] regulator: mt6359: const-ify regulator descriptions Chen-Yu Tsai
2026-05-12 8:53 ` [PATCH v3 5/6] regulator: mt6359: Add regulator supply names Chen-Yu Tsai
2026-05-13 20:34 ` sashiko-bot
2026-05-12 8:53 ` [PATCH v3 6/6] regulator: mt6359: Add proper ldo_vcn33_[12] regulators Chen-Yu Tsai
2026-05-13 20:59 ` 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=20260513193743.CE91BC19425@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.