All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: John Bonesio <bones@secretlab.ca>,
	linuxppc-dev@ozlabs.org, Anatolij Gustschin <agust@denx.de>
Subject: Re: [PATCH] powerpc: dts: 52xx: drop critical IRQ from dts files
Date: Fri, 24 Aug 2012 10:44:25 +0200	[thread overview]
Message-ID: <20120824084425.GA12630@pengutronix.de> (raw)
In-Reply-To: <CACxGe6si6a6=9511e0W_YDsQTUr98KOkqTpzYJryakcAAqQvew@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]

On Thu, Aug 23, 2012 at 04:59:26PM +0100, Grant Likely wrote:
> On Thu, Aug 23, 2012 at 4:31 PM, Wolfram Sang <w.sang@pengutronix.de> wrote:
> > The wakeup-gpios have been assigned a critical IRQ in current
> > devicetrees. The PIC driver does not support critical IRQs, though, which
> > leads to the following error when booting (a PCM030 in this case):
> >
> >         mpc52xx_irqhost_map: invalid irq: virq=16, l1=0, l2=3
> >         irq: irq-16==>hwirq-0x3 mapping failed: -22
> >         [WARNing skipped]
> >
> > Remove these entries until they are supported, if ever.
> 
> The warning is a bug since the irq specifier is valid. Removing the
> irqs from the .dts files isn't the solution.

Adding another warning (not error) that critical IRQ are not supported
is?

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2012-08-24  8:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-23 15:31 [PATCH] powerpc: dts: 52xx: drop critical IRQ from dts files Wolfram Sang
2012-08-23 15:59 ` Grant Likely
2012-08-24  8:44   ` Wolfram Sang [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=20120824084425.GA12630@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=agust@denx.de \
    --cc=bones@secretlab.ca \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.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 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.