"Hiremath, Vaibhav" <hvaibhav@xxxxxx> writes: >> -----Original Message----- >> From: Hilman, Kevin >> Sent: Saturday, January 07, 2012 12:24 AM >> To: linux-omap@xxxxxxxxxxxxxxx >> Cc: Paul Walmsley; Hiremath, Vaibhav >> Subject: [RFC/PATCH 8/7] ARM: OMAP: AM35xx: convert 3517 detection/flags >> to AM35xx >> >> Currently cpu_is_omap3517() actually detects any device in the AM35x >> family (3517 and no-SGX version 3505.) To make it more clear what is >> being detected, convert the names from 3517 to AM35xx. >> >> For the same reason, replace the CK_3517 flag used in the clock data >> to CK_AM35XX. >> >> Signed-off-by: Kevin Hilman <khilman@xxxxxx> >> --- >> arch/arm/mach-omap2/clock3xxx_data.c | 8 ++++---- >> arch/arm/mach-omap2/hsmmc.c | 8 ++++---- >> arch/arm/mach-omap2/id.c | 7 +++---- >> arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 2 +- >> arch/arm/mach-omap2/powerdomains3xxx_data.c | 2 +- >> arch/arm/mach-omap2/usb-musb.c | 2 +- >> arch/arm/mach-omap2/voltagedomains3xxx_data.c | 2 +- >> arch/arm/plat-omap/include/plat/clkdev_omap.h | 3 +-- >> arch/arm/plat-omap/include/plat/cpu.h | 15 +++++++-------- >> 9 files changed, 23 insertions(+), 26 deletions(-) >> > Is this also right time to change Makefile and Kconfig files??? > Change in board/mach-types/Makefile/Kconfig files will bring > consistency across... Probably, yes. Although Tony might thing that is too much churn. Feel free to spin up a patch and I'll add it to this series and we'll see what Tony thinks. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
