From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "sameo@linux.intel.com" <sameo@linux.intel.com>,
"lrg@ti.com" <lrg@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"g.liakhovetski@gmx.de" <g.liakhovetski@gmx.de>
Subject: Re: [PATCH V4 1/2] mfd: add TI TPS80031 mfd core driver
Date: Fri, 16 Nov 2012 05:47:15 -0500 [thread overview]
Message-ID: <50A619B3.9000607@nvidia.com> (raw)
In-Reply-To: <20121115075052.GJ7599@opensource.wolfsonmicro.com>
On 11/15/2012 02:50 AM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Wed, Nov 14, 2012 at 09:09:28PM +0530, Laxman Dewangan wrote:
>> TPS80031/ TPS80032 Fully Integrated Power Management with Power
>> Path and Battery Charger. The device provides five configurable
>> step-down converters, 11 general purpose LDOs, USB OTG Module,
>> ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
>> Power Path from USB, 32K clock generator.
> Reviwed-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
This patch use the function regmap_irq_get_domain() which is not in mfd
subsystem. So either it need to go to regmap branch or Samuel need to
pull this change.
It is good that it will apply on the same way as discussed in patch
[PATCH V3 RESEND 0/4] mfd: tps65910: use regmap irq framework for interrupt
next prev parent reply other threads:[~2012-11-16 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 15:39 [PATCH V4 1/2] mfd: add TI TPS80031 mfd core driver Laxman Dewangan
2012-11-14 15:39 ` [PATCH 2/2] regulator: tps80031: add prefix TPS80031 on common defines Laxman Dewangan
2012-11-15 5:36 ` Mark Brown
2012-11-15 7:50 ` [PATCH V4 1/2] mfd: add TI TPS80031 mfd core driver Mark Brown
2012-11-16 10:47 ` Laxman Dewangan [this message]
2012-11-21 13:24 ` Samuel Ortiz
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=50A619B3.9000607@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@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;
as well as URLs for NNTP newsgroup(s).