clocksource: sh_mtu2: Rename clock to "fck" in the non-legacy case
authorLaurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Tue, 4 Mar 2014 17:09:15 +0000 (18:09 +0100)
committerSimon Horman <horms@verge.net.au>
Fri, 5 Dec 2014 00:22:55 +0000 (09:22 +0900)
commit1f93199d8a02f1a7be92a8abcc518dff30716f7d
treef54d2b147d72bfd581addae41f4eaeb59abe6f9d
parent96d27152e1d650078079215d582a0f8c439781ed
clocksource: sh_mtu2: Rename clock to "fck" in the non-legacy case

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 <laurent.pinchart+renesas@ideasonboard.com>
Tested-by: Wolfram Sang <wsa@sang-engineering.com>
(cherry picked from commit 6dc9693bb3997cb324a2ffb39deaa72081a9bd0d)
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
drivers/clocksource/sh_mtu2.c