linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Alemao <xcarandiru@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: MPC85xx External/Internal Interrupts
Date: Fri, 4 Sep 2009 16:01:05 -0300	[thread overview]
Message-ID: <d970ff420909041201m343dafdfta0e55df8b5c01f60@mail.gmail.com> (raw)
In-Reply-To: <d970ff420909040604h1bb3874eg5c79f79f85e713a3@mail.gmail.com>

Hi all,

In all MPC85xx DTS files I have seen this interrupt configuration for
TSEC1:

interrupts = <29 2 30 2 34 2>;

29 - TSEC1 interrupt transmit
30 - TSEC1 interrupt receive
34 - TSEC1 interrupt error


But in MPC8555RM, chapter 10.1.5.2 the numbers are these:

13 - TSEC1 interrupt transmit
14 - TSEC1 interrupt receive
18 - TSEC1 interrupt error


Im a little bit confused about this internal interrupts, how can I get
this numbers? TSEC1 is working normally.


My real problem is that my driver is trying to request the external
interrupt IRQ0, and I dont know what number use in INTR_NUM:

request_irq(INTR_NUM, , , , )


Im using linux-2.6.26

Cheers,

--
Alemao

  parent reply	other threads:[~2009-09-04 19:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d970ff420909040604h1bb3874eg5c79f79f85e713a3@mail.gmail.com>
2009-09-04 13:13 ` Fwd: MPC85xx External/Internal Interrupts Alemao
2009-09-04 19:01 ` Alemao [this message]
2009-09-04 19:14   ` Alemao
2009-09-04 19:24     ` Alemao
     [not found] ` <d970ff420909041228h3638e840r34c0c0e79f178e55@mail.gmail.com>
     [not found]   ` <d970ff420909041229hb3aa96dya329e06ea56dd1ac@mail.gmail.com>
2009-09-06 11:06     ` Sebastian Andrzej Siewior
2009-09-09 18:28       ` Scott Wood
2009-09-10 13:15         ` Sebastian Andrzej Siewior
2009-09-10 22:24           ` Sebastian Andrzej Siewior
2009-09-10 22:27             ` Scott Wood
2009-12-06 11:32               ` [RFC] doc/powerpc: try to explain why the interrupt numbers are off by 16 Sebastian Andrzej Siewior
2009-12-09 20:51                 ` Kumar Gala

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=d970ff420909041201m343dafdfta0e55df8b5c01f60@mail.gmail.com \
    --to=xcarandiru@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;
as well as URLs for NNTP newsgroup(s).