[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201123185141.GE56553@e120937-lin>
Date: Mon, 23 Nov 2020 18:52:08 +0000
From: Cristian Marussi <cristian.marussi@....com>
To: Mark Brown <broonie@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
devicetree@...r.kernel.org, sudeep.holla@....com,
lukasz.luba@....com, james.quinlan@...adcom.com,
Jonathan.Cameron@...wei.com, robh@...nel.org,
satyakim@....qualcomm.com, etienne.carriere@...aro.org,
f.fainelli@...il.com, vincent.guittot@...aro.org,
souvik.chakravarty@....com
Subject: Re: [PATCH v6 4/5] dt-bindings: arm: add support for SCMI Regulators
On Mon, Nov 23, 2020 at 05:30:08PM +0000, Mark Brown wrote:
> On Thu, Nov 19, 2020 at 07:10:50PM +0000, Cristian Marussi wrote:
>
> > +This binding uses the common regulator binding[6] but, due to SCMI abstractions,
> > +supports only a subset of its properties as specified below amongst Optional
> > +properties.
>
> > +Required properties:
> > + - reg : shall identify an existent SCMI Voltage Domain.
>
> > +Optional properties:
> > + - regulator-name
> > + - regulator-min-microvolt / regulator-max-microvolt
> > + - regulator-always-on / regulator-boot-on
> > + - regulator-max-step-microvolt
> > + - regulator-coupled-with / regulator-coupled-max-spread
>
> Please send a followup patch removing this stuff about only specific
> properties being supported, that's just asking for bitrot and is equally
> true for most regulator drivers - people shouldn't have to do do an
> audit of every single regulator driver to add a generic feature.
Ok I'll remove any reference to partial SCMI regulator support.
Thanks
Cristian
Powered by blists - more mailing lists