All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: mach-shmobile: sh7372 INTCS support
Date: Thu, 20 May 2010 03:11:16 +0000	[thread overview]
Message-ID: <20100520031116.GB6661@linux-sh.org> (raw)
In-Reply-To: <20100311054221.27152.9839.sendpatchset@t400s>

On Thu, Mar 11, 2010 at 02:42:21PM +0900, Magnus Damm wrote:
> Add support for the sh7372 INTCS interrupt controller.
> 
> INTCS is the interrupt controller for the sh7372 SuperH
> processor core. It is tied into the INTCA interrupt
> controller which interfaces to the ARM processor.
> 
> INTCS support is implemented using a new INTC table
> together with a chained interrupt handler that ties
> into the already supported INTCA controller.

On Wed, May 12, 2010 at 06:03:19PM +0900, Magnus Damm wrote:
> Allow users to build the TMU driver on SH-Mobile ARM.

On Wed, May 12, 2010 at 11:21:14PM +0900, Magnus Damm wrote:
> [PATCH 01/02] ARM: mach-shmobile: Use shared clock framework
> [PATCH 02/02] ARM: mach-shmobile: sh7372 clock framework support V2

On Wed, May 19, 2010 at 07:29:47PM +0900, Magnus Damm wrote:
> Change INTCS_VECT_BASE from 0x3400 to 0x2200.
> 
> The old value 0x3400 gave the INTCA and INTCS interrupt
> conrollers separated spaces, but required ARM support
> for more than 512 NR_IRQS which is not in place at this
> point.
> 
> The value 0x2200 will make some of the INTCA interrupts
> make use of empty INTCS areas. This is a bit more error
> prone but works fine as a workaround for G3, G3 and AP4.

All applied, thanks.

  reply	other threads:[~2010-05-20  3:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11  5:42 [PATCH] ARM: mach-shmobile: sh7372 INTCS support Magnus Damm
2010-05-20  3:11 ` Paul Mundt [this message]
2011-01-18  3:13 ` [PATCH] ARM: mach-shmobile: sh7372 INTCS MFIS2 interrupt update Magnus Damm
2011-01-18  4:50 ` Paul Mundt

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=20100520031116.GB6661@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-sh@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 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.