From: Scott Wood <scottwood@freescale.com>
To: Ron Madrid <ron_madrid@sbcglobal.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Using DMA interrupt on MPC8313
Date: Mon, 16 Jun 2008 12:32:58 -0500 [thread overview]
Message-ID: <4856A3CA.4010905@freescale.com> (raw)
In-Reply-To: <101441.49932.qm@web83508.mail.sp1.yahoo.com>
Ron Madrid wrote:
> Here's my code. There are a few other things that happen but they are inconsequential to this
> problem. I'm sure that the request_irq call is right, especially since it works if the fsldma
> drivers are builtin to the kernel. Also, the irq number 71 comes from the reference manual for
> them MPC8313. It is the internal interrupt for the DMA. I'll do some more testing in a little
> while to try to determine the cause of the error in request_irq.
You cannot pass hardware IRQ numbers directly to request_irq() -- it has
no idea which IRQ controller you're referring to (even if there happens
to be only one on your board).
You should get the IRQ from the device tree, using
irq_of_parse_and_map() on the device node for the DMA channel (see the
mpc8377mds device tree for an example DMA node).
-Scott
next prev parent reply other threads:[~2008-06-16 17:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 19:35 Using DMA interrupt on MPC8313 Ron Madrid
2008-06-12 19:47 ` Kumar Gala
2008-06-12 20:04 ` Ron Madrid
2008-06-12 23:01 ` Kumar Gala
2008-06-13 19:02 ` Ron Madrid
2008-06-13 23:33 ` Kumar Gala
2008-06-13 23:52 ` Ron Madrid
2008-06-13 23:54 ` Timur Tabi
2008-06-14 0:19 ` Ron Madrid
2008-06-16 14:11 ` Timur Tabi
2008-06-16 14:44 ` Kumar Gala
2008-06-16 17:13 ` Ron Madrid
2008-06-16 17:32 ` Scott Wood [this message]
2008-06-16 18:07 ` Ron Madrid
2008-06-16 18:11 ` Timur Tabi
2008-06-16 18:40 ` Scott Wood
2008-06-16 19:10 ` Ron Madrid
2008-06-24 5:54 ` jumpingProgrammer
2008-06-24 18:04 ` Scott Wood
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=4856A3CA.4010905@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=ron_madrid@sbcglobal.net \
/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).