What causes a STOP in the trigger?

What causes a STOP in the trigger?

[Rob]

[-- Attachment #1.1: Type: text/plain, Size: 784 bytes --]

I'm seeing a weird issue where ALSA doesn't ever hit the pointer function,
and we go straight from START to STOP. Debugging the DMA, we get IRQs, I
call the period_elapsed.

It looks like we hit STOP before we even get the first IRQ. I've checked my
parentheses, and theres no overrun or underrun messages. I don't hit the
close function, nor any other functions until i control-C. Once I do that,
I get a large series of pointer() printks showing multiples of IRQ
positions, as if it queued up the commands...

I thought I was IRQing too fast maybe, but as mentioned above, the
irqreturn function doesn't even get called before we STOP.

What in aplay would instantly force a STOP?

Audio plays a few frames (I can hear a chord), then stalls and repeats
until i Ctrl-C.

Thanks,
Rob

[-- Attachment #1.2: Type: text/html, Size: 994 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



[-- Attachment #3: Type: text/plain, Size: 158 bytes --]

_______________________________________________
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Re: What causes a STOP in the trigger?

[Clemens Ladisch]

Rob wrote:
> I'm seeing a weird issue where ALSA doesn't ever hit the pointer function,
> and we go straight from START to STOP. Debugging the DMA, we get IRQs, I
> call the period_elapsed.

The pointer is called from that.

Sounds like a bug somewhere.


Regards,
Clemens