From: Samuel Ortiz <sameo@linux.intel.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: broonie@opensource.wolfsonmicro.com, swarren@nvidia.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 RESEND 0/4] mfd: tps65910: use regmap irq framework for interrupt
Date: Tue, 13 Nov 2012 20:56:37 +0100 [thread overview]
Message-ID: <20121113195637.GQ27828@sortiz-mobl> (raw)
In-Reply-To: <1352815439-26040-1-git-send-email-ldewangan@nvidia.com>
Hi Laxman,
On Tue, Nov 13, 2012 at 07:33:55PM +0530, Laxman Dewangan wrote:
> This patch series has following change:
> - Use regmap irq framework for interrupt registration. Corrected the
> register bit definition for interrupts.
> - Move the irq table to tps65910.c and get rid of tps65910-irq.c.
> - Raarrange the init sequence of different sub moduled of tps65910 like
> irq, clock and then mfd devices.
> - Export the irq domain handle from regmap to use in mfd driver.
> - Pass the irq domain in mfd_add_devices to have proper interrupt mapping
> for sub devices like RTC.
>
>
> Changes from V1:
> - rearrange patch on which older patch3 become the new patch 1.
> - Add stub for new api in the regmap.
> - Add empty line if paragraph change in description.
>
> Changes from V2:
> - Remove the older 4th patch where API for getting irq_domain was added
> in regmap. It is already taken care by Mark B.
The patchset looks fine, but it should either go through Mark's tree or I
should merge Mark's regmap_irq_get_domain patch to my for-next branch.
Mark, any preference ?
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-11-13 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 14:03 [PATCH V3 RESEND 0/4] mfd: tps65910: use regmap irq framework for interrupt Laxman Dewangan
2012-11-13 14:03 ` [PATCH V3 RESEND 1/4] mfd: tps65910: Initialize mfd devices after all initialization done Laxman Dewangan
2012-11-13 14:03 ` [PATCH RESEND V3 2/4] mfd: tps65910: use regmap irq framework for interrupt support Laxman Dewangan
2012-11-13 14:03 ` [PATCH V3 RESEND 3/4] mfd: tps65910: move interrupt implementation code to mfd file Laxman Dewangan
2012-11-13 14:03 ` [PATCH V3 RESEND 4/4] mfd: tps65910: pass irq_domain when adding mfd sub devices Laxman Dewangan
2012-11-13 19:56 ` Samuel Ortiz [this message]
2012-11-14 1:24 ` [PATCH V3 RESEND 0/4] mfd: tps65910: use regmap irq framework for interrupt Mark Brown
2012-11-18 23:23 ` Samuel Ortiz
2012-11-19 3:50 ` Laxman Dewangan
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=20121113195637.GQ27828@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.