From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
sameo@linux.intel.com, Marek Vasut <marex@denx.de>,
ashish.jangam@kpitcummins.com, dchen@diasemi.com, arnd@arndb.de,
kernel@pengutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mfd: da9052-core: Use regmap_irq_get_virq() and fix the probe
Date: Wed, 3 Oct 2012 19:08:08 +0100 [thread overview]
Message-ID: <20121003180808.GH4360@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAOMZO5AKf0uL9p-cSd7D5XeB6Q9s5EPHDjAgwfkXGGXVLPreMw@mail.gmail.com>
On Wed, Oct 03, 2012 at 01:04:33PM -0300, Fabio Estevam wrote:
> On Mon, Oct 1, 2012 at 7:22 AM, Mark Brown
> > I don't understand what this irq_chip or the custom domain you're adding
> > are for?
> I declared da9052_irq_chip because I do the following:
> irq_set_chip_and_handler(virq, &da9052_irq_chip, handle_level_irq);
> I am following the arizona-irq approach.
> If this is not suitable, can you please point me to some driver that
> does not define irq_chip and can still do setup
> "irq_set_chip_and_handler()"?
Any other regmap-irq user. The reason the Arizona driver is doing this
is that it has two interrupt controllers in it, one for the main chip
and one for the always on domain, which is why it registers two
regmap-irq domains. Notice that there's only two subinterrupts in the
primary domain.
prev parent reply other threads:[~2012-10-03 18:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 1:57 [PATCH v2] mfd: da9052-core: Use regmap_irq_get_virq() and fix the probe Fabio Estevam
2012-09-28 6:42 ` Arnd Bergmann
2012-09-28 10:45 ` Fabio Estevam
2012-09-28 11:34 ` Arnd Bergmann
2012-09-28 10:52 ` Mark Brown
2012-09-28 11:35 ` Arnd Bergmann
2012-09-28 10:49 ` Mark Brown
2012-09-28 14:33 ` Fabio Estevam
2012-09-28 14:29 ` Mark Brown
2012-09-28 15:37 ` Fabio Estevam
2012-09-28 15:51 ` Mark Brown
2012-09-28 20:34 ` Fabio Estevam
2012-10-01 10:22 ` Mark Brown
2012-10-03 16:04 ` Fabio Estevam
2012-10-03 18:08 ` Mark Brown [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=20121003180808.GH4360@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=arnd@arndb.de \
--cc=ashish.jangam@kpitcummins.com \
--cc=dchen@diasemi.com \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=sameo@linux.intel.com \
/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