[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141124152433.GD7712@sirena.org.uk>
Date: Mon, 24 Nov 2014 15:24:33 +0000
From: Mark Brown <broonie@...nel.org>
To: Alban Bedel <alban.bedel@...onic-design.de>
Cc: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
Grant Likely <grant.likely@...aro.org>,
Liam Girdwood <lgirdwood@...il.com>,
Kumar Gala <galak@...eaurora.org>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Mark Rutland <mark.rutland@....com>,
Pawel Moll <pawel.moll@....com>,
Rob Herring <robh+dt@...nel.org>
Subject: Re: [PATCH 3/4] devicetree: add a binding for a group of regulator
On Mon, Nov 24, 2014 at 02:02:02PM +0100, Alban Bedel wrote:
> +This binding allow creating a group of regulators for use with simple
> +drivers that only expect a single power supply. Additionally it is
> +possible to enforce the enable ordering to create simple power up
> +sequences.
Absoutely not, this sort of scripting is not sensible - if the consumer
device has multiple supplies the consumer device should be working with
them independently and if the consumer has ordering constraints it needs
to enforce them itself. Trying to solve this problem with a bodge in
the regulator API just isn't the right place, leaving aside the above
most power sequences involve things other than regulators like clocks
and reset signals so just doing things purely at the regulator API level
isn't ging to solve the problem.
Please look for the generic power sequence stuff that was getting
discussed a while back and try to resurrect that if you feel there's a
compelling reason to have this functionality without doing it for
drivers.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists