From: Kevin Hilman <khilman@ti.com>
To: Tony Lindgren <tony@atomide.com>, linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] ARM: OMAP3: cleanup AM35xx SoC detection
Date: Mon, 07 May 2012 10:33:41 -0700 [thread overview]
Message-ID: <87zk9j5216.fsf@ti.com> (raw)
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")
Tony,
Kevin Hilman <khilman@ti.com> 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(-)
next prev parent reply other threads:[~2012-05-07 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 23:37 [PATCH 0/2] ARM: OMAP3: cleanup AM35xx SoC detection Kevin Hilman
2012-04-30 23:37 ` [PATCH 1/2] ARM: OMAP: AM35xx: remove redunant cpu_is checks for AM3505 Kevin Hilman
2012-04-30 23:37 ` [PATCH 2/2] ARM: OMAP: AM35xx: convert 3517 detection/flags to AM35xx Kevin Hilman
2012-05-08 22:15 ` Tony Lindgren
2012-05-07 17:33 ` Kevin Hilman [this message]
2012-05-08 20:58 ` [PATCH 0/2] ARM: OMAP3: cleanup AM35xx SoC detection Tony Lindgren
2012-05-08 21:17 ` Kevin Hilman
2012-05-08 22:17 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zk9j5216.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox