From: Mark Brown <broonie@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Grant Likely <grant.likely@linaro.org>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: How to create IRQ mappings in a GPIO driver that doesn't control its IRQ domain ?
Date: Thu, 25 Jul 2013 14:53:19 +0100 [thread overview]
Message-ID: <20130725135319.GF9858@sirena.org.uk> (raw)
In-Reply-To: <CACRpkdY-mdLbMY16aMqR9Jwu8qs9q4KNyxOxnwhXiGrAAxpKjg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
On Thu, Jul 25, 2013 at 03:21:35PM +0200, Linus Walleij wrote:
> On Thu, Jul 25, 2013 at 3:15 PM, Mark Brown <broonie@kernel.org> wrote:
> > Are the interrupts in a contiguous block in the controller so you can
> > just pass around the controller and a base number?
> That works with platform data and in-kernel structures, but AFAICT
> device tree has no such "bulk" concept but expects you to list
> each and every line individually in cases like this.
It works fine with domains as well - the domains all have a hwirq number
which is local to the domain context and doesn't correspond to a Linux
interrupt number. If you can say "the X interrupts in this domain
starting at Y correspond to these X GPIOs" then you should be able to
cope. Hopefully.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-25 13:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 23:21 How to create IRQ mappings in a GPIO driver that doesn't control its IRQ domain ? Laurent Pinchart
2013-07-24 20:24 ` Grant Likely
2013-07-25 9:42 ` Laurent Pinchart
2013-07-25 9:20 ` Linus Walleij
2013-07-25 9:45 ` Laurent Pinchart
2013-07-25 13:15 ` Mark Brown
2013-07-25 13:21 ` Linus Walleij
2013-07-25 13:53 ` Mark Brown [this message]
2013-07-25 13:22 ` Laurent Pinchart
2013-07-25 13:55 ` Mark Brown
2013-07-28 5:00 ` Grant Likely
2013-07-31 11:14 ` Laurent Pinchart
2013-07-25 13:19 ` Linus Walleij
2013-07-28 10:07 ` Tomasz Figa
2013-07-31 11:11 ` Laurent Pinchart
2013-07-31 11:29 ` Tomasz Figa
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=20130725135319.GF9858@sirena.org.uk \
--to=broonie@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=g.liakhovetski@gmx.de \
--cc=grant.likely@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox