From: Archit Taneja <archit@ti.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Linux-OMAP <linux-omap@vger.kernel.org>,
Grant Likely <grant.likely@secretlab.ca>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2] gpio: Enable pcf857x GPIO expander for Device Tree
Date: Tue, 27 Aug 2013 12:30:18 +0530 [thread overview]
Message-ID: <521C4E82.9040309@ti.com> (raw)
In-Reply-To: <7142087.DRSP8TfuKN@avalon>
On Tuesday 27 August 2013 12:17 PM, Laurent Pinchart wrote:
> On Tuesday 27 August 2013 05:20:45 Linus Walleij wrote:
>> On Mon, Aug 26, 2013 at 8:21 AM, Archit Taneja <archit@ti.com> wrote:
>>> Add code to parse the GPIO expander Device Tree node and extract platform
>>> data out of it, and populate the struct 'pcf857x_platform_data'
>>> maintained by the driver. This enables devices to reference the gpio
>>> expander from Device Tree.
>>>
>>> Add DT binding info in Documentation.
>>>
>>> Signed-off-by: Archit Taneja <archit@ti.com>
>>> ---
>>> - v2 posted after quite a while, sorry for the delay!
>>>
>>> Changes in v2:
>>> - second gpeio-cell description corrected in Documentation
>>> - interrupt controller description removed for now, will be added in a
>>> follow up patch
>>> - n_latch description updated
>
> And it seems that the patch conflicts with
>
> https://lkml.org/lkml/2013/8/26/248
>
> :-/
:/
>
> If we end up merging this one, I'd like to at least rename the DT n-latch
> property to pin-initial-states as in my patch and update the documentation, as
> I find it more explicit.
I think your patch is cleaner and more descriptive. The only thing which
I am not clear about in your patch is the extra work done in getting
ngpio, that should be available in i2c_device_id pointer argument in
probe(id points to the array pcf857x_id already available in the driver
with the number of gpios for each chip variant).
Archit
WARNING: multiple messages have this Message-ID (diff)
From: archit@ti.com (Archit Taneja)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] gpio: Enable pcf857x GPIO expander for Device Tree
Date: Tue, 27 Aug 2013 12:30:18 +0530 [thread overview]
Message-ID: <521C4E82.9040309@ti.com> (raw)
In-Reply-To: <7142087.DRSP8TfuKN@avalon>
On Tuesday 27 August 2013 12:17 PM, Laurent Pinchart wrote:
> On Tuesday 27 August 2013 05:20:45 Linus Walleij wrote:
>> On Mon, Aug 26, 2013 at 8:21 AM, Archit Taneja <archit@ti.com> wrote:
>>> Add code to parse the GPIO expander Device Tree node and extract platform
>>> data out of it, and populate the struct 'pcf857x_platform_data'
>>> maintained by the driver. This enables devices to reference the gpio
>>> expander from Device Tree.
>>>
>>> Add DT binding info in Documentation.
>>>
>>> Signed-off-by: Archit Taneja <archit@ti.com>
>>> ---
>>> - v2 posted after quite a while, sorry for the delay!
>>>
>>> Changes in v2:
>>> - second gpeio-cell description corrected in Documentation
>>> - interrupt controller description removed for now, will be added in a
>>> follow up patch
>>> - n_latch description updated
>
> And it seems that the patch conflicts with
>
> https://lkml.org/lkml/2013/8/26/248
>
> :-/
:/
>
> If we end up merging this one, I'd like to at least rename the DT n-latch
> property to pin-initial-states as in my patch and update the documentation, as
> I find it more explicit.
I think your patch is cleaner and more descriptive. The only thing which
I am not clear about in your patch is the extra work done in getting
ngpio, that should be available in i2c_device_id pointer argument in
probe(id points to the array pcf857x_id already available in the driver
with the number of gpios for each chip variant).
Archit
next prev parent reply other threads:[~2013-08-27 7:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 14:05 [PATCH] gpio: Enable pcf857x GPIO expander for Device Tree Archit Taneja
2013-06-06 14:05 ` Archit Taneja
2013-06-17 7:03 ` Archit Taneja
2013-06-17 9:05 ` Linus Walleij
2013-06-17 11:46 ` Archit Taneja
2013-06-19 19:38 ` Linus Walleij
[not found] ` <CAOY=C6HRMKKJsSzVdcQSBabmZxZ7Su_CC6m7qi14h1+mOOyABA@mail.gmail.com>
2013-06-19 19:33 ` Linus Walleij
2013-08-26 6:21 ` [PATCH v2] " Archit Taneja
2013-08-26 6:21 ` Archit Taneja
2013-08-27 3:20 ` Linus Walleij
2013-08-27 3:20 ` Linus Walleij
2013-08-27 6:47 ` Laurent Pinchart
2013-08-27 6:47 ` Laurent Pinchart
2013-08-27 7:00 ` Archit Taneja [this message]
2013-08-27 7:00 ` Archit Taneja
2013-08-27 7:58 ` Laurent Pinchart
2013-08-27 7:58 ` Laurent Pinchart
2013-08-27 5:27 ` [RESEND PATCH " Archit Taneja
2013-08-27 5:27 ` Archit Taneja
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=521C4E82.9040309@ti.com \
--to=archit@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-omap@vger.kernel.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 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.