From: Sekhar Nori <nsekhar@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
Rob Herring <robh+dt@kernel.org>, <prabhakar.csengg@gmail.com>,
<davinci-linux-open-source@linux.davincidsp.com>,
<linux-gpio@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>
Subject: Re: [PATCH v3 0/2] gpio: davinci: reuse for keystone arch
Date: Thu, 9 Jan 2014 16:01:55 +0530 [thread overview]
Message-ID: <52CE7A9B.9000300@ti.com> (raw)
In-Reply-To: <52CD5BD8.8090903@ti.com>
On Wednesday 08 January 2014 07:38 PM, Santosh Shilimkar wrote:
> On Tuesday 07 January 2014 11:06 PM, Sekhar Nori wrote:
>> On Tuesday 07 January 2014 11:22 PM, Santosh Shilimkar wrote:
>>> Sekhar,
>>>
>>> On Tuesday 24 December 2013 06:41 AM, Grygorii Strashko wrote:
>>>> This series is intended to update Davinci GPIO driver and reuse
>>>> it for Keystone SoCs, because Keystone uses the similar GPIO IP like Davinci.
>>>> Keystone GPIO IP: supports:
>>>> - up to 32 GPIO lines;
>>>> - only unbanked irqs;
>>>>
>>>> See Documentation:
>>>> Keystone - http://www.ti.com/lit/ug/sprugv1/sprugv1.pdf
>>>>
>>>> This series based on:
>>>> https://git.kernel.org/cgit/linux/kernel/git/nsekhar/linux-davinci.git/log/?h=v3.14/gpio
>>>>
>>>> Changes in v3:
>>>> - fixed code, changed by mistake; fixed sparse warning
>>>> Changes in v2:
>>>> - minor comments applied, no functional changes
>>>>
>>>> v2: https://lkml.org/lkml/2013/12/18/135
>>>> v1: https://lkml.org/lkml/2013/12/12/366
>>>>
>>>> Cc: Linus Walleij <linus.walleij@linaro.org>
>>>> Cc: Alexandre Courbot <gnurou@gmail.com>
>>>> Cc: Sekhar Nori <nsekhar@ti.com>
>>>> Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
>>>>
>>>> Grygorii Strashko (2):
>>>> gpio: davinci: don't create irq_domain in case of unbanked irqs
>>>> gpio: davinci: reuse for Keystone SoC
>>>>
>>>> .../devicetree/bindings/gpio/gpio-davinci.txt | 4 +-
>>>> drivers/gpio/gpio-davinci.c | 82 ++++++++++++++------
>>>> 2 files changed, 61 insertions(+), 25 deletions(-)
>>>>
>>> Have you picked up the $subject series in your queue ?
>>
>> Not yet, at least on the new compatible introduction, I need an ack from
>> DT folks.
>>
> I noticed that but the usual 2 weeks period to get ack is over I guess ;-)
> The DT part is really trivial as well but I let you decide.
I just realize that Rob's e-mail address bounces. I have added his
updated address now and hopefully he will see this to provide his ack.
Rob,
We need your ack on 2/2 of this series. If you do not have the patch, I
can forward it to you.
>
>> I am happy with the patches though and have tested them as well, In case
>> I do not get an ack from 2/2 in time, I can at least send 1/2 for
>> inclusion after my first gpio pull request to ARM-SoC gets pulled.
>>
> Would be great to get both of them but if not both at least 1/2.
I had already sent it with my first pull request. Hmph. Everything
except 2/2 of tis series should be in linux-next now.
Thanks,
Sekhar
next prev parent reply other threads:[~2014-01-09 10:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 11:41 [PATCH v3 0/2] gpio: davinci: reuse for keystone arch Grygorii Strashko
2013-12-24 11:41 ` [PATCH v3 1/2] gpio: davinci: don't create irq_domain in case of unbanked irqs Grygorii Strashko
2013-12-24 11:41 ` [PATCH v3 2/2] gpio: davinci: reuse for Keystone SoC Grygorii Strashko
2013-12-24 11:20 ` Prabhakar Lad
2013-12-24 13:27 ` Grygorii Strashko
2013-12-26 4:08 ` Prabhakar Lad
2013-12-27 11:49 ` Grygorii Strashko
2014-01-07 17:52 ` [PATCH v3 0/2] gpio: davinci: reuse for keystone arch Santosh Shilimkar
2014-01-08 4:06 ` Sekhar Nori
2014-01-08 14:08 ` Santosh Shilimkar
2014-01-09 10:31 ` Sekhar Nori [this message]
2014-01-09 14:10 ` Santosh Shilimkar
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=52CE7A9B.9000300@ti.com \
--to=nsekhar@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=gnurou@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=santosh.shilimkar@ti.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;
as well as URLs for NNTP newsgroup(s).