From: Stephen Warren <swarren@wwwdotorg.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
grant.likely@secretlab.ca, rob.herring@calxeda.com,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
swarren@nvidia.com
Subject: Re: [PATCH] gpio: palmas: add dt support
Date: Wed, 27 Mar 2013 09:57:58 -0600 [thread overview]
Message-ID: <51531706.4040608@wwwdotorg.org> (raw)
In-Reply-To: <CACRpkdY_9pEkNfp7L82nGjsjFOi-VXwPHo7_3XwjCz8XcN8osg@mail.gmail.com>
On 03/27/2013 07:00 AM, Linus Walleij wrote:
> On Thu, Mar 21, 2013 at 3:30 PM, Laxman Dewangan <ldewangan@nvidia.com> wrote:
>
>> #ifdef CONFIG_OF_GPIO
>> - palmas_gpio->gpio_chip.of_node = palmas->dev->of_node;
>> + palmas_gpio->gpio_chip.of_node = pdev->dev.of_node;
>> #endif
>
> OK I think that #ifdef is necessary...
Laxman,
Don't we need to resolve and agree on the final DT bindings before we
can start making changes like this? It's not clear yet whether everyone
is on the same page re: how the MFD sub-devices are modelled in DT -
whether each sub-component really is a standalone device, or whether the
MFD itself instantiates all its children based on internal static tables
rather than DT.
Presumably, the answer to that question directly determines whether the
code change above is correct; the correct of_node might be either the
main Palmas node (if DT doesn't represent the MFD components) or it
might be the regulator sub-node (if DT is used to represent MFD components).
Given that, I'm not sure why the Slimlogic people aren't CC'd on this
patch:-(
next prev parent reply other threads:[~2013-03-27 15:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 14:30 [PATCH] gpio: palmas: add dt support Laxman Dewangan
2013-03-21 14:30 ` Laxman Dewangan
[not found] ` <1363876214-25933-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-03-21 17:29 ` Stephen Warren
2013-03-21 17:29 ` Stephen Warren
2013-03-27 13:00 ` Linus Walleij
2013-03-27 15:57 ` Stephen Warren [this message]
[not found] ` <51531706.4040608-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-03-28 6:05 ` Laxman Dewangan
2013-03-28 6:05 ` Laxman Dewangan
[not found] ` <CACRpkdY_9pEkNfp7L82nGjsjFOi-VXwPHo7_3XwjCz8XcN8osg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-03-28 5:59 ` Laxman Dewangan
2013-03-28 5:59 ` Laxman Dewangan
[not found] ` <5153DC24.7040309-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-03-28 14:55 ` Stephen Warren
2013-03-28 14:55 ` Stephen Warren
[not found] ` <515459D8.4010001-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-04-02 9:01 ` Linus Walleij
2013-04-02 9:01 ` Linus Walleij
[not found] ` <CACRpkdYTcEzVMK-7V_T1qxtz1Pbw_um8pzasM=pTJ+vFnZasAg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-02 15:30 ` Stephen Warren
2013-04-02 15:30 ` Stephen Warren
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=51531706.4040608@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rob.herring@calxeda.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 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.