>Policy notifiers are called before a frequency change and may narrow >the min/max frequency range in devfreq_policy, which is used to adjust >the target frequency if it is beyond this range. > >Also add a few helpers: > - devfreq_verify_within_[dev_]limits() > - should be used by the notifiers for policy adjustments. > - dev_to_devfreq() > - lookup a devfreq strict from a device pointer > >Signed-off-by: Matthias Kaehlcke <mka@xxxxxxxxxxxx> >--- > drivers/devfreq/devfreq.c | 47 +++++++++++++++++++++------- > include/linux/devfreq.h | 66 +++++++++++++++++++++++++++++++++++++++ > 2 files changed, 102 insertions(+), 11 deletions(-) Hello Matthias, Why should we have yet another notifier from an instance of devfreq? Wouldn't it better to let the current notifier (transition notifier) handle new events as well by adding possible event states to it? Anyway, is this the reason why you've separated some data of devfreq into "policy" struct? (I was wondering why while reading commit 6/11). Cheers MyungJoo -- 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
