On Wed, Feb 04, 2015 at 02:16:03PM +0800, Qiao Zhou wrote:
> Some dma channels may be reserved for other purpose in other layer,
> like secure driver in EL2/EL3. PDMA driver can see the interrupt
> status, but it should not try to handle related interrupt, since it
> doesn't belong to PDMA driver
On Wed, Feb 04, 2015 at 02:16:03PM +0800, Qiao Zhou wrote:
Some dma channels may be reserved for other purpose in other layer,
like secure driver in EL2/EL3. PDMA driver can see the interrupt
status, but it should not try to handle related interrupt, since it
doesn't belong to PDMA driver in
On 4 February 2015 at 14:16, Qiao Zhou wrote:
> Some dma channels may be reserved for other purpose in other layer,
> like secure driver in EL2/EL3. PDMA driver can see the interrupt
> status, but it should not try to handle related interrupt, since it
> doesn't belong to PDMA driver in kernel.
On 4 February 2015 at 14:16, Qiao Zhou zhouq...@marvell.com wrote:
Some dma channels may be reserved for other purpose in other layer,
like secure driver in EL2/EL3. PDMA driver can see the interrupt
status, but it should not try to handle related interrupt, since it
doesn't belong to PDMA
Some dma channels may be reserved for other purpose in other layer,
like secure driver in EL2/EL3. PDMA driver can see the interrupt
status, but it should not try to handle related interrupt, since it
doesn't belong to PDMA driver in kernel. These interrupts should be
handled by corresponding
Some dma channels may be reserved for other purpose in other layer,
like secure driver in EL2/EL3. PDMA driver can see the interrupt
status, but it should not try to handle related interrupt, since it
doesn't belong to PDMA driver in kernel. These interrupts should be
handled by corresponding
6 matches
Mail list logo