From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>
Subject: Re: gpio: mvebu: switch to regmap for register access
Date: Fri, 09 Jun 2017 12:04:39 +0200 [thread overview]
Message-ID: <874lvppjd4.fsf@free-electrons.com> (raw)
In-Reply-To: <e36744644a6c4b2a9a0c73c5f4a9d1b3@svr-chch-ex1.atlnz.lc> (Chris Packham's message of "Fri, 9 Jun 2017 04:09:38 +0000")
Hi Chris,
On ven., juin 09 2017, Chris Packham <Chris.Packham@alliedtelesis.co.nz> wrote:
> On 09/06/17 15:36, Chris Packham wrote:
>> Hi Thomas,
>>
>> Doing some more testing against linux-next and I've found that this
>> patch causes a flood of bad interrupts on my armada-xp-98dx3236 based
>> board (kernel startup output below). If I revert this patch I can boot
>> as normal.
>>
>> This doesn't happen on the 98dx3236 DB or another Armada-385 based board
>> I have so it's probably related something specific to this board
>> (probably one of the i2c gpios based on the log messages).
>>
>> Any thoughts on where I should start looking?
>
> Sure enough I think the problem is related to a pca9555 connected to one
> of the CPU gpios.
>
> gpio@27 {
> #address-cells = <2>;
> #size-cells = <0>;
> compatible = "nxp,pca9555";
> reg = <0x27>;
> gpio-controller;
> #gpio-cells = <2>;
> interrupt-parent = <&gpio0>;
> interrupts = <10 IRQ_TYPE_LEVEL_LOW>;
> };
>
> If I remove the interrupt properties I don't see the problem.
I found the bug and I've just sent a fix for it.
Thanks for the report,
Gregory
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2017-06-09 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 3:36 gpio: mvebu: switch to regmap for register access Chris Packham
2017-06-09 4:09 ` Chris Packham
2017-06-09 10:04 ` Gregory CLEMENT [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=874lvppjd4.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.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.