Changes since v4:
- Rebased to 3.8-rc7
- Updated the MCT controller device nodes to list all the four global timer
interrupts generated by the MCT controller.
Changes since v3:
- Based on Stephen Warren's CONFIG_CLKSRC_OF patches (merged from arm-soc
'timer/cleanup' branch).
- Moved the mct
All the MCT register read/writes use a fixed remapped address S5P_VA_SYSTIMER.
With device tree support for MCT controller, it is possible to remove the
static remap of the MCT controller address space and do the remap during the
initialization of the MCT controller with the physical address
Instead of using soc_is_xxx macro at more than one place in the MCT
controller driver to decide the MCT interrpt number to be setup, populate
a table of known MCT global and local timer interrupts and use the values
in table to setup the MCT interrupts.
This also helps in adding device tree
Allow the MCT controller base address and interrupts to be obtained from
device tree and remove unused static definitions of these. The non-dt support
for Exynos5250 is removed but retained for Exynos4210 based platforms.
Cc: Changhwan Youn chaos.y...@samsung.com
Signed-off-by: Thomas Abraham
Add entries to __clksrc_of_table so that Exynos MCT controller is discoverable
using call to clocksource_of_init. With this change, it would be appropriate to
rename the function 'exynos4_timer_init' as 'mct_init' since it aptly describes
this function. Additionally, the 'init_time' callback of
Add MCT device tree node for Exynos4210, Exynos4212, Exynos4412 and Exynos5250.
Cc: Changhwan Youn chaos.y...@samsung.com
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
Reviewed-by: Stephen Warren swar...@nvidia.com
---
arch/arm/boot/dts/exynos4210.dtsi | 22 ++
With device tree support enabled for MCT controller, the staticio-remapping
of the MCT controller address space is removed for Exynos5 platforms (which
supports only device tree based boot).
Cc: Changhwan Youn chaos.y...@samsung.com
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
Move the multi core timer (mct) driver to from mach-exynos to
drivers/clocksource and update the Kconfig and makefiles.
Cc: Changhwan Youn chaos.y...@samsung.com
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
Reviewed-by: Stephen Warren swar...@nvidia.com
---
arch/arm/Kconfig
Changes since v5:
- Squashed several Exynos4 fixes patch from Tomasz Figa
- Included support for Exynos5250 and Exynos5440, thus converting all
Exynos4 and Exynos5 platforms to common clock framework.
- Depends on the following patch series.
-
There are several types of pll clocks used in Samsung SoC's and these pll
clocks can be represented as Samsung specific pll clock types and registered
with the common clock framework. Add support for pll35xx, pll36xx, pll45xx,
pll46xx and pll2550x clock types and helper functions to register them.
The Exynos4 clocks are statically listed and registered using the Samsung
specific common clock helper functions. Both device tree based clock lookup
and clkdev based clock lookups are supported.
Cc: Mike Turquette mturque...@linaro.org
Cc: Kukjin Kim kgene@samsung.com
Reviewed-by: Sylwester
The Exynos5250 clocks are statically listed and registered using the Samsung
specific common clock helper functions. Both device tree based clock lookup
and clkdev based clock lookups are supported.
Cc: Mike Turquette mturque...@linaro.org
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by:
The Exynos5440 clocks are statically listed and registered using the Samsung
specific common clock helper functions.
Cc: Mike Turquette mturque...@linaro.org
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
---
All Samsung platforms include different types of clock including fixed-rate,
mux, divider and gate clock types. There are typically hundreds of such clocks
on each of the Samsung platforms. To enable Samsung platforms to register these
clocks using the common clock framework, a bunch of utility
Since the clock initialization should be completed prior to the mct timer
initialization, create a new function 'exynos_init_time' that first sets up
the clock and then invokes the timer initialization function. The 'init_time'
callback in the board files are updated to invoke this new wrapper
The clock speed of xxti and xusbxti clocks depends on the oscillator used on the
board to generate these clocks. For non-dt platforms, allow the board support
for those platforms to set the clock frequency of xxti and xusbxti clocks.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by: Thomas
With support for device tree based clock lookup now available, remove the
auxdata table from exynos4/5 dt-enabled machine file.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
---
arch/arm/mach-exynos/mach-exynos4-dt.c | 69 +--
With the migration of Exynos4 clocks to use common clock framework, the old
styled 'xtal' clock is not used anymore. Instead, the clock 'fin_pll' is used
as the tick clock for mct controller.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
---
Add support for mct clock lookup and setup to ensure that the mct clock
is has been turned on.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
---
drivers/clocksource/exynos_mct.c |7 ++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff
Add clock controller nodes for Exynos4210, Exynos4x12, Exynos5250 and
Exynos5440 SoC.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
---
arch/arm/boot/dts/exynos4210.dtsi |6 ++
arch/arm/boot/dts/exynos4x12.dtsi |6 ++
For all supported peripheral controllers on Exynos5250, add clock lookup
information.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
---
arch/arm/boot/dts/exynos5250.dtsi | 72 +
1 files changed, 72
For all supported peripheral controllers on Exynos5440, add clock lookup
information.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
---
arch/arm/boot/dts/exynos5440.dtsi | 18 ++
1 files changed, 18 insertions(+), 0 deletions(-)
The clock frequency of xxti and xusbxti clocks is dependent on the frequency of
the
on-board oscillator that is used to generate these clocks. So allow the
frequency
of these clocks to be specfied from device tree.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by: Thomas Abraham
For all supported peripheral controllers on Exynos4 SoCs, add clock lookup
information.
Cc: Kukjin Kim kgene@samsung.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
Tested-by: Sylwester Nawrocki s.nawro...@samsung.com
Reviewed-by: Tomasz Figa t.f...@samsung.com
Tested-by: Tomasz
On Mon, Feb 18, 2013 at 5:21 PM, Thomas Abraham
thomas.abra...@linaro.org wrote:
Since the clock initialization should be completed prior to the mct timer
initialization, create a new function 'exynos_init_time' that first sets up
the clock and then invokes the timer initialization function.
Hi,
[...]
+static void samsung_timer_parse_dt(struct device_node *np,
+ const struct of_device_id *match)
+{
+ int i;
+ u32 val;
+
+ timer_base = of_iomap(np, 0);
+ if (!timer_base)
+ panic(failed to map timer registers);
Hi Sylwester,
thannks for the review.
On 15 February 2013 16:08, Sylwester Nawrocki s.nawro...@samsung.com wrote:
Hi,
On 02/15/2013 08:10 AM, Vikas Sajjan wrote:
Adds FIMD DT binding documentation both SoC and Board, with an example
Signed-off-by: Vikas Sajjan vikas.saj...@linaro.org
---
Hi,
On 02/18/2013 11:51 AM, Vikas Sajjan wrote:
On 15 February 2013 16:08, Sylwester Nawrockis.nawro...@samsung.com wrote:
On 02/15/2013 08:10 AM, Vikas Sajjan wrote:
Adds FIMD DT binding documentation both SoC and Board, with an example
Signed-off-by: Vikas Sajjanvikas.saj...@linaro.org
This patch adds to support burst mode for for dev-to-mem and dev-to-mem transmit
Signed-off-by: Boojin Kim boojin@samsung.com
---
arch/arm/plat-samsung/dma-ops.c | 10 --
arch/arm/plat-samsung/include/plat/dma-ops.h |1 +
2 files changed, 9 insertions(+), 2
Hi,
On Mon, Feb 18, 2013 at 12:21 AM, Thomas Abraham
thomas.abra...@linaro.org wrote:
The clock frequency of xxti and xusbxti clocks is dependent on the frequency
of the
on-board oscillator that is used to generate these clocks. So allow the
frequency
of these clocks to be specfied from
30 matches
Mail list logo