PM / OPP: Don't allocate OPP table from _opp_allocate()

Browse source

There is no point in trying to find/allocate the table for every OPP
that is added for a device. It would be far more efficient to allocate
the table only once and pass its pointer to the routines that add the
OPP entry.

Locking is removed from _opp_add_static_v2() and _opp_add_v1() now as
the callers call them with that lock already held.

Call to _remove_opp_table() routine is also removed from _opp_free()
now, as opp_table isn't allocated from within _opp_allocate(). This is
handled by the routines which created the OPP table in the first place.

Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

...

This commit is contained in:

Viresh Kumar 2017-01-02 14:41:01 +05:30 • committed by Rafael J. Wysocki

parent 9274c89243

commit 8cd2f6e8f3

3 changed files with 78 additions and 73 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

67

drivers/base/power/opp/core.c

View file

75

drivers/base/power/opp/of.c

View file

9

drivers/base/power/opp/opp.h

View file