Thara Gopinath <th...@ti.com> writes: > This patch extends the device opp structure to contain > pointers to scale the operating rate of the > device and to retrieve the operating rate of the device. > This patch also adds the three new APIs in the opp layer > namely opp_set_rate that can be called to set a new operating > rate for a device, opp_get_rate that can be called to retrieve > the operating frequency for a device and opp_populate_rate_fns > to populte the device specific set_rate and get_rate API's. > The opp_set_rate and opp_get_rate does some routine error > checks and finally calls into the device specific set_rate > and get_rate APIs populated through opp_populate_rate_fns. > > Signed-off-by: Thara Gopinath <th...@ti.com>
As I think about this more, I'm not sure the OPP layer is the right layer for the get/set rate functions. The OPP layer is currently just the data store for OPP data. To me, these set/get functions are better associated directly with an omap_device instead of an OPP. For instance, the new OPP APIs are a bit confusing in terms of OPPs. e.g: opp_get_rate(). What is the "rate" of an OPP, and what's the difference with opp_get_freq()? What's really happening is the rate is being changed for a device, and the need for specific hooks are at the device level, not the OPP level. For example, this current approach would not scale if you needed multiple devices in the same domain that each needed custom set_rate/get_rate hooks. So instead, what about adding custom hooks at the omap_device level? They could be registered at omap_device_build() time in the device specific code. 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
