From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] mfd: add irq domain support for max8997 interrupts
Date: Fri, 9 Dec 2011 14:39:13 +0800 [thread overview]
Message-ID: <20111209063912.GG26952@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAJuYYwSCuu8U2rF3RGAnczXgbh4Px7hMwUhHr=xrhPZ1jEs5DA@mail.gmail.com>
On Fri, Dec 09, 2011 at 12:00:07PM +0530, Thomas Abraham wrote:
> If these gpio's are connected to the host system, and host system sets
> up gpio interrupt notification for these gpio lines, the linux irq
> number for the gpio interrupt would belong to the irq domain of the
> host interrupt controller (gic irq domain in case of exynos).
> Consumers of this interrupt would use the gpio interrupt independent
> of the max8997 irq domain. So irq_base can be maintained private to
> the max8997 mfd driver and its sub-block drivers.
How would you provide this interrupt to the device using it in a non-DT
systemm without passing the irq_base into the device as platform data?
next prev parent reply other threads:[~2011-12-09 6:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 16:27 [PATCH 0/2] Add device tree support for MAX8997 Thomas Abraham
2011-12-08 16:27 ` [PATCH 1/2] mfd: add irq domain support for max8997 interrupts Thomas Abraham
2011-12-08 16:27 ` [PATCH 2/2] regulator: add device tree support for max8997 Thomas Abraham
2011-12-09 2:30 ` Kyungmin Park
2011-12-09 5:17 ` Thomas Abraham
2011-12-09 6:17 ` Mark Brown
2011-12-09 7:25 ` Thomas Abraham
2011-12-09 4:00 ` [PATCH 1/2] mfd: add irq domain support for max8997 interrupts MyungJoo Ham
2011-12-09 4:41 ` Mark Brown
2011-12-09 5:25 ` Thomas Abraham
2011-12-09 6:02 ` Mark Brown
2011-12-09 6:30 ` Thomas Abraham
2011-12-09 6:39 ` Mark Brown [this message]
2011-12-09 7:19 ` Thomas Abraham
2011-12-09 8:15 ` Mark Brown
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=20111209063912.GG26952@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.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 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).