[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkda6mm8Ogam2vD6LY4XBwzKdSeh8-e5ieUZWtZXnbSrOhg@mail.gmail.com>
Date: Mon, 7 Aug 2017 14:15:12 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Gregory CLEMENT <gregory.clement@...e-electrons.com>
Cc: "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jason Cooper <jason@...edaemon.net>,
Andrew Lunn <andrew@...n.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Nadav Haklai <nadavh@...vell.com>,
Shadi Ammouri <shadi@...vell.com>,
Yehuda Yitschak <yehuday@...vell.com>,
Omri Itach <omrii@...vell.com>,
Hanna Hawa <hannah@...vell.com>,
Igal Liberman <igall@...vell.com>,
Marcin Wojtas <mw@...ihalf.com>
Subject: Re: [PATCH] gpio: mvebu: Fix cause computation in irq handler
On Wed, Jul 12, 2017 at 1:22 PM, Gregory CLEMENT
<gregory.clement@...e-electrons.com> wrote:
> When switching to regmap, the way to compute the irq cause was
> reorganized. However while doing it, a typo was introduced: a 'xor'
> replaced a 'and'.
>
> This lead to wrong behavior in the interrupt handler ans one of the
> symptom was wrong irq handler called on the Armada 388 GP:
> "->handle_irq(): c016303c,
> handle_bad_irq+0x0/0x278
> ->irq_data.chip(): c0b0ec0c,
> 0xc0b0ec0c
> ->action(): (null)
> IRQ_NOPROBE set
> IRQ_NOREQUEST set
> unexpected IRQ trap at vector 00
> irq 0, desc: ee804800, depth: 1, count: 0, unhandled: 0"
>
> Fixes: 2233bf7a92e7 ("gpio: mvebu: switch to regmap for register access")
> Signed-off-by: Gregory CLEMENT <gregory.clement@...e-electrons.com>
Patch applied for fixes.
Yours,
Linus Walleij
Powered by blists - more mailing lists