On pon, 2014-11-03 at 15:40 +0100, Javier Martinez Canillas wrote: > The regulator-initial-mode and regulator-mode DT properties allows to > configure the regulator operating modes at startup or when a system > enters into a susend state. > > But these properties use as valid values the operating modes supported > by each device while the core deals with the standard operating modes. > So a mapping function is needed to translate from the hardware specific > modes to the standard ones. > > This mapping is a non-varying configuration for each regulator, so add > a function pointer to struct regulator_desc that will allow drivers to > define their callback to do the modes translation. > > Signed-off-by: Javier Martinez Canillas <javier.martinez@xxxxxxxxxxxxxxx> > --- > include/linux/regulator/driver.h | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/include/linux/regulator/driver.h b/include/linux/regulator/driver.h > index 28da08e..b54d037 100644 > --- a/include/linux/regulator/driver.h > +++ b/include/linux/regulator/driver.h > @@ -243,6 +243,8 @@ enum regulator_type { > * > * @enable_time: Time taken for initial enable of regulator (in uS). > * @off_on_delay: guard time (in uS), before re-enabling a regulator > + * > + * @map_modes: Callback invoked to translate between hardware to standard modes. Initially I thought it should map from standard to hardware. But then I looked at max77802 implementation and it maps from hardware to standard. Anyway I got confused (both are "modes" and both unsigned ints). Could you describe which should be returned? > */ > struct regulator_desc { > const char *name; > @@ -285,6 +287,8 @@ struct regulator_desc { > unsigned int enable_time; > > unsigned int off_on_delay; > + > + unsigned int (*map_modes)(unsigned int mode); Shouldn't this be in regulator ops? Best regards, Krzysztof -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html