On Thu, Oct 03, 2013 at 05:11:14PM +0100, Charles Keepax wrote:
> For the bulk API would you prefer taking a single src and alias
> device and a list of supplies, or lists for all three?
> I would go for a list just for the supplies, as lists of devices
> would probably need to be filled in by a
On Wed, Oct 02, 2013 at 08:50:29PM +0100, Mark Brown wrote:
> Bulk versions of the API would also make sense - it's likely that more
> than one supply will need to be mapped - and please also add managed
> versions so people don't have to write cleanup code.
For the bulk API would you prefer takin
On Wed, Oct 02, 2013 at 01:16:59PM +0100, Charles Keepax wrote:
> Following our discussions around the Arizona regulator
> bindings here is an effort at putting a mechanism into the
> regulator core to alias registering of a supply from one
> device to another.
This seems basically fine, though I
These patches add the ability to create an alternative device on which
a lookup for a certain supply should be conducted.
A common use-case for this would be devices that are logically
represented as a collection of drivers within Linux but are are
presented as a single device from device tree. It
4 matches
Mail list logo
