linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: vitalywool@gmail.com (Vitaly Wool)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/9] lpc2k: Core support
Date: Thu, 17 Mar 2011 22:32:43 +0100	[thread overview]
Message-ID: <AANLkTik1fJKs81fRW+a6N24tFf-wmG+c4p68kVOAxqeA@mail.gmail.com> (raw)
In-Reply-To: <1300377264-10843-2-git-send-email-ithamar.adema@team-embedded.nl>

Hi,

On Thu, Mar 17, 2011 at 4:54 PM, Ithamar R. Adema
<ithamar.adema@team-embedded.nl> wrote:
> Core files (including IRQ handling) for NXP LPC2K architecture.

<snip>
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index e34bf02..331540d 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -490,6 +490,18 @@ config ARCH_LOKI
> ? ? ? ?help
> ? ? ? ? ?Support for the Marvell Loki (88RC8480) SoC.
>
> +config ARCH_LPC2K
> + ? ? ? bool "NXP LPC2K Family"
> + ? ? ? depends on !MMU
> + ? ? ? select CPU_ARM7TDMI
> + ? ? ? select ARM_VIC
> + ? ? ? select GENERIC_TIME
> + ? ? ? select GENERIC_CLOCKEVENTS
> + ? ? ? help
> + ? ? ? ? Support for NXP LPC2K family of SoCs. These SoCs are based on
> + ? ? ? ? an ARM7TDMI-S core, and have optional on-chip flash and SRAM,
> + ? ? ? ? also UART, I2C, SPI, SSP, CAN, RTC, and other peripherals.
> +
> ?config ARCH_LPC32XX
> ? ? ? ?bool "NXP LPC32XX"
> ? ? ? ?select CPU_ARM926T
> @@ -928,6 +940,8 @@ source "arch/arm/mach-ks8695/Kconfig"
>
> ?source "arch/arm/mach-loki/Kconfig"
>
> +source "arch/arm/mach-lpc2k/Kconfig"
> +

is there any good reason why you don't add your stuff to lpc32xx?

~Vitaly

  parent reply	other threads:[~2011-03-17 21:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 15:54 [PATCH 0/9] Support for NXP LPC2K SoCs Ithamar R. Adema
2011-03-17 15:54 ` [PATCH 1/9] lpc2k: Core support Ithamar R. Adema
2011-03-17 21:26   ` Jamie Iles
2011-03-17 21:32   ` Vitaly Wool [this message]
2011-03-17 21:50     ` Ithamar R. Adema
2011-03-17 22:08   ` Kevin Wells
2011-03-17 22:25     ` Ithamar R. Adema
2011-03-17 15:54 ` [PATCH 2/9] lpc2k: Exception vector handling Ithamar R. Adema
2011-03-17 16:18   ` Uwe Kleine-König
2011-03-17 16:28     ` Ithamar R. Adema
2011-03-18  0:43       ` Greg Ungerer
2011-03-17 15:54 ` [PATCH 3/9] lpc2k: clk API Ithamar R. Adema
2011-03-17 22:08   ` Kevin Wells
2011-03-18  9:44     ` Ithamar R. Adema
2011-03-17 22:16   ` Kevin Wells
2011-03-17 22:29     ` Ithamar R. Adema
2011-03-17 15:54 ` [PATCH 4/9] lpc2k: generic time and clockevents Ithamar R. Adema
2011-03-17 21:38   ` Jamie Iles
2011-03-17 22:00     ` Ithamar R. Adema
2011-03-17 15:54 ` [PATCH 5/9] lpc2k: gpiolib Ithamar R. Adema
2011-03-17 15:54 ` [PATCH 6/9] lpc2k: multifunction pin configuration Ithamar R. Adema
2011-03-17 15:54 ` [PATCH 7/9] lpc2k: Add EmbeddedArtists LPC2478 Developer's Kit board Ithamar R. Adema
2011-03-17 22:07   ` Kevin Wells
2011-03-17 22:18     ` Ithamar R. Adema
2011-03-17 22:33   ` Kevin Wells
2011-03-17 22:49     ` Ithamar R. Adema
2011-03-17 15:54 ` [PATCH 8/9] lpc2k: Add UART, SSP, and MCI devices Ithamar R. Adema
2011-03-17 15:54 ` [PATCH 9/9] lpc2k: defconfig for NXP LPC2K platform Ithamar R. Adema
2011-03-17 17:18 ` [PATCH 0/9] Support for NXP LPC2K SoCs Kevin Wells
2011-03-18  0:45 ` Greg Ungerer

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=AANLkTik1fJKs81fRW+a6N24tFf-wmG+c4p68kVOAxqeA@mail.gmail.com \
    --to=vitalywool@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).