All of lore.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	linux-gpio@vger.kernel.org, nsekhar@ti.com,
	prabhakar.csengg@gmail.com, linux-kernel@vger.kernel.org,
	davinci-linux-open-source@linux.davincidsp.com
Subject: Re: [RFC v1 6/9] arm: dts: keystone: add GPIO device entry
Date: Fri, 29 Nov 2013 11:40:12 -0500	[thread overview]
Message-ID: <5298C36C.8000709@ti.com> (raw)
In-Reply-To: <1385494815-15740-7-git-send-email-grygorii.strashko@ti.com>

On Tuesday 26 November 2013 02:40 PM, Grygorii Strashko wrote:
> This patch adds Keystone GPIO IP device definitions in DT which supports
> up to 32 GPIO lines and each GPIO line can be configured as separate
> interrupt source (so called "unbanked" IRQ).
> 
> For more information see:
>  http://www.ti.com/lit/ug/sprugv1/sprugv1.pdf
> 
> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
> ---
>  arch/arm/boot/dts/keystone.dtsi |   45 +++++++++++++++++++++++++++++++++++++++
>  1 file changed, 45 insertions(+)
> 
Patch 6/9, 7/9, 8/9 and 9/9 needs to be in
a separate series. They all good to me and I
will take them once the GPIO driver re-use gets
sorted out.

Regards,
Santosh


WARNING: multiple messages have this Message-ID (diff)
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	<linux-gpio@vger.kernel.org>, <nsekhar@ti.com>,
	<prabhakar.csengg@gmail.com>, <linux-kernel@vger.kernel.org>,
	<davinci-linux-open-source@linux.davincidsp.com>
Subject: Re: [RFC v1 6/9] arm: dts: keystone: add GPIO device entry
Date: Fri, 29 Nov 2013 11:40:12 -0500	[thread overview]
Message-ID: <5298C36C.8000709@ti.com> (raw)
In-Reply-To: <1385494815-15740-7-git-send-email-grygorii.strashko@ti.com>

On Tuesday 26 November 2013 02:40 PM, Grygorii Strashko wrote:
> This patch adds Keystone GPIO IP device definitions in DT which supports
> up to 32 GPIO lines and each GPIO line can be configured as separate
> interrupt source (so called "unbanked" IRQ).
> 
> For more information see:
>  http://www.ti.com/lit/ug/sprugv1/sprugv1.pdf
> 
> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
> ---
>  arch/arm/boot/dts/keystone.dtsi |   45 +++++++++++++++++++++++++++++++++++++++
>  1 file changed, 45 insertions(+)
> 
Patch 6/9, 7/9, 8/9 and 9/9 needs to be in
a separate series. They all good to me and I
will take them once the GPIO driver re-use gets
sorted out.

Regards,
Santosh


  reply	other threads:[~2013-11-29 16:40 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26 19:40 [RFC v1 0/9] gpio: davinci: reuse for keystone arch Grygorii Strashko
2013-11-26 19:40 ` Grygorii Strashko
2013-11-26 19:40 ` [RFC v1 2/9] gpio: introduce GPIO_DAVINCI kconfig option Grygorii Strashko
2013-11-26 19:40   ` Grygorii Strashko
2013-11-29 15:48   ` Santosh Shilimkar
2013-11-29 15:48     ` Santosh Shilimkar
     [not found] ` <1385494815-15740-1-git-send-email-grygorii.strashko-l0cyMroinI0@public.gmane.org>
2013-11-26 19:40   ` [RFC v1 1/9] gpio: davinci: get rid of DAVINCI_N_GPIO Grygorii Strashko
2013-11-26 19:40     ` Grygorii Strashko
2013-11-29 15:48     ` Santosh Shilimkar
2013-11-29 15:48       ` Santosh Shilimkar
2013-11-26 19:40   ` [RFC v1 3/9] gpio: davinci: use chained_irq_enter/chained_irq_exit API Grygorii Strashko
2013-11-26 19:40     ` Grygorii Strashko
2013-11-29  8:39     ` Linus Walleij
     [not found]     ` <1385494815-15740-4-git-send-email-grygorii.strashko-l0cyMroinI0@public.gmane.org>
2013-11-29 15:49       ` Santosh Shilimkar
2013-11-29 15:49         ` Santosh Shilimkar
2013-12-15 13:25     ` Sekhar Nori
2013-12-15 13:25       ` Sekhar Nori
2013-11-26 19:40   ` [RFC v1 4/9] gpio: davinci: make IRQ initialization soc specific Grygorii Strashko
2013-11-26 19:40     ` Grygorii Strashko
2013-11-29  9:21     ` Linus Walleij
2013-11-29 16:20       ` Santosh Shilimkar
2013-11-26 19:40   ` [RFC v1 5/9] gpio: davinci: reuse for Keystone SoC Grygorii Strashko
2013-11-26 19:40     ` Grygorii Strashko
2013-11-29  9:25     ` Linus Walleij
     [not found]       ` <CACRpkda=5KyvRpN=O5UHhX8S-jYB-0g3272Xg61_jvpCEb7Nzg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-29 16:28         ` Santosh Shilimkar
2013-11-29 16:28           ` Santosh Shilimkar
2013-11-26 19:40 ` [RFC v1 6/9] arm: dts: keystone: add GPIO device entry Grygorii Strashko
2013-11-26 19:40   ` Grygorii Strashko
2013-11-29 16:40   ` Santosh Shilimkar [this message]
2013-11-29 16:40     ` Santosh Shilimkar
2013-11-26 19:40 ` [RFC v1 7/9] ARM: keystone_defconfig: enable gpio support Grygorii Strashko
2013-11-26 19:40   ` Grygorii Strashko
2013-11-26 19:40 ` [RFC v1 8/9] arm: dts: keystone-evm: add LEDs supports Grygorii Strashko
2013-11-26 19:40   ` Grygorii Strashko
2013-11-26 19:40 ` [RFC v1 9/9] ARM: keystone_defconfig: enable LED support Grygorii Strashko
2013-11-26 19:40   ` Grygorii Strashko
2013-11-29  8:37 ` [RFC v1 0/9] gpio: davinci: reuse for keystone arch Linus Walleij
2013-12-02 10:41   ` Grygorii Strashko
2013-12-09 16:20   ` Santosh Shilimkar
2013-12-11 17:55 ` Prabhakar Lad

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=5298C36C.8000709@ti.com \
    --to=santosh.shilimkar@ti.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=grygorii.strashko@ti.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=prabhakar.csengg@gmail.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.