From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: add initial support for Picochip picoXcell SoC
Date: Mon, 6 Dec 2010 10:25:21 +0000 [thread overview]
Message-ID: <20101206102521.GC2891@pulham.picochip.com> (raw)
In-Reply-To: <1290506774-17895-1-git-send-email-jamie@jamieiles.com>
On Tue, Nov 23, 2010 at 10:06:01AM +0000, Jamie Iles wrote:
> Hi,
>
> This patch series adds support for the Picochip picoXcell series of
> femotcell SoC's. There are currently two device families - PC3X2 and
> PC3X3. Both include an ARM1176JZ-S, 100Mb Ethernet controller, 2xDMA
> controllers, eFuses, crypto offload engines and Picochip's array
> processor the picoArray. This patch series adds support for the base
> chip support including timers, gpio, pin muxing, clocks and pm and also
> the PC7302 development board that can take either PC3X2 or PC3X3 devices.
>
> This patch series is based off of linux-next (next-20101122) and also requires
> the following patches:
>
> - 8250: add a UPIO_DWAPB32 for 32 bit accesses (v2):
> http://marc.info/?l=linux-serial&m=129043658715199&w=2
> - debug-8250: add a 32 bit mode:
> http://marc.info/?l=linux-arm-kernel&m=129044061221371&w=2
Does anyone have any comments on this patch series?
Thanks,
Jamie
prev parent reply other threads:[~2010-12-06 10:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 10:06 ARM: add initial support for Picochip picoXcell SoC Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 01/13] picoxcell: add support for picoXcell Jamie Iles
2010-11-26 11:08 ` [PATCH] " Jamie Iles
2010-12-08 16:09 ` [RFC PATCH 01/13] " Russell King - ARM Linux
2010-12-08 16:52 ` Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 02/13] picoxcell: add support for AXI bus snoopers Jamie Iles
2010-12-08 16:10 ` Russell King - ARM Linux
2010-12-08 16:52 ` Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 03/13] picoxcell: add support for the system timers Jamie Iles
2010-11-26 11:11 ` [RFC PATCHv2] " Jamie Iles
2010-12-08 16:14 ` Russell King - ARM Linux
2010-12-08 17:26 ` Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 04/13] picoxcell: add a pin muxing infrastructure Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 05/13] picoxcell: add gpio infrastructure Jamie Iles
2010-11-30 18:08 ` [RFC PATCHv2 " Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 06/13] picoxcell: add support for system clks Jamie Iles
2010-12-08 16:18 ` Russell King - ARM Linux
2010-12-08 17:39 ` Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 07/13] picoxcell: add common SoC devices Jamie Iles
2010-11-26 11:13 ` [RFC PATCHv2] " Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 08/13] picoxcell: add cpufreq support Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 09/13] picoxcell: add support for pm Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 10/13] picoxcell: add chained GPIO IRQ handlers Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 11/13] picoxcell: add support for pc3x2 devices Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 12/13] picoxcell: add support for pc3x3 devices Jamie Iles
2010-11-26 11:14 ` [RFC PATCHv2] " Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 13/13] picoxcell: add support for the PC7302 development board Jamie Iles
2010-11-30 18:10 ` [RFC PATCHv2 10/13] picoxcell: add chained GPIO IRQ handlers Jamie Iles
2010-12-06 10:25 ` Jamie Iles [this message]
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=20101206102521.GC2891@pulham.picochip.com \
--to=jamie@jamieiles.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).