linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: bterrell <bterrell@empirix.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: MPC8572 - IPR Register
Date: Tue, 16 Dec 2008 14:08:55 -0800 (PST)	[thread overview]
Message-ID: <21042870.post@talk.nabble.com> (raw)
In-Reply-To: <A7BF6E08-786A-4D00-BBEA-1568939722E9@kernel.crashing.org>



Kumar Gala-3 wrote:
> 
> 
> <1. Which PCIe port is the device on?
> 2. is this a INT-X style or MSI interrupt?
> 3. if INT-X is INT-A, B, C, D?
> 
> - k
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
> 
> 

He was posting a question for me.  The external device (PLX8616
non-transparent bridge) which is sending the interrupt is connected to the
first PCIE controller.  The PCIE controller is configured in RC mode and is
"x4".  I'm using legacy (INTx) interrupts from the external switch NTB port. 
The NTB port always generates INTA, but is swizzled by the upstream port of
the PLX8616 switch, so it comes to the PCIE controller as INTB I believe.

It works fine when the the 8572 and 8616 both start after power-on reset. 
Can send multiple interrupts and each is acknowledged properly.  However,
after I generate a "hot reset" event from the PCIE controller to the
upstream port on the 8616 (or link goes down/up), it no longer seems to
propagate the INTx interrupt to the CPU.  Either the 8616 is not sending the
interrrupt or the 8572 is ignoring/masking it.  I'm trying to determine
which device is at fault.  I don't have access to a PCIE analyzer at the
moment.  Looking for some more visibility into received interrupts within
the 8572 PCIE or MPIC.  

FYI, I have not tried MSI yet but will soon.

thanks,
Bill
-- 
View this message in context: http://www.nabble.com/MPC8572---IPR-Register-tp21040440p21042870.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.

  reply	other threads:[~2008-12-16 22:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2123.1229452170.29923.linuxppc-dev@ozlabs.org>
2008-12-16 19:54 ` MPC8572 - IPR Register Morrison, Tom
2008-12-16 21:34   ` Kumar Gala
2008-12-16 22:08     ` bterrell [this message]
2008-12-16 23:00       ` Kumar Gala
2008-12-17 18:41         ` bterrell

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=21042870.post@talk.nabble.com \
    --to=bterrell@empirix.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;
as well as URLs for NNTP newsgroup(s).