public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: sameo@linux.intel.com, swarren@nvidia.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 4/4] mfd: tps65910: pass irq_domain when adding mfd sub devices
Date: Fri, 2 Nov 2012 18:50:55 +0000	[thread overview]
Message-ID: <20121102185055.GI4413@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1351877398-11389-5-git-send-email-ldewangan@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 416 bytes --]

On Fri, Nov 02, 2012 at 10:59:58PM +0530, Laxman Dewangan wrote:
> When adding the sub device "tps65910-rtc", is it passed the
> IO resource IRQ for the interrupt number. This interrupt needs
> to map in the device irq domain. Pass the irq domain of device
> in mfd_add_devices() so that proper irq mapping can be done when
> adding the sub device RTC.

Rewiewed-by: Mark Brown <broonie@opensource.wolfsonmicro.com>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2012-11-02 18:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-02 17:29 [PATCH V3 0/4] mfd: tps65910: use regmap irq framework for interrupt Laxman Dewangan
2012-11-02 17:29 ` [PATCH V3 1/4] mfd: tps65910: Initialize mfd devices after all initialization done Laxman Dewangan
2012-11-02 17:29 ` [PATCH V3 2/4] mfd: tps65910: use regmap irq framework for interrupt support Laxman Dewangan
2012-11-02 17:29 ` [PATCH V3 3/4] mfd: tps65910: move interrupt implementation code to mfd file Laxman Dewangan
2012-11-02 17:29 ` [PATCH V3 4/4] mfd: tps65910: pass irq_domain when adding mfd sub devices Laxman Dewangan
2012-11-02 18:50   ` 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=20121102185055.GI4413@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    --cc=swarren@nvidia.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