From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
Stephen Warren <swarren@nvidia.com>,
"gg@slimlogic.co.uk" <gg@slimlogic.co.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mfd: palmas: initialise client->of_node for dummy created client
Date: Wed, 20 Mar 2013 20:09:13 +0530 [thread overview]
Message-ID: <5149CA11.2070301@nvidia.com> (raw)
In-Reply-To: <20130319172648.GD22168@opensource.wolfsonmicro.com>
On Tuesday 19 March 2013 10:56 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Tue, Mar 19, 2013 at 11:10:34AM -0600, Stephen Warren wrote:
>> On 03/19/2013 10:52 AM, Mark Brown wrote:
>>> This does then make it more complicated for all users of I2C as
>>> they need to become aware of such devices. Not sure that's a
>>> win...
>> Presumably the existing APIs would work identically, and additional
>> APIs would be added for the complex case?
> Right, but we'd have to add the additional APIs to things like regmap
> and ASoC which seems like a kerfuffle.
>
Yes, to add the multiple address list in i2c_client, then adding address
index in i2c apis, adding address index in regmap inits etc. can require
lots of RFE patches in different subsystem. We can keep discussing this
and once conclude, we can go for implementation.
But for now, can I assume that this patch is fine for resolving my
interrupt issue?
Thanks,
Laxman
next prev parent reply other threads:[~2013-03-20 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 8:58 [PATCH] mfd: palmas: initialise client->of_node for dummy created client Laxman Dewangan
2013-03-19 9:23 ` Graeme Gregory
2013-03-19 15:44 ` Stephen Warren
[not found] ` <20130319165228.GC22168@opensource.wolfsonmicro.com>
2013-03-19 17:10 ` Stephen Warren
[not found] ` <20130319172648.GD22168@opensource.wolfsonmicro.com>
2013-03-20 14:39 ` Laxman Dewangan [this message]
2013-04-08 12:55 ` Laxman Dewangan
2013-04-08 16:14 ` 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=5149CA11.2070301@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gg@slimlogic.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
/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