diff options
author | Paul Walmsley <paul@pwsan.com> | 2010-02-23 00:09:16 -0500 |
---|---|---|
committer | Paul Walmsley <paul@pwsan.com> | 2010-02-24 14:15:04 -0500 |
commit | 1a3377176b3d41e3f30483a624cdafadeeb4064f (patch) | |
tree | 6e7fd09d43e95a5757affc4e134ed174b32f4b4c /Documentation/kernel-docs.txt | |
parent | 17d092733d9ffd7fcf6da36169a60caf8400fc4c (diff) |
OMAP2 clock: drop CONFIG_PARTICIPANT clock flag
It turns out that the only purpose of the CONFIG_PARTICIPANT clock
flag is to prevent omap2_clk_set_rate() and omap2_clk_set_parent()
from being executed on clocks with that flag set. The rate-changing
component can be more directly accomplished by dropping the .set_rate
and .round_rate function pointers from those CONFIG_PARTICIPANT struct
clks. As far as the parent-changing component is concerned, it turns
out that none of the CONFIG_PARTICIPANT clocks have multiple parent
choices, so all that is necessary is for omap2_clk_set_parent() to
bail out early if the new parent is equal to the old parent.
Implement this change and get rid of the flag, which has always had a
confusing name (it appears to be a Kconfig option, falsely).
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Cc: Richard Woodruff <r-woodruff2@ti.com>
Diffstat (limited to 'Documentation/kernel-docs.txt')
0 files changed, 0 insertions, 0 deletions