From: Samuel Ortiz <sameo@linux.intel.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: swarren@nvidia.com, broonie@opensource.wolfsonmicro.com,
gg@slimlogic.co.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: palmas: initialise client->of_node for dummy created client
Date: Mon, 8 Apr 2013 18:14:10 +0200 [thread overview]
Message-ID: <20130408161410.GB24058@zurbaran> (raw)
In-Reply-To: <1363683500-24891-1-git-send-email-ldewangan@nvidia.com>
Hi Laxman,
On Tue, Mar 19, 2013 at 02:28:20PM +0530, Laxman Dewangan wrote:
> Palmas device have three different i2c addresses. The device creates
> the two new dummy i2c clients for accessing the register by using
> primary client adapter. This new dummy i2c client have their of_node
> as NULL.
>
> The dummy i2c client is used for registering interrupt and on this,
> it creates irq domain handle. This created irq domain handle has
> their of_node as NULL.
>
> Now when any child of this device is registered through the DT as
> follows:
> palmas: tps65913@58 {
> ::::::::::::::::::
>
> #interrupt-cells = <2>;
> interrupt-controller;
>
> palmas_rtc {
> compatible = "ti,palmas-rtc";
> interrupt-parent = <&palmas>;
> interrupts = <8 0>;
> };
> ::::::::::;;;
> };
>
> And child driver (palam-rtc in this case) get their irq number as
> irq = platform_get_irq(pdev, 0);
>
> The returned irq number is error in this case. The reason is that
> the created irq_domain handle for the palmas interrupt does not have
> valid node and so matching of node fails with palmas node.
>
> Hence initialising the newly dummy created client->of_node with the
> primary clients of_node so that irq_domain handle have proper of_node
> for matching.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
> drivers/mfd/palmas.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
Applied to mfd-next, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2013-04-08 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 8:58 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
2013-04-08 12:55 ` Laxman Dewangan
2013-04-08 16:14 ` Samuel Ortiz [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=20130408161410.GB24058@zurbaran \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gg@slimlogic.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®