From: Krzysztof Kozlowski <krzk@kernel.org>
To: Luca Leonardo Scorcia <l.scorcia@gmail.com>
Cc: linux-mediatek@lists.infradead.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sen Chu <sen.chu@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
Macpaul Lin <macpaul.lin@mediatek.com>,
Lee Jones <lee@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Linus Walleij <linusw@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Julien Massot <julien.massot@collabora.com>,
Gary Bisson <bisson.gary@gmail.com>,
Louis-Alexis Eyraud <louisalexis.eyraud@collabora.com>,
Val Packett <val@packett.cool>,
Fabien Parent <parent.f@gmail.com>,
Chen Zhong <chen.zhong@mediatek.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v3 3/9] dt-bindings: regulator: Document MediaTek MT6392 PMIC Regulators
Date: Wed, 18 Mar 2026 23:14:16 +0100 [thread overview]
Message-ID: <ad0d1ea1-4c5d-4cfc-af0d-8d843e7e0e9e@kernel.org> (raw)
In-Reply-To: <CAORyz2Laoo4EiLcHZ-ygLiFGW_h8qV7QxqNsMbueM=nov5zH0A@mail.gmail.com>
On 18/03/2026 22:25, Luca Leonardo Scorcia wrote:
>>
>> Drop compatible. Regulator nodes do not have compatibles.
>
> Thanks for this comment. It took me a while to understand what you
> meant as most of the MediaTek PMIC regulator drivers still require the
> compatible node to probe, including MT6397 that was the template for
> this patch. I compared the driver to MT6359 that does not use it and I
> am now working on the driver to not rely on it.
>
>> With this, you can also drop example as it won't be used.
>
> Just to be sure - do you mean remove the compatible attribute from the
> example, or the whole example section?
The entire example because without the compatible it will be no-op.
>
>>> +
>>> +patternProperties:
>>> + "^(buck_)?v(core|proc|sys)$":
>>
>> Nope, underscores are not allowed. Use only hyphens.
>
> Got it. I will actually completely remove the (buck_|ldo_) prefix
> altogether as suggested in another comment.
>
>>> + "^(ldo_)?v(adc18|camio|cn18|io18)$":
>>> + description: LDOs with fixed 1.8V output
>>
>> If fixed, then encode it in the schema - min/max microvolt.
>
> If possible I'd like some clarification here. According to Chen-Yu
> Tsai comment [1], dtsi shouldn't contain voltage constraints. The way
That's odd, because long time in the past I heard that DTS must
absolutely set min/max constraints, because these are real hardware
(board) constraints for each regulator, unlike the generic and broad
ones from the driver.
IOW, driver has what datasheet tells. DTS has what actually should be used.
Also, I did not actually require to make min/max required, just they
have to be specific/constrained.
> I understood this is that electrical constraints are a matter of the
> actual board layout, so if adjustments are needed they have to be in
> the board dts. But you also specify "If fixed", so maybe there's an
> exception to this rule when the constraint is "absolute" and boards
> can't actually set a different value?
Now I am confused. You wrote - LDOs with fixed 1.8V output - so board
cannot set it to 2.0V for example. They are affixed. This regulator
CANNOT physically produce anything else.
At least this is the meaning of the text you wrote.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-18 22:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 18:43 [PATCH v3 0/9] Add support for mt6392 PMIC Luca Leonardo Scorcia
2026-03-17 18:43 ` [PATCH v3 1/9] dt-bindings: mfd: mt6397: Add bindings for MT6392 PMIC Luca Leonardo Scorcia
2026-03-18 7:37 ` Krzysztof Kozlowski
2026-03-18 7:47 ` Krzysztof Kozlowski
2026-03-18 12:39 ` AngeloGioacchino Del Regno
2026-03-17 18:43 ` [PATCH v3 2/9] dt-bindings: input: mtk-pmic-keys: add MT6392 binding definition Luca Leonardo Scorcia
2026-03-18 12:39 ` AngeloGioacchino Del Regno
2026-03-17 18:43 ` [PATCH v3 3/9] dt-bindings: regulator: Document MediaTek MT6392 PMIC Regulators Luca Leonardo Scorcia
2026-03-18 7:43 ` Krzysztof Kozlowski
2026-03-18 21:25 ` Luca Leonardo Scorcia
2026-03-18 22:14 ` Krzysztof Kozlowski [this message]
2026-03-19 4:53 ` Chen-Yu Tsai
2026-03-19 7:23 ` Krzysztof Kozlowski
2026-03-18 12:39 ` AngeloGioacchino Del Regno
2026-03-19 4:56 ` Chen-Yu Tsai
2026-03-17 18:43 ` [PATCH v3 4/9] dt-bindings: pinctrl: mt65xx: Document MT6392 pinctrl Luca Leonardo Scorcia
2026-03-18 12:39 ` AngeloGioacchino Del Regno
2026-03-17 18:43 ` [PATCH v3 5/9] mfd: mt6397: Add support for MT6392 pmic Luca Leonardo Scorcia
2026-03-18 12:39 ` AngeloGioacchino Del Regno
2026-03-26 12:10 ` Lee Jones
2026-03-17 18:43 ` [PATCH v3 6/9] input: keyboard: mtk-pmic-keys: add MT6392 support Luca Leonardo Scorcia
2026-03-18 12:39 ` AngeloGioacchino Del Regno
2026-03-17 18:43 ` [PATCH v3 7/9] regulator: mt6392: Add support for MT6392 regulator Luca Leonardo Scorcia
2026-03-18 12:39 ` AngeloGioacchino Del Regno
2026-03-19 5:04 ` Chen-Yu Tsai
2026-03-17 18:43 ` [PATCH v3 8/9] pinctrl: mediatek: mt6397: Add support for MT6392 variant Luca Leonardo Scorcia
2026-03-18 12:38 ` AngeloGioacchino Del Regno
2026-03-17 18:43 ` [PATCH v3 9/9] arm64: dts: mt6392: add mt6392 PMIC dtsi Luca Leonardo Scorcia
2026-03-18 12:39 ` AngeloGioacchino Del Regno
2026-03-18 13:54 ` Chen-Yu Tsai
2026-03-18 17:22 ` AngeloGioacchino Del Regno
2026-03-26 5:43 ` Chen-Yu Tsai
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=ad0d1ea1-4c5d-4cfc-af0d-8d843e7e0e9e@kernel.org \
--to=krzk@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bisson.gary@gmail.com \
--cc=broonie@kernel.org \
--cc=chen.zhong@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=julien.massot@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=l.scorcia@gmail.com \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=louisalexis.eyraud@collabora.com \
--cc=macpaul.lin@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=parent.f@gmail.com \
--cc=robh@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=sen.chu@mediatek.com \
--cc=val@packett.cool \
/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