From: Grygorii Strashko <grygorii.strashko-l0cyMroinI0@public.gmane.org>
To: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org"
<davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org>,
Alexandre Courbot
<gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Santosh Shilimkar
<santosh.shilimkar-l0cyMroinI0@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [RESEND][PATCH v4] gpio: davinci: reuse for keystone soc
Date: Tue, 4 Mar 2014 13:28:43 +0200 [thread overview]
Message-ID: <5315B8EB.40806@ti.com> (raw)
In-Reply-To: <CACRpkda=+vnOEfGeZNS7+7WXU4v29gfQYY0xoc8d-sFEfrWqUw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 03/04/2014 11:20 AM, Linus Walleij wrote:
> On Thu, Feb 13, 2014 at 4:58 PM, Grygorii Strashko
> <grygorii.strashko-l0cyMroinI0@public.gmane.org> wrote:
>
>> The similar GPIO HW block is used by keystone SoCs as
>> in Davinci SoCs.
>> Hence, reuse Davinci GPIO driver for Keystone taking into
>> account that Keystone contains ARM GIC IRQ controller which
>> is implemented using IRQ Chip.
>>
>> Documentation:
>> http://www.ti.com/lit/ug/sprugv1/sprugv1.pdf
>>
>> Acked-by: Santosh Shilimkar <santosh.shilimkar-l0cyMroinI0@public.gmane.org>
>> Acked-by: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
>> Signed-off-by: Grygorii Strashko <grygorii.strashko-l0cyMroinI0@public.gmane.org>
>
> Applied! Santosh hunted me down in person so it really happened this
> time...
Thanks a lot :)
>
> Yours,
> Linus Walleij
>
prev parent reply other threads:[~2014-03-04 11:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 15:47 [PATCH v4] gpio: davinci: reuse for keystone soc Grygorii Strashko
[not found] ` <1391615244-12014-1-git-send-email-grygorii.strashko-l0cyMroinI0@public.gmane.org>
2014-02-06 13:20 ` Linus Walleij
[not found] ` <CACRpkdbgteBtuwdEn+Bg+kA1JnEHus2FOfTbj-hm5fKBsw7XeA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-07 13:25 ` Sekhar Nori
2014-02-12 15:03 ` Linus Walleij
2014-02-12 18:00 ` Grygorii Strashko
[not found] ` <52FBB6BC.2060801-l0cyMroinI0@public.gmane.org>
2014-02-13 15:58 ` [RESEND][PATCH " Grygorii Strashko
2014-02-21 14:18 ` Santosh Shilimkar
[not found] ` <53076032.5080202-l0cyMroinI0@public.gmane.org>
2014-02-25 11:52 ` Grygorii Strashko
[not found] ` <1392307125-27927-1-git-send-email-grygorii.strashko-l0cyMroinI0@public.gmane.org>
2014-03-04 9:20 ` Linus Walleij
[not found] ` <CACRpkda=+vnOEfGeZNS7+7WXU4v29gfQYY0xoc8d-sFEfrWqUw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-04 11:28 ` Grygorii Strashko [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=5315B8EB.40806@ti.com \
--to=grygorii.strashko-l0cymroini0@public.gmane.org \
--cc=davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=santosh.shilimkar-l0cyMroinI0@public.gmane.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 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).