linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP: irqs: Fix NR_IRQS value to handle PRCM interrupts
Date: Tue, 28 Feb 2012 15:55:28 -0800	[thread overview]
Message-ID: <20120228235528.GI18901@atomide.com> (raw)
In-Reply-To: <4F4CD231.4030709@ti.com>

* Cousson, Benoit <b-cousson@ti.com> [120228 04:38]:
> The following commit: 2f31b51659c2d8315ea2888ba5b93076febe672b
> Author: Tero Kristo <t-kristo@ti.com>
> Date:   Fri Dec 16 14:37:00 2011 -0700
> 
>     ARM: OMAP4: PRM: use PRCM interrupt handler
> 
> introduced the PRCM interrupt handler and thus the need
> for 64 more interrupts. Since SPARSE_IRQ is still not fully
> functional on OMAP, the NR_IRQS needs to be updated to avoid
> the failure that happen during irq_alloc_descs call inside
> the PRCM driver:
> 
> [    0.208221] PRCM: failed to allocate irq descs: -12
> 
> Later the mux framework is then unable to request an IRQ from
> the PRCM interrupt handler.
> 
> [    1.802795] mux: Failed to setup hwmod io irq -22
> 
> Fix that by adding 64 more interrupts for OMAP2PLUS config.
> 
> Signed-off-by: Benoit Cousson <b-cousson@ti.com>
> Cc: Tero Kristo <t-kristo@ti.com>
> ---
> Tony,
> 
> This patch should probably go for the next -rc if possible.

Thanks applying into fixes as it seems like the only available
fix right now.

Tony

      parent reply	other threads:[~2012-02-28 23:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 13:10 [PATCH] ARM: OMAP: irqs: Fix NR_IRQS value to handle PRCM interrupts Cousson, Benoit
2012-02-28 14:36 ` Russell King - ARM Linux
2012-02-28 20:32   ` Cousson, Benoit
2012-02-28 20:43     ` Russell King - ARM Linux
2012-02-28 23:55 ` Tony Lindgren [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=20120228235528.GI18901@atomide.com \
    --to=tony@atomide.com \
    --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 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).