Thara Gopinath <th...@ti.com> writes: > This patch introduces a user list of devices associated with each > voltage domain instance. The user list is implemented using plist > structure with priority node populated with the voltage values. > This patch also adds an API which will take in a device and > requested voltage as parameters, adds the info to the user list > and returns back the maximum voltage requested by all the user > devices. This can be used anytime to get the voltage that the > voltage domain instance can be transitioned into. > > Signed-off-by: Thara Gopinath <th...@ti.com>
Looking closer at this, keeping track of a list of devices and constraints is what the regulator framework does as well. Before we get too far down this path, we need to start working with Thomas Petazzoni to better understand how we can use the regulator framework for much of the management levels of the voltage layer. I'd rather not re-invent some of the management/constraints management that could be done by the regulator framework. Basically, I think r = regulator_get(dev, voltdm->name) regulator_set_voltage(r, volt) would basially be the equivalent of omap_voltage_add_userreq(voldm, dev, &volt); omap_scale_voltage(voltdm, volt) The regulator framework not only provides management of the users and constraints, but also provides post-change notifiers where things like dependent voltages could be handled. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
