From: Sanjeev Premi <premi@ti.com>
To: linux-omap@vger.kernel.org
Cc: Sanjeev Premi <premi@ti.com>
Subject: [PATCH 0/2] Introduce support for AM35xx
Date: Tue, 27 Oct 2009 19:32:18 +0530 [thread overview]
Message-ID: <1256652138-5669-1-git-send-email-premi@ti.com> (raw)
This patch adds support for the recently announced
AM3505 and AM3517 devices from Texas Instruments.
It also defines the AM3517 EVM board. Detailed
support will follow in subsequent patches.
[1] http://www.ti.com/sitara
[2] http://www.ti.com/arm
[3] http://tiexpressdsp.com/index.php?title=Applications_Processors_Crossreference
[4] http://marc.info/?l=linux-omap&m=125615009412281&w=2
The patches have been created against omap-next branch.
Sanjeev Premi (2):
AM35xx: Runtime detection of the device
AM35xx: Define the AM3517EVM board
arch/arm/mach-omap2/Kconfig | 4 +++
arch/arm/mach-omap2/id.c | 43 ++++++++++++++++++++++++++++----
arch/arm/plat-omap/include/plat/cpu.h | 12 +++++++++
3 files changed, 53 insertions(+), 6 deletions(-)
next reply other threads:[~2009-10-27 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 14:02 Sanjeev Premi [this message]
2009-11-02 13:45 ` [PATCH 0/2] Introduce support for AM35xx Premi, Sanjeev
2009-11-10 13:41 ` Premi, Sanjeev
2009-11-11 3:02 ` 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=1256652138-5669-1-git-send-email-premi@ti.com \
--to=premi@ti.com \
--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