Searched hist:"1 efae8d2e7775b04656eb18d0a044fbd412dab3c" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/drivers/opp/ |
| H A D | opp.h | diff 1efae8d2e7775b04656eb18d0a044fbd412dab3c Fri Jun 03 04:31:30 CDT 2022 Viresh Kumar <viresh.kumar@linaro.org> OPP: Make dev_pm_opp_set_opp() independent of frequency
dev_pm_opp_set_opp() can be called for any device, it may or may not
have a frequency value associated with it.
If a frequency value isn't available, we pass 0 to _set_opp(). Make it
optional instead by making _set_opp() accept a pointer instead, as the
frequency value is anyway available in the OPP. This makes
dev_pm_opp_set_opp() and _set_opp() completely independent of any
special key value.
Tested-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
|
| H A D | core.c | diff 1efae8d2e7775b04656eb18d0a044fbd412dab3c Fri Jun 03 04:31:30 CDT 2022 Viresh Kumar <viresh.kumar@linaro.org> OPP: Make dev_pm_opp_set_opp() independent of frequency
dev_pm_opp_set_opp() can be called for any device, it may or may not
have a frequency value associated with it.
If a frequency value isn't available, we pass 0 to _set_opp(). Make it
optional instead by making _set_opp() accept a pointer instead, as the
frequency value is anyway available in the OPP. This makes
dev_pm_opp_set_opp() and _set_opp() completely independent of any
special key value.
Tested-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
|