lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A667231.3020809@gmail.com>
Date:	Wed, 22 Jul 2009 09:58:09 +0800
From:	Eric Miao <eric.y.miao@...il.com>
To:	Daniel Ribeiro <drwyrm@...il.com>
CC:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Liam Girdwood <lrg@...mlogic.co.uk>,
	linux-kernel@...r.kernel.org, David Brownell <david-b@...bell.net>
Subject: Re: [PATCH 1/6] regulator: Add regulator_get_exclusive() API

Daniel Ribeiro wrote:
> Em Ter, 2009-07-21 às 16:00 +0100, Mark Brown escreveu:
>> Some consumers require complete control of the regulator and can't
>> tolerate sharing it with other consumers, most commonly because they need
>> to have the regulator actually disabled so can't have other consumers
>> forcing it on. This new regulator_get_exclusive() API call allows these
>> consumers to explicitly request this, documenting the assumptions that
>> they are making.
>>
>> In order to simplify coding of such consumers the use count for regulators
>> they request is forced to match the enabled state of the regulator when
>> it is requested. This is not possible for consumers which can share
>> regulators due to the need to keep track of the ownership of use counts.
>>
>> A new API call is used rather than an additional argument to the existing
>> regulator_get() in order to avoid merge headaches with driver code in
>> other trees.
>>
>> Signed-off-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>
> 
> Thanks for finally fixing the mmc/regulator issue. ;)
> 
> Can you update pxamci.c and twl4030-mmc.c to make use of this new API?
> 

I think that deserves another two patches for making use of this
new API.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ