Clean up the SoC detection code for some OMAP3 devices. The main goal
is to make the AM3517 family detection code work like the rest of the
OMAP3 SoCs, although this series does some other cleanup of this code
at the same time. This patch series will be a prerequisite for the
OMAP_CHIP removal series.
Tested locally on an OMAP3530ES2 BeagleBoard C2 and a OMAP3730ES1
BeagleBoard A2. These are the only OMAP3 boards I have access to
right now - testing welcomed from people with other OMAP3 families or
ES levels. Thanks to Igor Grinberg <grinb...@compulab.co.il> and
Abhilash Koyamangalath <abhilash...@ti.com> for their help testing
these patches on AM3517 boards.
This third version fixes another 3517/3505 bug in the first patch.
- Paul
---
id_3517_cleanup_3.2
text data bss dec hex filename
6330180 656956 5591124 12578260 bfedd4 vmlinux.omap2plus_defconfig.orig
6329924 656956 5591124 12578004 bfecd4
vmlinux.omap2plus_defconfig.patched
Paul Walmsley (6):
OMAP3: id: remove identification codes that only correspond to marketing
names
OMAP3: id: remove useless strcpy()s
OMAP3: id: use explicit omap_revision codes for 3505/3517 ES levels
OMAP3: id: add fallthrough warning; fix some CodingStyle issues
OMAP3: id: remove duplicate code for testing SoC ES level
OMAP2+: id: remove OMAP_REVBITS_* macros
arch/arm/mach-omap2/clock3xxx_data.c | 11 ++-
arch/arm/mach-omap2/id.c | 136 ++++++++++++---------------------
arch/arm/plat-omap/include/plat/cpu.h | 46 ++++-------
3 files changed, 76 insertions(+), 117 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
