On 2021-05-13 3:59 PM, Takashi Sakamoto wrote:
On Thu, May 13, 2021 at 03:37:02PM +0200, Amadeusz Sławiński wrote:
On 5/13/2021 3:25 PM, Takashi Sakamoto wrote:
Hi,
On Thu, May 13, 2021 at 01:34:25PM +0200, Amadeusz Sławiński wrote:
I was checking some stuff relater to NO_PERIOD_WAKEUP and noticed that axfer
has support for using either --sched-model=irq or --sched-model=timer.
However from few quick tests it seems like it doesn't work?
...
It's a regression added by a commit e5e6a7838b06 ("axfer: return ETIMEDOUT
when no event occurs after waiter expiration"), and the -ETIMEDOUT come
neither from ALSA PCM core nor alsa-lib. Thanks for your reporting!
* https://github.com/alsa-project/alsa-utils/commit/e5e6a7838b06
As a quick fix, please revert the commit. I'll post better fixes later.
After the revert, it looks work well under my hardware:
Yes, I can confirm, that it fixes the problem. Thanks for quick workaround!
That's good. I just filed the better fix. Please apply it with your local
repository instead of the revert patch.
* alsa-utils: axfer: fix regression of timeout in timer-based scheduling model #88
* https://github.com/alsa-project/alsa-utils/pull/88
Anyway, thank you for reporting the bug. In recent years I've been
working for devices in which no-period-wakeup is unavailable, so I
overlooked the bug so long...
No problem Takashi, happens to us all. We thank you for a very quick
reply and solving the issue.
Regards,
Czarek
