From: Tony Lindgren <tony@atomide.com>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [GIT PULL] ARM: OMAP: IRQ domain support for INTC
Date: Wed, 29 Feb 2012 13:42:55 -0800 [thread overview]
Message-ID: <20120229214255.GR18901@atomide.com> (raw)
In-Reply-To: <4F4E4F1D.7020109@ti.com>
* Cousson, Benoit <b-cousson@ti.com> [120229 07:43]:
> On 2/29/2012 12:48 AM, Tony Lindgren wrote:
> >
> > Hmm, looks like this now produces the following warning at least on omap3:
>
> Yes, Rajendra has just reported that issue with linux-next.
>
> It is not due to that series but to the increase of TWL irq_desc I did for Grant to fix a warning with irq_domain in the DT boot.
> Unfortunately due the lack of NR_IRQS we already have becasue of PRCM handler we exceed the actual NR_IRQS that is set to 410 for the moment.
>
> > [ 0.290832] WARNING: at drivers/mfd/twl4030-irq.c:645 twl4030_sih_setup+0x258/0x298()
> > [ 0.290832] irq 428 for gpio too big
OK. I've pulled this into dt-part2 branch.
> After applying the NR_IRQS fix, we still have a warning but a different one in that case:
>
> [ 0.303771] twl4030: PIH (irq 7) chaining IRQs 368..401
> [ 0.304473] twl4030: power (irq 373) chaining IRQs 402..409
> [ 0.307159] twl4030: gpio (irq 368) chaining IRQs 410..427
> [ 0.307189] ------------[ cut here ]------------
> [ 0.307220] WARNING: at drivers/gpio/gpio-twl4030.c:410 gpio_twl4030_probe+0x44/0x214()
>
> This one is due to a "WARN_ON(ret != pdata->irq_base)" that is checking that the board irq_base is the same as the one from the twl4030_sih_setup. This kind of test are not SPARSE_IRQ friendly at all and should be removed anyway. I've attached a patch to fix the GPIO warning.
OK, maybe post that separately so Samuel can queue it?
> Felipe has started a twl4030 IRQ cleanup series to make that driver SPARSE_IRQ enabled. That's will fix properly the actual hack in the twl-core IRQ management. On top of that we can fix the twl-gpio warning.
Great, good to hear.
Regards,
Tony
next prev parent reply other threads:[~2012-02-29 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 16:36 [GIT PULL] ARM: OMAP: IRQ domain support for INTC Cousson, Benoit
2012-02-28 23:48 ` Tony Lindgren
2012-02-29 16:15 ` Cousson, Benoit
2012-02-29 21:42 ` Tony Lindgren [this message]
2012-03-05 13:58 ` Johan Hovold
2012-03-05 14:25 ` Cousson, Benoit
2012-03-05 15:03 ` Johan Hovold
2012-03-05 15:19 ` Cousson, Benoit
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=20120229214255.GR18901@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).