On Mon, Jul 14, 2014 at 10:38:56AM +0200, Thierry Reding wrote: > On Fri, Jul 11, 2014 at 08:21:27PM +0300, Tuomas Tynkkynen wrote: > > I don't think we can assume that each selector maps to a concrete register > > value, though I'm not sure. include/linux/regulator/driver.h documents for > > @list_voltage "Selectors range from zero to one less > > regulator_desc.n_voltages." but maybe the consumer API could take different > > values. > I don't think the regulator API makes any guarantees that the selector > corresponds to a register value. Adding Mark Brown, maybe he can help > figure out the best way to do this. The selector value is opaque, it's entirely up to the driver to define it. If you could tell me what "this" is I might be able to advise on how to do it.
Attachment:
signature.asc
Description: Digital signature
