From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "zhiyong.tao" <zhiyong.tao@mediatek.com>,
lee.jones@linaro.org, robh+dt@kernel.org, matthias.bgg@gmail.com,
lgirdwood@gmail.com, broonie@kernel.org,
eddie.huang@mediatek.com, a.zummo@towertech.it,
alexandre.belloni@bootlin.com, fshao@chromium.org
Cc: sen.chu@mediatek.com, hui.liu@mediatek.com,
allen-kh.cheng@mediatek.com, hsin-hsiung.wang@mediatek.com,
sean.wang@mediatek.com, macpaul.lin@mediatek.com,
wen.su@mediatek.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
Project_Global_Chrome_Upstream_Group@mediatek.com,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v4] regulator: dt-bindings: mediatek: add mt6366
Date: Tue, 30 Aug 2022 10:42:29 +0300 [thread overview]
Message-ID: <52336b1e-f0b3-c828-48ef-b6977fd90547@linaro.org> (raw)
In-Reply-To: <93bb8a3f7f5567cfe427ed067f68d5c8b6db776d.camel@mediatek.com>
On 29/08/2022 06:25, zhiyong.tao wrote:
>>> +properties:
>>> + compatible:
>>> + const: mediatek,mt6366-regulator
>>
>> This looks incomplete. How does it bind? Further pieces also suggest
>> you
>> send something incomplete.
> ==>
>
> The project dts file(such as 8186-evb.dts) will add the compatible.
> The project dts file is examining.
>
I don't understand this at all. I am not talking about DTS, but about
bindings which look incomplete. Although seeing entire DTS would
probably help understand the context.
(...)
>>
>>
>>> + type: object
>>> + $ref: regulator.yaml#
>>> + unevaluatedProperties: false
>>> +
>>> +required:
>>> + - compatible
>>> + - regulators
>>> +
>>> +additionalProperties: false
>>> +
>>> +examples:
>>> + - |
>>> + pmic {
>>> + compatible = "mediatek,mt6366-regulator";
>>> +
>>> + regulators {
>>> + mt6366_vdram1_reg: buck-vdram1 {
>>
>> Drop the labels here and further. Why you do not have here any
>> regular
>> constraints like min/max voltage?
>
> we will add properties min/max voltag on project dts file.
Example should be complete. DTS does not matter here.
>
>>
>>> + regulator-ramp-delay = <12500>;
>>> + regulator-enable-ramp-delay = <0>;
>>> + regulator-allowed-modes = <0 1>;
>>
>> Where do you explain the meaning of modes?
> support pwm mode.
The question was "Where". Where did you explain them?
(...)
>>> +
>>> + mt6366_vsim2_reg: ldo-vsim2 {
>>> + regulator-enable-ramp-delay = <540>;
>>> + };
>>> +
>>> + mt6366_vcore_sshub_reg: buck-vcore-sshub {
>>
>> Empty node? What does it do?
> just define here, we will add properties on project dts file.
How is it related to bindings?
Best regards,
Krzysztof
prev parent reply other threads:[~2022-08-30 7:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 12:37 [PATCH v4] regulator: dt-bindings: mediatek: add mt6366 Zhiyong Tao
2022-08-23 18:47 ` Nícolas F. R. A. Prado
2022-08-24 13:48 ` Krzysztof Kozlowski
[not found] ` <93bb8a3f7f5567cfe427ed067f68d5c8b6db776d.camel@mediatek.com>
2022-08-30 7:42 ` Krzysztof Kozlowski [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=52336b1e-f0b3-c828-48ef-b6977fd90547@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eddie.huang@mediatek.com \
--cc=fshao@chromium.org \
--cc=hsin-hsiung.wang@mediatek.com \
--cc=hui.liu@mediatek.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=macpaul.lin@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=sen.chu@mediatek.com \
--cc=wen.su@mediatek.com \
--cc=zhiyong.tao@mediatek.com \
/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;
as well as URLs for NNTP newsgroup(s).