All of lore.kernel.org
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: ux500: Change IRQ from low-to-high edge triggered to high-to-low
Date: Tue, 4 Dec 2012 09:12:15 +0000	[thread overview]
Message-ID: <20121204091215.GD2718@gmail.com> (raw)
In-Reply-To: <CACRpkdafvpnyq7YMV=iSjN4+u1hpt3xntAb-daJZifG9VpgnOw@mail.gmail.com>

On Sat, 01 Dec 2012, Linus Walleij wrote:

> On Fri, Nov 30, 2012 at 4:24 PM, Lee Jones <lee.jones@linaro.org> wrote:
> 
> > When the STMPE IRQ is triggered to be active high level-sensitive, the
> > Nomadik GPIO controller it uses complains, although it still works.
> > Recently we attempted to move triggering to low-to-high in an attempt
> > to prevent the warning; however, this ensured that the IRQ was actually
> > missed completely. Now we have a solution which both works and keeps the
> > GPIO controller happy.
> >
> > Signed-off-by: Lee Jones <lee.jones@linaro.org>
> 
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
> 
> Is this something I should put into the ux500 tree or will you
> take care of this in a separate pull request?

Can you still get this into the RCs, as it's a bugfix?

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, arnd@arndb.de,
	linus.walleij@stericsson.com
Subject: Re: [PATCH 1/1] ARM: ux500: Change IRQ from low-to-high edge triggered to high-to-low
Date: Tue, 4 Dec 2012 09:12:15 +0000	[thread overview]
Message-ID: <20121204091215.GD2718@gmail.com> (raw)
In-Reply-To: <CACRpkdafvpnyq7YMV=iSjN4+u1hpt3xntAb-daJZifG9VpgnOw@mail.gmail.com>

On Sat, 01 Dec 2012, Linus Walleij wrote:

> On Fri, Nov 30, 2012 at 4:24 PM, Lee Jones <lee.jones@linaro.org> wrote:
> 
> > When the STMPE IRQ is triggered to be active high level-sensitive, the
> > Nomadik GPIO controller it uses complains, although it still works.
> > Recently we attempted to move triggering to low-to-high in an attempt
> > to prevent the warning; however, this ensured that the IRQ was actually
> > missed completely. Now we have a solution which both works and keeps the
> > GPIO controller happy.
> >
> > Signed-off-by: Lee Jones <lee.jones@linaro.org>
> 
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
> 
> Is this something I should put into the ux500 tree or will you
> take care of this in a separate pull request?

Can you still get this into the RCs, as it's a bugfix?

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2012-12-04  9:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30 15:24 [PATCH 1/1] ARM: ux500: Change IRQ from low-to-high edge triggered to high-to-low Lee Jones
2012-11-30 15:24 ` Lee Jones
2012-12-01 16:51 ` Linus Walleij
2012-12-01 16:51   ` Linus Walleij
2012-12-04  9:12   ` Lee Jones [this message]
2012-12-04  9:12     ` Lee Jones
2012-12-04 12:31     ` Linus Walleij
2012-12-04 12:31       ` Linus Walleij
2012-12-04 13:58       ` Lee Jones
2012-12-04 13:58         ` Lee Jones

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=20121204091215.GD2718@gmail.com \
    --to=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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 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.