From: Andrew Lunn <andrew@lunn.ch>
To: raghu MG <raghumag@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
sebastian.hesselbarth@gmail.com
Subject: Re: Armadaxp GPIO interrupts
Date: Tue, 4 Aug 2015 17:34:39 +0200 [thread overview]
Message-ID: <20150804153439.GA28673@lunn.ch> (raw)
In-Reply-To: <CAG1O52Xg88OsifBzmpSdqvC8wQaOW78nC9nnfxugFv1VU1m1LQ@mail.gmail.com>
On Tue, Aug 04, 2015 at 08:52:17PM +0530, raghu MG wrote:
> Hello,
>
> I am working on a card which as GPIOs connected to external I/O's. The
> board consists of ARMADAXP 78460 host cpu.
>
> Board currently runs Linux-4.1 with modified armada-xp-gp.dtb for ArmadaXP.
> I enabled "orion-gpio" driver to initialize GPIOs as given in
> armada-xp-mv78460.
What kernel configuration are you using? Do you have the same problem
with multi_v7_defconfig and mvebu_v7_defconfig?
> The driver while initializing calls irq_domain_add_simple which throws up
> following warning
> "irq: Cannot allocate irq_descs @ IRQ47, assuming pre-allocated"
> The warning repeats for next set(32-63 & 64-66).
>
> Also the GPIO IRQs are not getting listed in cat /proc/interrupts
irq_domain_add_simple() returning an error is fatal for the probe. The
driver will not be loaded, so more than interrupts will be missing,
all the gpios will be missing.
Andrew
next parent reply other threads:[~2015-08-04 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAG1O52Xg88OsifBzmpSdqvC8wQaOW78nC9nnfxugFv1VU1m1LQ@mail.gmail.com>
2015-08-04 15:34 ` Andrew Lunn [this message]
2015-08-05 5:07 ` Armadaxp GPIO interrupts raghu MG
[not found] ` <CAG1O52VQPpeGkA8bqYbPMTiT9Mua1yHi3H3osqJsHqm-RRKzow@mail.gmail.com>
2015-08-05 16:21 ` Andrew Lunn
2015-08-06 5:54 ` raghu MG
2015-08-06 13:29 ` Andrew Lunn
2015-08-06 16:58 ` raghu MG
2015-08-06 17:13 ` Andrew Lunn
2015-08-06 18:18 ` raghu MG
2015-08-07 20:54 ` raghu MG
2015-08-07 22:10 ` Andrew Lunn
2015-08-05 15:02 ` raghu MG
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=20150804153439.GA28673@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raghumag@gmail.com \
--cc=sebastian.hesselbarth@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox