- 27 3月, 2009 1 次提交
-
-
由 Sascha Hauer 提交于
This adds clk_get_sys to get a clock without the associated struct device. Signed-off-by: NSascha Hauer <s.hauer@pengutronix.de>
-
- 17 10月, 2008 1 次提交
-
-
由 Alex Raimondi 提交于
clk_get and clk_put may not be used from within interrupt context. Change comment to this function. Signed-off-by: NAlex Raimondi <raimondi@miromico.ch> Signed-off-by: NHaavard Skinnemoen <haavard.skinnemoen@atmel.com> Acked-by: NRussell King <rmk+kernel@arm.linux.org.uk> Cc: john stultz <johnstul@us.ibm.com> Signed-off-by: NAndrew Morton <akpm@linux-foundation.org> Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
-
- 26 3月, 2006 1 次提交
-
-
由 Todd Poynor 提交于
include/linux/clk.h is betraying its ARM origins. Signed-off-by: NTodd Poynor <tpoynor@mvista.com> Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
-
- 08 1月, 2006 1 次提交
-
-
由 Russell King 提交于
This is needs to be visible to other architectures using the AMBA bus and peripherals. Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
-
- 04 1月, 2006 2 次提交
-
-
由 Russell King 提交于
It seems that clk_use() and clk_unuse() are additional complexity which isn't required anymore. Remove them from the clock framework to avoid the additional confusion which they cause, and update all ARM machine types except for OMAP. Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk> -
由 Russell King 提交于
It seems that there's some confusion over how the clock source framework should be used. Add some additional comments to explain the ambiguous areas. Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
-
- 28 4月, 2005 1 次提交
-
-
由 Russell King 提交于
clk_get() comments can be confusing. Add extra explaination of the dev and id parameters to ensure correct usage. Signed-off-by: NRussell King <rmk@arm.linux.org.uk>
-
- 17 4月, 2005 1 次提交
-
-
由 Linus Torvalds 提交于
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
-