All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Vitaly Andrianov <vitalya@ti.com>,
	Kevin Hilman <khilman@linaro.org>
Cc: Alexandre Courbot <gnurou@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] gpio/davinci: add interrupt support for GPIOs 16-31
Date: Thu, 16 Jul 2015 14:34:18 +0530	[thread overview]
Message-ID: <55A77392.30400@ti.com> (raw)
In-Reply-To: <CACRpkda-OSsFdGHN9de00TsQjgdzC1Eg=vHXpeSvqBKH64wPmg@mail.gmail.com>

On Tuesday 14 July 2015 07:31 PM, Linus Walleij wrote:
> On Thu, Jun 18, 2015 at 7:10 PM, Vitaly Andrianov <vitalya@ti.com> wrote:
> 
>> Interrupts for GPIOs 16 through 31 are enabled by bit 1 in the
>> "binten" register (offset 8). Previous versions of GPIO only
>> used bit 0, which enables GPIO 0-15 interrupts.
>>
>> Signed-off-by: Reece Pollack <x0183204@ti.com>
>> Signed-off-by: Vitaly Andrianov <vitalya@ti.com>
> 
> Sekhar/Kevin: OK with this? We don't have a maintainer
> listed for davinci GPIO so I assume it's you guys...

Hi Linus, I had reviewed this patch and there was a v2 send based on my
comments on July 03.

> Should this be tagged for stable?

Not sure about that. It affects Keystone devices. Vitaly?

Thanks,
Sekhar

  reply	other threads:[~2015-07-16  9:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 17:10 [PATCH] gpio/davinci: add interrupt support for GPIOs 16-31 Vitaly Andrianov
2015-06-18 17:10 ` Vitaly Andrianov
2015-07-14 14:01 ` Linus Walleij
2015-07-16  9:04   ` Sekhar Nori [this message]
2015-07-16 17:41     ` Vitaly Andrianov
2015-07-17  5:02       ` Sekhar Nori
2015-07-17 12:18         ` Vitaly Andrianov

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=55A77392.30400@ti.com \
    --to=nsekhar@ti.com \
    --cc=gnurou@gmail.com \
    --cc=khilman@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vitalya@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 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.