On Sat, May 22, 2010 at 09:32:10AM +0530, Sundar wrote: > > operating mode for the entire power domain. For example, I can see > > hardware requiring that if more than a given number of blocks are > > enabled at any level a higher operating point is selected. > To me, since such a requirement is a constraint on the regulator, > this can be added as a flag to the regulator details. > This flag can then be used in the set_opp* functions to check the > condition along with the client dependencies! This is just one example of something that might come up and need fitting in to the regulator API which is substantially different to the needs of the core regulator applications. As I keep saying I'm just not seeing much more overlap here with the regulator API than I do with the clock API: it feels like you've got another use case which needs an API with a similar structure and the reference counted enable and disable calls but otherwise very little overlap. I don't think the enable and disable calls are enough of an overlap to mean that the regulator use case and the operating point use case are going to overlap well, it feels like it'd cause pain trying to match the concepts between the two APIs. _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
