From: Mark Brown <broonie@kernel.org>
To: Mehar Bajwa <mehar.bajwa@ti.com>
Cc: linux-kernel@vger.kernel.org, sameo@linux.intel.com,
liam.r.girdwood@intel.com, navada@ti.com
Subject: Re: [PATCH V2 2/4] mfd: Interrupt handling support for AIC family
Date: Wed, 1 May 2013 16:46:29 +0100 [thread overview]
Message-ID: <20130501154629.GP26160@sirena.org.uk> (raw)
In-Reply-To: <1366119860-9754-1-git-send-email-mehar.bajwa@ti.com>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
On Tue, Apr 16, 2013 at 07:14:20PM +0530, Mehar Bajwa wrote:
> This provides Interrupt handling features for common interface
> to series of low power AIC audio CODECS.
This looks like it should be able to use regmap-irq if you fix the page
mapping open coding in the core.
> + if (aic->irq_base) {
> + aic->domain = irq_domain_add_legacy(aic->dev->of_node,
> + ARRAY_SIZE(aic_irqs),
> + aic->irq_base, 0,
> + &aic_domain_ops, aic);
> + } else {
> + aic->domain = irq_domain_add_linear(aic->dev->of_node,
> + ARRAY_SIZE(aic_irqs),
> + &aic_domain_ops, aic);
> + /* initiallizing irq_base from irq_domain*/
> + }
irq_domain_add_simple().
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-05-01 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 13:43 [PATCH V2 1/4] mfd: Initial support for Texas Instruments AIC family of CODECs Mehar Bajwa
2013-04-16 13:44 ` [PATCH V2 2/4] mfd: Interrupt handling support for AIC family Mehar Bajwa
2013-04-16 13:44 ` [PATCH V2 3/4] mfd: I2C interface with AIC platform Mehar Bajwa
2013-04-16 13:45 ` [PATCH V2 4/4] mfd: SPI " Mehar Bajwa
2013-05-01 15:47 ` [PATCH V2 3/4] mfd: I2C " Mark Brown
2013-05-01 15:46 ` Mark Brown [this message]
2013-05-01 15:43 ` [PATCH V2 1/4] mfd: Initial support for Texas Instruments AIC family of CODECs 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=20130501154629.GP26160@sirena.org.uk \
--to=broonie@kernel.org \
--cc=liam.r.girdwood@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mehar.bajwa@ti.com \
--cc=navada@ti.com \
--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
all inboxes | Powered by JetHome®