| commit | 4ff29ff8e8723a41e7defd8bc78a7b16cbf940a2 | |
| author | Paul Mundt <lethal@linux-sh.org> | |
| Mon, 11 May 2009 20:14:53 +0000 (12 05:14 +0900) | ||
| committer | Paul Mundt <lethal@linux-sh.org> | |
| Mon, 11 May 2009 20:14:53 +0000 (12 05:14 +0900) | ||
| tree | 0e277d27eee3af89e66856458dce29e6ba3f4721 | treesnapshot (tar.gz zip) |
| parent | b1f6cfe48c3cb1dfa77db3d2f42f765febaef9bc | commitdiff |
sh: clkfwk: Consolidate the ALWAYS_ENABLED / NEEDS_INIT mess.
There is no real distinction here in behaviour, either a clock needs to
be enabled on initialiation or not. The ALWAYS_ENABLED flag was always
intended to only apply to clocks that were physically always on and could
simply not be disabled at all from software. Unfortunately over time this
was abused and the meaning became a bit blurry.
So, we kill off both of all of those paths now, as well as the newer
NEEDS_INIT flag, and consolidate on a CLK_ENABLE_ON_INIT. Clocks that
need to be enabled on initialization can set this, and it will purposely
enable them and bump the refcount up.
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
There is no real distinction here in behaviour, either a clock needs to
be enabled on initialiation or not. The ALWAYS_ENABLED flag was always
intended to only apply to clocks that were physically always on and could
simply not be disabled at all from software. Unfortunately over time this
was abused and the meaning became a bit blurry.
So, we kill off both of all of those paths now, as well as the newer
NEEDS_INIT flag, and consolidate on a CLK_ENABLE_ON_INIT. Clocks that
need to be enabled on initialization can set this, and it will purposely
enable them and bump the refcount up.
Signed-off-by: Paul Mundt <lethal@linux-sh.org>