LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Johns Daniel <johns.daniel@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: PCIe interrupts in the device tree
Date: Tue, 24 Mar 2009 15:24:50 -0500	[thread overview]
Message-ID: <ba5d9360903241324n57aa74caq2dd2bcdd2a885e19@mail.gmail.com> (raw)

Could somebody please explain the declaration of the PCIe interrupts
in the device tree?

I was under the impression that PCIe interrupts in the PowerPC Linux
kernel default to using INTx signaling (vs. external IRQ pin assertion
and MSI signaling). Am I right?

If so, then do the interrupt-map lines in the DTS refer to the
internal IRQ used by Freescale processors to implement INTx virtual
wire interrupts?

For example, in the mpc8536ds.dts file, under "pci1: pcie@ffe09000" we have:
		interrupt-map = <
			/* IDSEL 0x0 */
			0000 0 0 1 &mpic 4 1
			0000 0 0 2 &mpic 5 1
			0000 0 0 3 &mpic 6 1
			0000 0 0 4 &mpic 7 1
			>;
Are the 4, 5, 6, and 7 internal or external IRQs?

And the "msi@41600" section in the same mpc8536ds.dts file does NOT
affect PCIe interrupts unless a driver calls pci_enable_msi()?

TIA!

-- Johns

             reply	other threads:[~2009-03-24 20:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 20:24 Johns Daniel [this message]
2009-03-24 20:54 ` PCIe interrupts in the device tree Kumar Gala
2009-03-24 21:13   ` Johns Daniel
2009-03-25  1:12     ` Kumar Gala
2009-03-25 13:45       ` Johns Daniel

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=ba5d9360903241324n57aa74caq2dd2bcdd2a885e19@mail.gmail.com \
    --to=johns.daniel@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox