summaryrefslogtreecommitdiff
path: root/tools/perf/Documentation
diff options
context:
space:
mode:
authorAlexandre Bailon <abailon@baylibre.com>2016-12-09 17:59:32 +0100
committerSekhar Nori <nsekhar@ti.com>2017-01-02 16:10:42 +0530
commit48cd30b49527f04078ef7de217cc188157f76ba6 (patch)
tree062d3553ca1d5467bdf92717a5c23c8848c070a9 /tools/perf/Documentation
parentef37427ac5677331145ab27a17e6f5f1b43f0c11 (diff)
ARM: davinci: Make __clk_{enable,disable} functions public
In some cases, there is a need to enable a clock as part of clock enable callback of a different clock. For example, USB 2.0 PHY clock enable requires USB 2.0 clock to be enabled. In this case, it is safe to instead call __clk_enable() since the clock framework lock is already taken. Calling clk_enable() causes recursive locking error. A similar case arises in the clock disable path. To enable such usage, make __clk_{enable,disable} functions publicly available outside of clock.c. Also, call them davinci_clk_{enable|disable} now to be consistent with how other davinci-specific clock functions are named. Note that these functions are not exported to drivers. They are meant for usage in platform specific clock management code. Signed-off-by: Alexandre Bailon <abailon@baylibre.com> Suggested-by: David Lechner <david@lechnology.com> Signed-off-by: Sekhar Nori <nsekhar@ti.com>
Diffstat (limited to 'tools/perf/Documentation')
0 files changed, 0 insertions, 0 deletions