From: "Paul Louvel" <paul.louvel@bootlin.com>
To: "Krzysztof Kozlowski" <krzk@kernel.org>,
"Paul Louvel" <paul.louvel@bootlin.com>
Cc: "Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Herve Codina" <herve.codina@bootlin.com>,
"Miquel Raynal" <miquel.raynal@bootlin.com>
Subject: Re: [PATCH v2 1/4] regulator: dt-bindings: Add TI LM51772 support
Date: Thu, 29 Oct 2026 10:05:38 +0100 [thread overview]
Message-ID: <DMH7AO649J2M.2XFQNV3VXL6UP@bootlin.com> (raw)
In-Reply-To: <20261029-indefinable-bustard-of-ampleness-44abaf@quoll>
Hi Krzysztof,
On Thu Oct 29, 2026 at 9:41 AM CET, Krzysztof Kozlowski wrote:
> On Tue, Oct 27, 2026 at 10:39:23AM +0100, Paul Louvel wrote:
>> + regulator-temp-warn-kelvin:
>> + enum: [0, 1, 368, 383, 398, 413]
>> +
>> + regulator-ramp-delay:
>> + enum: [40000, 20000, 1000, 500]
>> +
>> + regulator-min-microvolt:
>> + minimum: 1000000
>> + maximum: 48000000
>> +
>> + regulator-max-microvolt:
>> + minimum: 1000000
>> + maximum: 48000000
>> +
>> + regulator-min-microamp:
>> + minimum: 500000
>> + maximum: 7000000
>> +
>> + regulator-max-microamp:
>> + minimum: 500000
>> + maximum: 7000000
>> +
>> + unevaluatedProperties: false
>
> Place this line after description, that's the convention for child nodes
> for readability.
>
>> +
>> + vcc1:
>> + type: object
>> + $ref: regulator.yaml#
>> + description: |
>> + LDO regulator for auxiliary use.
>> + It can used to power, for example, a PD controller that will drive this PMIC.
>> +
>> + properties:
>> + regulator-min-microvolt:
>> + minimum: 5000000
>> + maximum: 5000000
>> +
>> + regulator-max-microvolt:
>> + minimum: 5000000
>> + maximum: 5000000
>> +
>> + unevaluatedProperties: false
>
> Place this line after description, that's the convention for child nodes
> for readability.
>
>> +
>> + additionalProperties: false
>
> Place this line after description (for relevant block), that's the
> convention for child nodes for readability.
>
>> +
>> + ti,sync-pin:
>> + description: |
>> + Selects the function of the SYNC pin, used when several converters
>> + operate in parallel.
>> + $ref: /schemas/types.yaml#/definitions/string
>> + enum: [input-rising, input-falling, output-rising, output-falling]
>> + default: input-rising
>> +
>> + ti,ivp-thres-microvolt:
>
> Use either existing over-voltage-threshold-microvolt from battery schema
> or ti,ovp-microvolt from the other TI binding.
IVP is not the same as OVP.
>
>> + description: |
>> + Input Overvoltage Protection and Regulation Threshold.
>> + It shall avoid any damage to the device in case the current flows from the
>> + output to the input and the input source cannot sink current.
>> + This threshold is used for IVP (Input Voltage Protection) and IVR (Input
>> + Voltage Regulation).
>> + oneOf:
>> + - multipleOf: 125000
>> + minimum: 4750000
>> + maximum: 23250000
>> + - multipleOf: 250000
>> + minimum: 23500000
>> + maximum: 50000000
>> + default: 50000000
>> +
>> + ti,ivp:
>> + description: Enable the IVP feature of the regulator.
>> + type: boolean
>> +
>> + ti,ivr:
>> + description: Enable the IVR feature of the regulator.
>> + type: boolean
>
> Why wouldn't you want to enable these two always?
>
By default, these are off when the device is powered on and these features exist
only for reverse-current situation.
Also if IVP and IVR is on, only the regulation feature is enabled, not the
protection feature. This is a requirement from the datasheet. It is not ideal
and I should not reflect that requirement in the DT.
It should be ti,ivp or ti,ivr but not both because it is confusing.
Or:
ti,input-voltage-mode:
enum: [protection, regulation]
...
>> +
>> + ti,nint:
>> + description: |
>> + Configures the nFLT/nINT pin to act as an interrupt pin.
>> +
>> + nFLT mode: The pin remains low until the cause of the status change ceases.
>> + In this mode use an level irq trigger.
>> +
>> + nINT mode: The pin is asserted low to signal a status change.
>> + In this mode use an edge irq trigger.
>> + type: boolean
>> +
>> + ti,cable-drop-compensation:
>> + description: |
>> + The cable drop compensation feature helps to keep the output voltage at the
>> + nominal value over a wide range of load current without the need for
>> + additional remote sensing. The cable drop compensation measures the
>> + current and offsets the output voltage proportionally to the measured
>> + current.
>> + type: boolean
>> +
>> +dependencies:
>> + ti,ivr: ["ti,ivp"]
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - interrupts
>
> Best regards,
> Krzysztof
Thanks.
Best regards,
--
Paul Louvel, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-10-29 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 9:39 [PATCH v2 0/4] Add TI LM51772 buck-boost voltage regulator Paul Louvel
2026-10-27 9:39 ` [PATCH v2 1/4] regulator: dt-bindings: Add TI LM51772 support Paul Louvel
2026-10-29 8:41 ` Krzysztof Kozlowski
2026-10-29 9:05 ` Paul Louvel [this message]
2026-10-27 9:39 ` [PATCH v2 2/4] regulator: Support regulators where the voltage selector spans two registers Paul Louvel
2026-10-27 9:39 ` [PATCH v2 3/4] regulator: core: Call set_over_voltage_protection() if OVP limit is fixed after setting new voltage Paul Louvel
2026-10-27 9:50 ` sashiko-bot
2026-10-27 9:39 ` [PATCH v2 4/4] regulator: Add TI LM51772 support Paul Louvel
2026-10-27 10:01 ` sashiko-bot
2026-10-27 11:36 ` Paul Louvel
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=DMH7AO649J2M.2XFQNV3VXL6UP@bootlin.com \
--to=paul.louvel@bootlin.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=herve.codina@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.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