From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: vt8500: multiplatform for 3.8
Date: Sun, 23 Sep 2012 12:35:24 +0000 [thread overview]
Message-ID: <201209231235.24679.arnd@arndb.de> (raw)
In-Reply-To: <1348372670.28422.6.camel@gitbox>
On Sunday 23 September 2012, Tony Prisk wrote:
> I just took a cursory look over the work required for enabling
> multiplatform support for v3.8 for arch-vt8500.
>
> There are 2 files I don't know what to do with in
> arch-vt8500/include/mach:
>
> 1) entry-macro.S
> Contains some low-level irq macro's.
The solution is to enable CONFIG_MULTI_IRQ_HANDLER (implied in
CONFIG_MULTIPLATFORM), and implement the same code in C, and then
set the .handle_irq callback in the your machine descriptor
to this function.
> 2) irqs.h
> Only contains '#define NR_IRQS 128' so I thought it would be easy enough
> to get rid of, but it looks like I need to enable SPARSE_IRQ to drop it,
> which will require some coding - what exactly is SPARSE_IRQ and what's
> required to make it work?
SPARSE_IRQ (in combination with IRQDOMAIN) removes the direct mapping
between hardware IRQ numbers and Linux IRQ numbers. You already have
IRQ domain support in the irq driver. If all IRQ numbers are parsed
from the device tree, you can convert this from legacy to linear domain
to cut the last ties (the local irq_cnt variable) and just set SPARSE_IRQ
without reserving any legacy interrupts. Some platforms put an nr_irqs
variable into the machine descriptor as an intermediate step, but I think
you don't even need that.
Arnd
prev parent reply other threads:[~2012-09-23 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 3:57 vt8500: multiplatform for 3.8 Tony Prisk
2012-09-23 12:35 ` Arnd Bergmann [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=201209231235.24679.arnd@arndb.de \
--to=arnd@arndb.de \
--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.