diff options
author | Tony Lindgren <tony@atomide.com> | 2012-11-14 01:32:24 +0400 |
---|---|---|
committer | Tony Lindgren <tony@atomide.com> | 2012-11-14 01:32:24 +0400 |
commit | 558a0780b0a04862a678f7823215424b4e5501f9 (patch) | |
tree | d68f98b9a905557ad95ba97090e99087da30fabd /arch/arm/mach-omap2/prm2xxx.h | |
parent | 89ab216b33ba9405880fd3d89531305a931bc70f (diff) | |
parent | f9ae32a74f0242cbef76d9baa10993d707be1714 (diff) | |
download | linux-558a0780b0a04862a678f7823215424b4e5501f9.tar.xz |
Merge tag 'omap-cleanup-c-for-3.8' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into omap-for-v3.8/clock
Convert the OMAP2+ clock code and data to rely on the common
clock framework for internal bookkeeping and the driver API.
Basic test logs for this branch on top of Tony's cleanup-prcm branch
at commit c9d501e5cb0238910337213e12a09127221c35d8 are here:
http://www.pwsan.com/omap/testlogs/common_clk_devel_3.8_rebase/20121112192516/
However, cleanup-prcm at c9d501e5 does not include some fixes
that are needed for a successful test. With several reverts,
fixes, and workarounds applied, the following test logs were
obtained:
http://www.pwsan.com/omap/testlogs/TEST_common_clk_devel_3.8_rebase/20121112192300/
which indicate that the series tests cleanly.
N.B. The common clock data addition patches result in many
checkpatch warnings of the form "WARNING: static const char *
array should probably be static const char * const". However, it
appears that resolving these would require changes to the CCF
itself. So the resolution of these warnings is being postponed
until that can be coordinated.
These patches result in a ~55KiB increase in runtime kernel memory
usage when booting omap2plus_defconfig kernels.
Conflicts:
arch/arm/mach-omap2/clock33xx_data.c
arch/arm/mach-omap2/clock3xxx_data.c
arch/arm/mach-omap2/clock44xx_data.c
Diffstat (limited to 'arch/arm/mach-omap2/prm2xxx.h')
0 files changed, 0 insertions, 0 deletions