From: wellsk40@gmail.com (Kevin Wells)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/10] ARM: LPC32XX: New architecture support
Date: Tue, 26 Jan 2010 15:58:22 -0800 [thread overview]
Message-ID: <1264550302.6528.2@usb10132> (raw)
This patch series adds support for the LPC32XX processor and includes
updates and fixes from review comments based on the previous RFC posts
from late November (thanks to everyone that reviewed and offered
feedback and suggestions).
This also adds full power and event management.
The previous i2c-pnx and pnx4008-wdt changes submitted by RK are
required to build a system based on these patches.
I would like inclusion into the Linux source tree with this code and
will start rolling in the other support drivers (net, RTC, TS, etc)
in later patches.
Patch summary
[PATCH 01/10] ARM: LPC32XX: Changes to existing files to support the
LPC32XX architecture
[PATCH 02/10] ARM: LPC32XX: arch Kconfig, platform Kconfig, and
makefiles
[PATCH 03/10] ARM: LPC32XX: core architecture files
[PATCH 04/10] ARM: LPC32XX: common architecture functions and structures
[PATCH 05/10] ARM: LPC32XX: clock tree support
[PATCH 06/10] ARM: LPC32XX: power and event management
[PATCH 07/10] ARM: LPC32XX: Phytec PHY3250 platform support file
[PATCH 08/10] ARM: LPC32XX: uncompress output and printascii() output
functions
[PATCH 09/10] ARM: LPC32XX: architecture header files
[PATCH 10/10] ARM: LPC32XX: Phytec PHY3250 default kernel config
thanks,
Kevin Wells
NXP Semiconductors
next reply other threads:[~2010-01-26 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 23:58 Kevin Wells [this message]
2010-01-27 11:23 ` [PATCH 00/10] ARM: LPC32XX: New architecture support Luotao Fu
-- strict thread matches above, loose matches on Subject: below --
2010-01-27 0:13 Kevin Wells
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=1264550302.6528.2@usb10132 \
--to=wellsk40@gmail.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).