- 17 May, 2014 3 commits
-
-
Wolfram Sang authored
Copy the device nodes from Genmai reference into the Genmai device tree file. This will allow us to use a single DTS file regardless of kernel configuration. In case of legacy C board code the device nodes may or may not be used, but in the multiplatform case all the DT device nodes will be used. Signed-off-by:
Wolfram Sang <wsa+renesas@sang-engineering.com> Signed-off-by:
Simon Horman <horms+renesas@verge.net.au>
-
Wolfram Sang authored
genmai-reference is now only built for multiplatform which means that CCF comes with the package. Remove unused legacy code ifdefs to clean up the code. Signed-off-by:
Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by:
-
Wolfram Sang authored
Now that r7s72100 has CCF support, remove the legacy Genmai reference Kconfig bits for the non-multiplatform case. Starting from this commit Genmai board support is always enabled via CONFIG_MACH_GENMAI, and CONFIG_ARCH_MULTIPLATFORM is used to select between board-genmai.c and board-genmai-reference.c The file board-genmai-reference.c can no longer be used together with the legacy sh-clk clock framework, instead CCF is used. Signed-off-by:
-
- 14 May, 2014 12 commits
-
-
Wolfram Sang authored
MTU2 is not yet prepared for DT usage, so use the common workaround via clkdev for now. Acked-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com> Acked-by:
Magnus Damm <damm+renesas@opensource.se> Signed-off-by:
Geert Uytterhoeven <geert+renesas@glider.be> Signed-off-by:
-
Geert Uytterhoeven authored
arch/arm/mach-shmobile/board-genmai-reference.c:23:0: arch/arm/mach-shmobile/include/mach/clock.h:19:54: warning: 'struct clk' declared inside parameter list [enabled by default] arch/arm/mach-shmobile/include/mach/clock.h:19:54: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default] Signed-off-by:
-
Wolfram Sang authored
Not used anymore since we switched to CCF. Acked-by:
-
Wolfram Sang authored
Acked-by:
-
Wolfram Sang authored
Not used anymore since we switched to CCF. Acked-by:
-
Wolfram Sang authored
Acked-by:
-
Wolfram Sang authored
We have now DT support for SCIF, so use the platform_device initialization only for the legacy support. Acked-by:
-
Wolfram Sang authored
We keep the UART naming backwards compatible with the legacy version. Acked-by:
-
Wolfram Sang authored
Acked-by:
-
Wolfram Sang authored
Acked-by:
-
Wolfram Sang authored
Only essential clocks are added for now. Other clocks will be added when needed. Acked-by:
-
Wolfram Sang authored
Acked-by:
Mike Turquette <mturquette@linaro.org> Signed-off-by:
-
- 11 May, 2014 15 commits
-
-
Laurent Pinchart authored
The MTU2 (Multi-Function Timer Pulse Unit 2) driver implements a new style of platform data that handles the timer as a single device with multiple channel. Switch from the old-style platform data to the new-style platform data. Signed-off-by:
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> Tested-by:
Wolfram Sang <wsa@sang-engineering.com> Signed-off-by:
-
Laurent Pinchart authored
The MTU2 (Multi-Function Timer Pulse Unit 2) driver implements a new style of platform data that handles the timer as a single device with multiple channel. Switch from the old-style platform data to the new-style platform data. Signed-off-by:
-
Laurent Pinchart authored
The TMU (Timer Unit) driver implements a new style of platform data that handles the timer as a single device with multiple channel. Switch from the old-style platform data to the new-style platform data. Signed-off-by:
-
Laurent Pinchart authored
The TMU (Timer Unit) driver implements a new style of platform data that handles the timer as a single device with multiple channel. Switch from the old-style platform data to the new-style platform data. Signed-off-by:
-
Laurent Pinchart authored
The TMU (Timer Unit) driver implements a new style of platform data that handles the timer as a single device with multiple channel. Switch from the old-style platform data to the new-style platform data. Signed-off-by:
-
Laurent Pinchart authored
The TMU (Timer Unit) driver implements a new style of platform data that handles the timer as a single device with multiple channel. Switch from the old-style platform data to the new-style platform data. Signed-off-by:
-
Laurent Pinchart authored
The TMU (Timer Unit) driver implements a new style of platform data that handles the timer as a single device with multiple channel. Switch from the old-style platform data to the new-style platform data. Signed-off-by:
-
Laurent Pinchart authored
The TMU (Timer Unit) driver implements a new style of platform data that handles the timer as a single device with multiple channel. Switch from the old-style platform data to the new-style platform data. Signed-off-by:
-
Laurent Pinchart authored
The CMT (Compare Match Timer) driver implements a new style of platform data that handles the timer as a single device with multiple channel. Switch from the old-style platform data to the new-style platform data. Signed-off-by:
-
Laurent Pinchart authored
The CMT (Compare Match Timer) driver implements a new style of platform data that handles the timer as a single device with multiple channel. Switch from the old-style platform data to the new-style platform data. Signed-off-by:
-
Laurent Pinchart authored
The CMT (Compare Match Timer) driver implements a new style of platform data that handles the timer as a single device with multiple channel. Switch from the old-style platform data to the new-style platform data. Signed-off-by:
-
Laurent Pinchart authored
The CMT (Compare Match Timer) driver implements a new style of platform data that handles the timer as a single device with multiple channel. Switch from the old-style platform data to the new-style platform data. Signed-off-by:
-
Laurent Pinchart authored
The CMT (Compare Match Timer) driver implements a new style of platform data that handles the timer as a single device with multiple channel. Switch from the old-style platform data to the new-style platform data. Signed-off-by:
-
Laurent Pinchart authored
The CMT (Compare Match Timer) driver implements a new style of platform data that handles the timer as a single device with multiple channel. Switch from the old-style platform data to the new-style platform data. Signed-off-by:
-
Laurent Pinchart authored
The CMT (Compare Match Timer) driver implements a new style of platform data that handles the timer as a single device with multiple channel. Switch from the old-style platform data to the new-style platform data. Signed-off-by:
-
- 23 Apr, 2014 2 commits
-
-
Simon Horman authored
Merge branch 'clockevents/cmt-mtu2-tmu-cleanups' of git://git.linaro.org/people/daniel.lezcano/linux into cmt-mtu2-tmu-cleanups-for-v3.16
-
Simon Horman authored
Renesas ARM Based SoC Clock Updates for v3.16 SH Mobile shared clock code * Introduce shmobile_clk_workaround() r8a7791 (R-Car M2) SoC * Rename VSP1_SY clocks to VSP1_S * Correct the I2C clocks parents r8a7790 (R-Car H2) SoC * Remove old style audio clock * Rename VSP1_(SY|RT) clocks to VSP1_(S|R) * Fix the I2C clocks parents r8a7778 (R-Car M1) SoC * Remove old style audio clock
-
- 16 Apr, 2014 8 commits
-
-
Laurent Pinchart authored
This helps locating duplicates and inserting new headers. Signed-off-by:
-
Laurent Pinchart authored
Do not include the paragraph about writing to the Free Software Foundation's mailing address from the sample GPL notice. The FSF has changed addresses in the past, and may do so again. Linux already includes a copy of the GPL. Signed-off-by:
-
Laurent Pinchart authored
The sh_mtu2 driver gets the MTU2 functional clock using a connection ID of "mtu2_fck". While all SH SoCs create clock lookup entries with a NULL device ID and a "mtu2_fck" connection ID, the ARM SoCs use the device ID only with a NULL connection ID. This works on legacy platforms but will break on ARM with DT boot. Fix the situation by using a connection ID of "fck" in the non-legacy platform data case. Clock lookup entries will be renamed to use the device ID as well as the connection ID as platforms get moved to new platform data. The legacy code will eventually be dropped, leaving us with device ID based clock lookup, compatible with DT boot. Signed-off-by:
-
Laurent Pinchart authored
MTU2 hardware devices can support multiple channels, with global registers and per-channel registers. The sh_mtu2 driver currently models the hardware with one Linux device per channel. This model makes it difficult to handle global registers in a clean way. Add support for a new model that uses one Linux device per timer with multiple channels per device. This requires changes to platform data, add new channel configuration fields. Support for the legacy model is kept and will be removed after all platforms switch to the new model. Signed-off-by:
-
Laurent Pinchart authored
All boards use clock event ratings of 200 for the MTU2, hardcode it in the driver. Signed-off-by:
-
Laurent Pinchart authored
The MTU2 is not tied to CPU0, make it usable on any CPU. Signed-off-by:
-
Laurent Pinchart authored
Define symbolic macros for all used registers bits. Signed-off-by:
-
Laurent Pinchart authored
This prepares the driver for multi-channel support. Signed-off-by:
-
