From: Stephen Warren <swarren@wwwdotorg.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
"gg@slimlogic.co.uk" <gg@slimlogic.co.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Stephen Warren <swarren@nvidia.com>,
"ian@slimlogic.co.uk" <ian@slimlogic.co.uk>
Subject: Re: [PATCH] mfd: palmas: provide irq flags through DT/platform data
Date: Fri, 01 Mar 2013 12:34:40 -0700 [thread overview]
Message-ID: <513102D0.5030609@wwwdotorg.org> (raw)
In-Reply-To: <20130301131633.GB25302@opensource.wolfsonmicro.com>
On 03/01/2013 06:16 AM, Mark Brown wrote:
> On Fri, Mar 01, 2013 at 06:25:24PM +0530, Laxman Dewangan wrote:
>> On Friday 01 March 2013 06:13 PM, Mark Brown wrote:
>
>>> This can't be a generic problem on ARM systems, I'm pretty sure
>>> the primary users of palmas would've noticed, this is more of a
>>> new feature isn't it?
>
>> I think it is tested with eval board and connected to gpio
>> interrupt and hence it is not noticed.
>
> One of the palmas chips is the default PMIC for OMAP5 isn't it?
A tangential question more re: DT bindings for it:
Is Palmas a family of chips rather than a single chip then? That
implies that the DT would need two compatible values, e.g.:
compatible = "ti,12345", "ti,palmas";
... where "12345" is the actual chip name.
... rather than just the following which IIRC was in the example in
the DT binding document in another patch series:
compatible = "ti,palmas";
next prev parent reply other threads:[~2013-03-01 19:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 12:34 [PATCH] mfd: palmas: provide irq flags through DT/platform data Laxman Dewangan
2013-03-01 12:43 ` Mark Brown
2013-03-01 12:55 ` Laxman Dewangan
2013-03-01 13:16 ` Mark Brown
2013-03-01 19:34 ` Stephen Warren [this message]
2013-03-02 3:35 ` Mark Brown
2013-03-02 12:13 ` Graeme Gregory
2013-03-02 12:21 ` 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=513102D0.5030609@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gg@slimlogic.co.uk \
--cc=ian@slimlogic.co.uk \
--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