From: hvaibhav@ti.com (hvaibhav at ti.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH-V3 0/4] Introducing TI's New SoC/board AM335XEVM
Date: Tue, 20 Sep 2011 20:02:18 +0530 [thread overview]
Message-ID: <1316529142-27564-1-git-send-email-hvaibhav@ti.com> (raw)
In-Reply-To: <hvaibhav@ti.com>
From: Vaibhav Hiremath <hvaibhav@ti.com>
This patch set adds support for AM335x device having
Cortex-A8 MPU.
AM335X is treated as another OMAP3 variant, where,
along with existing cpu class OMAP34XX, new cpu class AM33XX is created
and the respective type is AM335X, which is newly added device in the family.
This means, cpu_is_omap34xx(), cpu_is_am33xx() and
cpu_is_am335x() checks return success for AM335X.
Also, I have validated OMAP3 boot test with this patch-series on OMAP3EVM.
Changes from V1(RFC):
- Created separate cpu/SoC class for AM33XX family of devices,
due to all known facts. This is been mentioned in main-chain
https://patchwork.kernel.org/patch/1056312/
- BUG Fix in debug-macro.S, which was leading to build failure.
https://patchwork.kernel.org/patch/1056302/
Changes from V2(RFC):
- Rebased against Paul's OMAP_CHIP* cleanup patches
git://git.pwsan.com/linux-2.6 omap_chip_remove_cleanup_3.2
- Removed dependancy on Hemant's submitted patches for TI814X
support, in order to get it upstream.
Afzal Mohammed (4):
arm:omap:am33xx: Update common omap platform files
arm:omap:am33xx: Update common OMAP machine specific sources
arm:omap:am33xx: Create board support and enable build for AM335XEVM
arm:omap:am33xx: Add low level debugging support
arch/arm/mach-omap2/Kconfig | 10 ++++
arch/arm/mach-omap2/Makefile | 2 +
arch/arm/mach-omap2/board-am335xevm.c | 57 ++++++++++++++++++++++++
arch/arm/mach-omap2/clock.c | 2 +-
arch/arm/mach-omap2/clock.h | 2 +-
arch/arm/mach-omap2/clock3xxx_data.c | 6 ++-
arch/arm/mach-omap2/common.c | 16 +++++++
arch/arm/mach-omap2/id.c | 10 +++-
arch/arm/mach-omap2/include/mach/debug-macro.S | 22 +++++++++
arch/arm/mach-omap2/io.c | 25 ++++++++++
arch/arm/mach-omap2/opp2xxx.h | 2 +-
arch/arm/mach-omap2/serial.c | 6 +-
arch/arm/plat-omap/include/plat/am33xx.h | 25 ++++++++++
arch/arm/plat-omap/include/plat/clkdev_omap.h | 1 +
arch/arm/plat-omap/include/plat/clock.h | 3 +-
arch/arm/plat-omap/include/plat/common.h | 1 +
arch/arm/plat-omap/include/plat/cpu.h | 25 ++++++++++
arch/arm/plat-omap/include/plat/hardware.h | 1 +
arch/arm/plat-omap/include/plat/io.h | 20 ++++++++
arch/arm/plat-omap/include/plat/omap34xx.h | 2 +
arch/arm/plat-omap/include/plat/serial.h | 4 ++
arch/arm/plat-omap/include/plat/uncompress.h | 6 +++
arch/arm/plat-omap/io.c | 5 ++
23 files changed, 243 insertions(+), 10 deletions(-)
create mode 100644 arch/arm/mach-omap2/board-am335xevm.c
create mode 100644 arch/arm/plat-omap/include/plat/am33xx.h
next reply other threads:[~2011-09-20 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 14:32 hvaibhav at ti.com [this message]
2011-09-26 9:21 ` [PATCH-V3 0/4] Introducing TI's New SoC/board AM335XEVM Hiremath, Vaibhav
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=1316529142-27564-1-git-send-email-hvaibhav@ti.com \
--to=hvaibhav@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).