diff options
| author | Paul Walmsley <paul@pwsan.com> | 2011-02-25 15:49:01 -0700 |
|---|---|---|
| committer | Paul Walmsley <paul@pwsan.com> | 2011-02-25 16:10:16 -0700 |
| commit | b80b956dc56c6a3cb77b97e2abff48fb7ebc2119 (patch) | |
| tree | 09c2fdf7f9cd0c5998c2bc5e1ef7144d405d1279 /lib/btree.c | |
| parent | 6c6f5a7437955cec637c00ab1d09b8f70fc0ab3a (diff) | |
| download | op-kernel-dev-b80b956dc56c6a3cb77b97e2abff48fb7ebc2119.zip op-kernel-dev-b80b956dc56c6a3cb77b97e2abff48fb7ebc2119.tar.gz | |
OMAP2+: clock: autoidle as many clocks as possible if CONFIG_OMAP_RESET_CLOCKS
Attempt to enable autoidle for as many clocks as possible in the
OMAP2+-common CONFIG_OMAP_RESET_CLOCKS code. Currently, this only
enables DPLL autoidle for OMAP3/4 DPLLs; but future patches will
enable autoidle for other clocks and the OMAP2 DPLL/APLLs.
In the long run, we should probably get rid of
CONFIG_OMAP_RESET_CLOCKS, and unconditionally run the code that it
selects. Otherwise, the state of the clock tree won't match the
hardware state - this could result in clocks being enabled or disabled
unpredictably.
Based on a patch by Rajendra Nayak <rnayak@ti.com> that did this in
the pm34xx.c/pm44xx.c code.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Cc: Rajendra Nayak <rnayak@ti.com>
Diffstat (limited to 'lib/btree.c')
0 files changed, 0 insertions, 0 deletions
