Using DMA interrupt on MPC8313
Kumar Gala
galak at kernel.crashing.org
Tue Jun 17 00:44:43 EST 2008
What does your code actually look like. In your driver how are you
getting the IRQ value that you pass to request_irq?
- k
On Jun 13, 2008, at 6:52 PM, Ron Madrid wrote:
> I don't know why request_irq is succeeding when the fsldma and
> dmaengine drivers are installed.
> I'm using the same dts in both cases.
>
> Ron
> --- Kumar Gala <galak at kernel.crashing.org> wrote:
>
>> That's a bit odd. How is your driver getting the IRQ its requesting?
>> Are you using the same .dts in both cases?
>>
>> - k
>>
>> On Jun 13, 2008, at 2:02 PM, Ron Madrid wrote:
>>
>>> So after I've built the kernel to include the dmaengine and fsldma
>>> drivers, my driver is allowed
>>> to register its ISR via request_irq. However, if these drivers are
>>> not installed then request_irq
>>> fails in my driver. So it seems that there is some other
>>> initialization happening before
>>> request_irq is being called in fsldma and subsequently my driver.
>>> Does anyone know what this is?
>>>
>>> Ron
>>> --- Kumar Gala <galak at kernel.crashing.org> wrote:
>>>
>>>> The dmaengine provides a generic set of APIs w/a FSL dma
>>>> backend. It
>>>> might be the case that your need of dma doesnt fit into the current
>>>> set of APIs.
>>>>
>>>> - k
>>>>
>>>> On Jun 12, 2008, at 3:04 PM, Ron Madrid wrote:
>>>>
>>>>> Well in that case wouldn't I need to use the fsldma driver? Or is
>>>>> dmaengine a generic dma driver?
>>>>>
>>>>> Ron
>>>>> --- Kumar Gala <galak at kernel.crashing.org> wrote:
>>>>>
>>>>>>
>>>>>> On Jun 12, 2008, at 2:35 PM, Ron Madrid wrote:
>>>>>>
>>>>>>> I'm trying to write a driver that would make use of the DMA on
>>>>>>> the
>>>>>>> MPC8313. I'm attempting to
>>>>>>> register the interrupt with request_irq but it is not
>>>>>>> passing. Is
>>>>>>> there something that I need to
>>>>>>> do before I call request_irq, maybe in the dts or somewhere
>>>>>>> else?
>>>>>>
>>>>>>
>>>>>> any reason you aren't using the dmaengine driver?
>>>>>>
>>>>>> - k
>>>>>>
>>>>
>>>>
>>
>>
More information about the Linuxppc-dev
mailing list