From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCH 0/2] ARM: OMAP3: cleanup AM35xx SoC detection Date: Mon, 07 May 2012 10:33:41 -0700 Message-ID: <87zk9j5216.fsf@ti.com> References: <1335829030-19431-1-git-send-email-khilman@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from na3sys009aog118.obsmtp.com ([74.125.149.244]:33388 "EHLO na3sys009aog118.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757078Ab2EGRd2 (ORCPT ); Mon, 7 May 2012 13:33:28 -0400 Received: by pbcwz7 with SMTP id wz7so7129564pbc.30 for ; Mon, 07 May 2012 10:33:26 -0700 (PDT) In-Reply-To: <1335829030-19431-1-git-send-email-khilman@ti.com> (Kevin Hilman's message of "Mon, 30 Apr 2012 16:37:08 -0700") Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Tony Lindgren , linux-omap@vger.kernel.org Cc: linux-arm-kernel@lists.infradead.org Tony, Kevin Hilman writes: > The detection of AM35xx SoCs is confusing and has redundancies. Clean > this up so that SoC detection is only based on SoC family: AM35xx. Since these aren't PM related, can you queue these with other cleanups for v3.5. This is now independent from the similar changes made to the clock fwk which Paul is queuing. Once both series are merged, I'll have one final patch that removes all users of cpu_is_omap35*. Kevin > Kevin Hilman (2): > ARM: OMAP: AM35xx: remove redunant cpu_is checks for AM3505 > ARM: OMAP: AM35xx: convert 3517 detection/flags to AM35xx > > 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/cpu.h | 8 ++++++++ > 7 files changed, 19 insertions(+), 12 deletions(-)