[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130601184511.GC16790@sirena.org.uk>
Date: Sat, 1 Jun 2013 19:45:11 +0100
From: Mark Brown <broonie@...nel.org>
To: Laxman Dewangan <ldewangan@...dia.com>
Cc: Kishon Vijay Abraham I <kishon@...com>,
"lgirdwood@...il.com" <lgirdwood@...il.com>,
"sameo@...ux.intel.com" <sameo@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"gg@...mlogic.co.uk" <gg@...mlogic.co.uk>,
"ian@...mlogic.co.uk" <ian@...mlogic.co.uk>,
"balbi@...com" <balbi@...com>
Subject: Re: [RFC PATCH] regulator: palmas: enable all modes for SMPS10
On Thu, May 30, 2013 at 06:30:32PM +0530, Laxman Dewangan wrote:
> Palma have SMPS10 regulator which can generate two voltage level
> 3.75 and 5V.
> This SMPS10 has the two outputs OUT1 and OUT2 and having one input IN1.
> SMPS10-OUT2 is always connected to SMPS10-IN1 via following logic:
> - Through parasitic diode (no sw control)
> - In bypass mode (bit configuration is there to enable/disable Bypass)
> - In Boost mode (bit configuration is there to enable/disable Boost mode)
> SMPS10-OUT1 is connected to the SMPS10-OUT2 pin through Switch (SW
> control for enabling/disabling this switch).
> So I think:
> regualtor enable/disable, we should toggle the bit for SWITCH.
> In STANDBY mode, it should be BYPASS disable and Boost disable.
> In Idle/Normal mode, BYPASS enable and Boost disable.
> In Fast mode, it should be bypass disable and Boost enable.
No, that makes no sense at all to me. Why do you think this maps onto
the set mode API? Modes are all about accuracy of regulation.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists