From: Sekhar Nori <nsekhar@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Grygorii Strashko <grygorii.strashko@ti.com>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Prabhakar Lad <prabhakar.csengg@gmail.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] gpio: introduce GPIO_DAVINCI kconfig option
Date: Sun, 15 Dec 2013 17:34:29 +0530 [thread overview]
Message-ID: <52AD9ACD.7010507@ti.com> (raw)
In-Reply-To: <CACRpkdbrtyBgMiQ-+J9O5JdfBo8vZLL1rY9F7p1X_rWbr54Qzg@mail.gmail.com>
On Friday 29 November 2013 02:05 PM, Linus Walleij wrote:
> On Thu, Nov 21, 2013 at 4:34 PM, Grygorii Strashko
> <grygorii.strashko@ti.com> wrote:
>
>> The compatible to Davinci GPIO HW block is used by other TI SoCs, like
>> Keystone, where GPIO support is declared as optional.
>>
>> Hence, introduce GPIO_DAVINCI Kconfig option which will allow to enable
>> Davinci GPIO driver for Keystone SoCs when needed. At same time, kept
>> Davinci GPIO driver enabled for Davinci SoCs by default.
>>
>> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>
> Sekhar, same comment here.
Queuing this with your's, Santosh's and Prabhakar's acks.
Thanks,
Sekhar
next prev parent reply other threads:[~2013-12-15 12:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 15:34 [PATCH 0/2] gpio: davinci: preparation fixes and updates to reuse it for Keystone Grygorii Strashko
2013-11-21 15:34 ` [PATCH 1/2] gpio: davinci: get rid of DAVINCI_N_GPIO Grygorii Strashko
2013-11-26 10:27 ` Prabhakar Lad
2013-11-29 8:33 ` Linus Walleij
2013-12-15 11:57 ` Sekhar Nori
2013-11-21 15:34 ` [PATCH 2/2] gpio: introduce GPIO_DAVINCI kconfig option Grygorii Strashko
2013-11-26 10:29 ` Prabhakar Lad
2013-11-29 8:35 ` Linus Walleij
2013-12-15 12:04 ` Sekhar Nori [this message]
2013-11-29 15:41 ` [PATCH 0/2] gpio: davinci: preparation fixes and updates to reuse it for Keystone 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=52AD9ACD.7010507@ti.com \
--to=nsekhar@ti.com \
--cc=grygorii.strashko@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--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