Re: [PATCH] PM / OPP: predictable fail results for opp_find* functions

2012-10-18 Thread Rafael J. Wysocki
On Wednesday 17 of October 2012 15:14:22 Kevin Hilman wrote: > Nishanth Menon writes: > > > Currently the opp_find* functions return -ENODEV when: > > a) it cant find a device (e.g. request for an OPP search on device > >which was not registered) > > b) When it cant find a match for the searc

Re: [PATCH] PM / OPP: predictable fail results for opp_find* functions

2012-10-17 Thread MyungJoo Ham
> Currently the opp_find* functions return -ENODEV when: > a) it cant find a device (e.g. request for an OPP search on device >which was not registered) > b) When it cant find a match for the search strategy used > > This makes life a little in-efficient for users such as devfreq > to make rea

Re: [PATCH] PM / OPP: predictable fail results for opp_find* functions

2012-10-17 Thread Kevin Hilman
Nishanth Menon writes: > Currently the opp_find* functions return -ENODEV when: > a) it cant find a device (e.g. request for an OPP search on device >which was not registered) > b) When it cant find a match for the search strategy used > > This makes life a little in-efficient for users such

[PATCH] PM / OPP: predictable fail results for opp_find* functions

2012-10-11 Thread Nishanth Menon
Currently the opp_find* functions return -ENODEV when: a) it cant find a device (e.g. request for an OPP search on device which was not registered) b) When it cant find a match for the search strategy used This makes life a little in-efficient for users such as devfreq to make reasonable judgem