From: Segher Boessenkool <segher@kernel.crashing.org>
To: "André Schwarz" <andre.schwarz@matrix-vision.de>
Cc: Scott Wood <scottwood@freescale.com>,
linux-ppc list <linuxppc-dev@ozlabs.org>
Subject: Re: MPC83xx ipic problem
Date: Mon, 30 Jun 2008 18:36:34 +0200 [thread overview]
Message-ID: <7dd3673e01cb808007902b12a63d0399@kernel.crashing.org> (raw)
In-Reply-To: <4868FCE9.1060103@matrix-vision.de>
> interrupt-map = <0x5800 0 0 1 &ipic 0x30 0x8 -> FPGA @ IRQ0
> 0x6000 0 0 1 &ipic 0x11 0x8 -> miniPCI INTA @
> IRQ1
> 0x6000 0 0 2 &ipic 0x11 0x8>; -> miniPCI INTB @
> IRQ1
>
> Is it legal to use a single irq pin twice ?
The device tree simply describes the hardware; if the hardware
connects both INTXs to the same IPIC interrupt pin, then it is
correct. You'll have to ask a hardware designer whether it is
okay to just tie the two lines together; I believe it is, for
PCI, but you better ask someone who really knows :-)
Segher
next prev parent reply other threads:[~2008-06-30 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 15:34 MPC83xx ipic problem André Schwarz
2008-06-30 16:36 ` Segher Boessenkool [this message]
2008-06-30 17:14 ` André Schwarz
2008-06-30 19:03 ` Scott Wood
2008-07-01 7:45 ` André Schwarz
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=7dd3673e01cb808007902b12a63d0399@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=andre.schwarz@matrix-vision.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).