From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/9] lpc2k: Core support
Date: Thu, 17 Mar 2011 21:26:38 +0000 [thread overview]
Message-ID: <20110317212637.GA2927@pulham.picochip.com> (raw)
In-Reply-To: <1300377264-10843-2-git-send-email-ithamar.adema@team-embedded.nl>
Hi,
On Thu, Mar 17, 2011 at 04:54:16PM +0100, Ithamar R. Adema wrote:
> Core files (including IRQ handling) for NXP LPC2K architecture.
>
> Signed-off-by: Ithamar R. Adema <ithamar.adema@team-embedded.nl>
> ---
[...]
> diff --git a/arch/arm/mach-lpc2k/include/mach/entry-macro.S b/arch/arm/mach-lpc2k/include/mach/entry-macro.S
> new file mode 100644
> index 0000000..f6c7a46
> --- /dev/null
> +++ b/arch/arm/mach-lpc2k/include/mach/entry-macro.S
> @@ -0,0 +1,33 @@
> +/*
> + * Copyright 2011 Team Embedded VOF
> + * Ithamar R. Adema <ihamar.adema@team-embedded.nl>
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License version 2 as
> + * published by the Free Software Foundation.
> + */
> +
> +#include <mach/hardware.h>
> +
> + .macro disable_fiq
> + .endm
> +
> + .macro get_irqnr_preamble, base, tmp
> + ldr \base, =APH_VIC_BASE
> + .endm
> +
> + .macro arch_ret_to_user, tmp1, tmp2
> + .endm
> +
> + .macro get_irqnr_and_base, irqnr, irqstat, base, tmp
> + ldr \irqstat, [\base, #0]
> + mov \irqnr, #0
> +1001:
> + tst \irqstat, #1
> + bne 1002f
> + add \irqnr, \irqnr, #1
> + mov \irqstat, \irqstat, lsr #1
> + cmp \irqnr, #32
> + bcc 1001b
> +1002:
Could you adapt the code in arch/arm/include/asm/entry-macro-vic2.S for
a single VIC? That eliminates the looping that you have here.
Jamie
next prev parent reply other threads:[~2011-03-17 21:26 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 [this message]
2011-03-17 21:32 ` Vitaly Wool
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=20110317212637.GA2927@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.