[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <dd547319-f8c8-4c3a-979d-4610971cdd25@sirena.org.uk>
Date: Wed, 26 Feb 2025 11:47:36 +0000
From: Mark Brown <broonie@...nel.org>
To: "Torreno, Alexis Czezar" <AlexisCzezar.Torreno@...log.com>
Cc: Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: regulator: add adi,adp5055-regulator
On Wed, Feb 26, 2025 at 02:25:02AM +0000, Torreno, Alexis Czezar wrote:
> > > + adi,disable-delay-us:
> > > + description:
> > > + Configures the disable delay for each channel. Dependent on Tset.
> > > + enum: [0, 5200, 10400, 15600, 20800, 26000, 31200, 36400]
> > > + default: 0
> > This looks a lot like the driver should implemnt the enable_time() and/or
> > set_ramp_delay() operations and use the constraints to configure this.
> Based on what I understand I agree implementing the enable_time() core
> function for this. However, shall I keep the code for the disable-delay-us?
> I don't think I saw a disable_time() equivalent
We don't generally worry about disable times, they're hugely load
dependent so the numbers tend to involve a lot of wishful thinking.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists