From: Russell King - ARM Linux <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 1/2] versatile: sic: add device tree bindings
Date: Fri, 13 Jan 2012 21:19:58 +0000 [thread overview]
Message-ID: <20120113211958.GE1068@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120113210041.GD22767-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
On Fri, Jan 13, 2012 at 02:00:41PM -0700, Grant Likely wrote:
> Let me look at it a bit. You can leave the initialization loop in
> fpga_irq_init() for now. I'm looking at adding a mask field to
> irq_domain_add_legacy in addition to the host_data pointer. I also
> want to investigate replacing fpga_irq with generic-chip.c. The
> problem I've currently got though is that irq_domain_add_legacy() can
> currently support any number of irqs, but adding a simple mask
> argument will limit it to 32. That won't work for large irq
> controllers like the gic.
The easy answer is not to register the IRQs which don't actually exist
or we don't want to be used out of the set of 32.
However, the problem comes with:
#define PIC_MASK 0xFFD00000
where we have an IRQ23 but no IRQ22.
next prev parent reply other threads:[~2012-01-13 21:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 0:43 [PATCH 0/2] Full DT IRQ support for versatile Jamie Iles
[not found] ` <1326415441-17695-1-git-send-email-jamie-wmLquQDDieKakBO8gow8eQ@public.gmane.org>
2012-01-13 0:44 ` [PATCH 1/2] versatile: sic: add device tree bindings Jamie Iles
[not found] ` <1326415441-17695-2-git-send-email-jamie-wmLquQDDieKakBO8gow8eQ@public.gmane.org>
2012-01-13 2:29 ` Grant Likely
[not found] ` <20120113022932.GB25999-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2012-01-13 10:35 ` Jamie Iles
2012-01-13 21:00 ` Grant Likely
[not found] ` <20120113210041.GD22767-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2012-01-13 21:19 ` Russell King - ARM Linux [this message]
2012-01-13 10:48 ` Russell King - ARM Linux
[not found] ` <20120113104842.GS1068-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2012-01-13 10:58 ` Jamie Iles
2012-01-13 18:41 ` Grant Likely
[not found] ` <20120113184151.GC22767-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2012-01-13 19:04 ` Russell King - ARM Linux
2012-01-13 0:44 ` [PATCH 2/2] versatile: dt: register interrupt controllers from dt Jamie Iles
2012-01-13 1:20 ` [PATCH 0/2] Full DT IRQ support for versatile Grant Likely
[not found] ` <CACxGe6v-gkW+pDP-2hTcf7WqeMBtx+H80Xymj7SqS8nqin9qUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-13 1:42 ` Jamie Iles
2012-01-13 2:31 ` Grant Likely
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=20120113211958.GE1068@n2100.arm.linux.org.uk \
--to=linux-lfz/pmaqli7xmaaqvzeohq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.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).