| commit | 67fde41ea4251f722b4466597c479fb42fccac2c | |
| author | Magnus Damm <damm@opensource.se> | |
| Wed, 24 Jul 2013 03:53:15 +0000 (24 12:53 +0900) | ||
| committer | Simon Horman <horms+renesas@verge.net.au> | |
| Wed, 24 Jul 2013 07:35:30 +0000 (24 16:35 +0900) | ||
| tree | 3bd8c9de8e2cfd6e8ae43193248c6733e0d3d34e | treesnapshot (tar.gz zip) |
| parent | 5717bcf3712fc30c8b4b7f714ebbf0bfcb922bb6 | commitdiff |
ARM: shmobile: r8a73a4: Remove ->init_machine() special case
No need to special case r8a73a4 ->init_machine(),
so get rid of undesired cpufreq platform device
from the generic long term r8a73a4 DT support code.
For short term support on APE6EVM the DT reference
implementation already adds a "cpufreq-cpu0" platform
device so that can be used for development.
Regarding more long term cpufreq support, perhaps
it makes sense to adjust the cpufreq driver to check
for DT information directly instead of using a
platform device for software configuration and DT
for hardware parameters.
Signed-off-by: Magnus Damm <damm@opensource.se>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
No need to special case r8a73a4 ->init_machine(),
so get rid of undesired cpufreq platform device
from the generic long term r8a73a4 DT support code.
For short term support on APE6EVM the DT reference
implementation already adds a "cpufreq-cpu0" platform
device so that can be used for development.
Regarding more long term cpufreq support, perhaps
it makes sense to adjust the cpufreq driver to check
for DT information directly instead of using a
platform device for software configuration and DT
for hardware parameters.
Signed-off-by: Magnus Damm <damm@opensource.se>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
| arch/arm/mach-shmobile/setup-r8a73a4.c | diffblobblamehistory |