From: Kevin Hilman <khilman@ti.com>
To: linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFT 0/8] ARM: OMAP: remove IP checks from SoC family detection
Date: Thu, 26 Apr 2012 16:29:45 -0700 [thread overview]
Message-ID: <1335482993-14035-1-git-send-email-khilman@ti.com> (raw)
This is a rebased version of this series which is ready for broader
testing. I'd especially appreciate testing from those of you with
AM35x platforms.
Currently, our SoC detection is based on SoC family detection
(using die ID) and the presence of specific IP blocks (or feature.)
This series begins the separation of the SoC family detection and
specific IP detection by completely removing IP detection from the SoC
family detection (cpu_is_*.)
Applies on top of v3.4-rc4, boot tested on AM3517 EVM.
Kevin
Kevin Hilman (8):
ARM: OMAP: remove unused cpu_is macros that depend on specific IP
checks
ARM: OMAP3: clock data: replace 3503/3517 flag with AM35x flag for
UART4
ARM: OMAP3: clock data: treat all AM35x devices the same
ARM: OMAP: AM35x: remove redunant cpu_is checks for AM3505
ARM: OMAP: clock: remove unused CK_3505 flag
ARM: OMAP: remove unused cpu_is_omap3505()
ARM: OMAP: remove unused cpu_is_omap3530()
ARM: OMAP: AM35xx: convert 3517 detection/flags to AM35xx
arch/arm/mach-omap2/clock3xxx_data.c | 22 ++++----------
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 | 4 +--
arch/arm/plat-omap/include/plat/cpu.h | 39 +++++--------------------
9 files changed, 24 insertions(+), 64 deletions(-)
--
1.7.9.2
next reply other threads:[~2012-04-26 23:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 23:29 Kevin Hilman [this message]
2012-04-26 23:29 ` [PATCH/RFT 1/8] ARM: OMAP: remove unused cpu_is macros that depend on specific IP checks Kevin Hilman
2012-04-26 23:29 ` [PATCH/RFT 2/8] ARM: OMAP3: clock data: replace 3503/3517 flag with AM35x flag for UART4 Kevin Hilman
2012-04-26 23:29 ` [PATCH/RFT 3/8] ARM: OMAP3: clock data: treat all AM35x devices the same Kevin Hilman
2012-04-26 23:29 ` [PATCH/RFT 4/8] ARM: OMAP: AM35x: remove redunant cpu_is checks for AM3505 Kevin Hilman
2012-04-26 23:29 ` [PATCH/RFT 5/8] ARM: OMAP: clock: remove unused CK_3505 flag Kevin Hilman
2012-04-30 9:05 ` Jean Pihet
2012-04-30 17:19 ` Kevin Hilman
2012-04-26 23:29 ` [PATCH/RFT 6/8] ARM: OMAP: remove unused cpu_is_omap3505() Kevin Hilman
2012-04-30 9:07 ` Jean Pihet
2012-04-30 9:35 ` Koen Kooi
2012-04-30 17:20 ` Kevin Hilman
2012-04-26 23:29 ` [PATCH/RFT 7/8] ARM: OMAP: remove unused cpu_is_omap3530() Kevin Hilman
2012-04-26 23:29 ` [PATCH/RFT 8/8] ARM: OMAP: AM35xx: convert 3517 detection/flags to AM35xx Kevin Hilman
2012-04-27 22:08 ` [PATCH/RFT 0/8] ARM: OMAP: remove IP checks from SoC family detection Mark A. Greer
2012-04-27 22:25 ` Kevin Hilman
2012-04-28 20:20 ` Derald D. Woods
2012-04-29 9:48 ` Hiremath, Vaibhav
2012-04-30 16:30 ` Mark A. Greer
2012-04-30 16:27 ` Mark A. Greer
2012-04-30 16:25 ` Mark A. Greer
2012-04-30 20:48 ` Kevin Hilman
2012-04-30 23:47 ` Kevin Hilman
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=1335482993-14035-1-git-send-email-khilman@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
/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