From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933934AbcBBTj0 (ORCPT ); Tue, 2 Feb 2016 14:39:26 -0500 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:59835 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932921AbcBBTjX (ORCPT ); Tue, 2 Feb 2016 14:39:23 -0500 Date: Tue, 2 Feb 2016 19:39:13 +0000 From: Mark Brown To: menghui lin Cc: John Crispin , Liam Girdwood , HenryC Chen =?utf-8?B?KOmZs+W7uuixqik=?= , linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org, Matthias Brugger , Chen Zhong , linux-arm-kernel@lists.infradead.org Message-ID: <20160202193913.GY4455@sirena.org.uk> References: <1453896059-44589-1-git-send-email-blogic@openwrt.org> <1453896059-44589-2-git-send-email-blogic@openwrt.org> <20160127144105.GQ6042@sirena.org.uk> <56AA5A5C.9080402@openwrt.org> <20160128231306.GD4130@sirena.org.uk> <1454061134.10861.14.camel@mtksdaap41> <20160129112717.GP4130@sirena.org.uk> <1454069479.10861.30.camel@mtksdaap41> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="b/3kIrr+SWblMf9a" Content-Disposition: inline In-Reply-To: <1454069479.10861.30.camel@mtksdaap41> X-Cookie: Duckies are fun! User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: 2a01:348:6:8808:fab::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH V4 2/2] regulator: mt6323: Add support for MT6323 regulator X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --b/3kIrr+SWblMf9a Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jan 29, 2016 at 08:11:19PM +0800, menghui lin wrote: > On Fri, 2016-01-29 at 12:27 +0100, Mark Brown wrote: > > None of this is answering my question - I know what the current API is, > > describing it doesn't tell me about actual users or how they are able to > > sensibly use the interface. Bear in mind that the definitions of the > > various modes are all relative and what one device thinks is high usage > > may be low usage for another device. > Assuming valid_modes_mask and initial_mode are specified, a possible > way to modify regulator_set_mode() is to allow mode change only if the > regulator is controlled exclusively by a certain consumer or the > requested mode provides stronger power capability than current mode. > Here I assume that power capability fast > normal > idle > standby. ...and I also note that the above *still* doesn't answer my questions above. --b/3kIrr+SWblMf9a Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWsQXgAAoJECTWi3JdVIfQ2fwH/0/NuBXkjO3k6AEV8LpuvK2E PamCWVfN4FFSz/rwtsMKTShq2Ng8sjBJ8k4OcNo61l/bOHOZ8jBC9Zk/XQ8QXKFQ WKwwIsk1ZnNvPTTEu5/Eo6D7CBPFxFsbmQ0a3vDos4GXm5EfmLFy73IKphYl5rzN 7DiQqVXJyVWtu2NtNcLLDDTWSgd1tYUc+xv1+SsLhJpI/gY4HcRYCSc5vEU9VU0b dvZaTW8jVIxa3nr2FTrPBIlvvt+cKwcx7LiXHNP3f1CqD9tq85kDFWEYL+UAZVFF L/uSsEcqNHFLMqSMyHUMY9JJE7wF0/Z1rb3B/fSsVWX911vz9VeyO5UYcY989Xw= =Z7CK -----END PGP SIGNATURE----- --b/3kIrr+SWblMf9a--