From: Timur Tabi <timur@freescale.com>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: linuxppc-dev@ozlabs.org, dan.j.williams@intel.com
Subject: Re: [PATCH] fsldma: print correct IRQ on mpc83xx
Date: Wed, 14 Jan 2009 10:42:16 -0600 [thread overview]
Message-ID: <496E15E8.2060106@freescale.com> (raw)
In-Reply-To: <87eiz5c074.fsf@macbook.be.48ers.dk>
Peter Korsgaard wrote:
> Documentation/powerpc/dts-bindings/fsl/dma.txt and
> The NO_IRQ check in fsldma.c:fsl_dma_chan_probe()
>
> And it makes sense, there's no per-channel DMAC interrupts on mpc83xx.
But the device trees do have IRQs in the channels:
arch/powerpc/boot/dts/mpc836x_mds.dts:
dma@82a8 {
...
interrupt-parent = <&ipic>;
interrupts = <71 8>;
dma-channel@0 {
compatible = "fsl,mpc8360-dma-channel", "fsl,elo-dma-channel";
reg = <0 0x80>;
cell-index = <0>;
interrupt-parent = <&ipic>;
interrupts = <71 8>;
};
...
So I don't see what bug you're trying to fix. If you're saying that the
interrupts should not be specific DMA channels, then the proper fix is to have
the DMA driver pick up the interrupts from the DMA controller's node when
necessary. Hacking up a printk doesn't fix anything.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2009-01-14 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 14:44 [PATCH] fsldma: print correct IRQ on mpc83xx Peter Korsgaard
2009-01-14 16:10 ` Timur Tabi
2009-01-14 16:15 ` Peter Korsgaard
2009-01-14 16:30 ` Timur Tabi
2009-01-14 16:38 ` Peter Korsgaard
2009-01-14 16:42 ` Timur Tabi [this message]
2009-01-14 19:29 ` Peter Korsgaard
2009-01-14 19:30 ` Timur Tabi
2009-01-15 6:17 ` Dan Williams
2009-01-15 11:21 ` Li Yang
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=496E15E8.2060106@freescale.com \
--to=timur@freescale.com \
--cc=dan.j.williams@intel.com \
--cc=jacmet@sunsite.dk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.