02 Jun, 2016
1 commit
-
The samsung_clk_init() cannot return NULL. Either it returns allocated
memory or it panics.Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
Signed-off-by: Sylwester Nawrocki
03 Mar, 2016
1 commit
-
This flag is a no-op now. Remove usage of the flag.
Acked-by: Sylwester Nawrocki
Signed-off-by: Stephen Boyd
21 Jul, 2015
1 commit
-
Clock provider drivers generally shouldn't include clk.h because
it's the consumer API. Only include clk.h in files that are
using it. The clkdev.h header isn't always used either, so remove
it and add in slab.h where files were relying on it to include
slab for them.Cc: Chanwoo Choi
Cc: Sylwester Nawrocki
Cc: Krzysztof Kozlowski
Cc: Kukjin Kim
Signed-off-by: Stephen Boyd
30 Jun, 2014
2 commits
-
Ensure the clock provider is not registered until after all its related
clocks were created and are ready to use. Currently there are races
possible and any (of_)clk_get() call right after a clock provider's
clk_init_cb callback call may fail.Signed-off-by: Sylwester Nawrocki
Signed-off-by: Tomasz Figa -
In the move to this clock driver the hookups for the SPI clocks were
dropped, which causes my system Cragganmore (s3c6410 based) to be unable
to locate any spibus clocks. This patch adds them back in.When taking the clock from the epll clock (SCLK) the rates on the SPI
bus are incorrect, this needs further debugging but the hookup here
should be correct and the problem should be else where.The USBCLK case has been dropped because this requires the USB PHY to be
enabled.Signed-off-by: Charles Keepax
Signed-off-by: Tomasz Figa
15 May, 2014
1 commit
-
Samsung CCF helper functions do not provide support to
register multiple Clock Providers for a given SoC. Due to
this limitation, SoC platforms are not able to use these
helpers for registering multiple clock providers and are
forced to bypass this layer.This layer is modified accordingly to enable the support
for multiple clock providers.Clock file for exynos4, exynos5250, exynos5420, exynos5440,
S3c64xx, S3c24xx are also modified as per changed helper functions.Signed-off-by: Rahul Sharma
[t.figa: Modified s3c2410 clock driver as well]
Signed-off-by: Tomasz Figa
14 Feb, 2014
2 commits
-
Since all SoC drivers have been moved to local suspend/resume handling,
the old code can be safely dropped.Signed-off-by: Tomasz Figa
Acked-by: Kyungmin Park
Acked-by: Heiko Stuebner
Reviewed-by: Thomas Abraham
Reviewed-by: Sylwester Nawrocki
Signed-off-by: Kukjin Kim -
Since there are multiple differences in how suspend/resume of particular
Exynos SoCs must be handled, SoC driver is better place for
suspend/resume handlers and so this patch moves them.Signed-off-by: Tomasz Figa
Acked-by: Kyungmin Park
Reviewed-by: Thomas Abraham
Reviewed-by: Sylwester Nawrocki
Signed-off-by: Kukjin Kim
24 Nov, 2013
2 commits
-
Since the old DMA driver got removed, these aliases are no longer
necessary.Signed-off-by: Tomasz Figa
Signed-off-by: Mark Brown -
This patch adds clkdev aliases for clocks used by PL08x DMA driver.
Signed-off-by: Tomasz Figa
Signed-off-by: Mark Brown
28 Aug, 2013
1 commit
-
__initdata should be placed between the variable name and equal
sign for the variable to be placed in the intended section.Signed-off-by: Sachin Kamat
Signed-off-by: Mike Turquette
06 Aug, 2013
1 commit
-
This patch adds new, Common Clock Framework-based clock driver for Samsung
S3C64xx SoCs. The driver is just added, without actually letting the
platforms use it yet, since this requires more intermediate steps.Signed-off-by: Tomasz Figa
Signed-off-by: Mike Turquette