From: Clemens Ladisch <clemens@ladisch.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: "Dominic Sacré" <dominic.sacre@gmx.de>,
alsa-devel@alsa-project.org,
"Takashi Sakamoto" <o-takashi@sakamocchi.jp>
Subject: Re: snd-fireworks requires larger period sizes than FFADO
Date: Tue, 1 Dec 2015 18:15:46 +0100 [thread overview]
Message-ID: <565DD5C2.5040804@ladisch.de> (raw)
In-Reply-To: <20151201153111.4f7a0e1f@kant>
Stefan Richter wrote:
> is there a strict requirement that the ALSA period is more than double of
> the FireWire interrupt period?
No. But the ALSA API promises that interrupts arrive at the end of
a period (which always has a constant size), and with the FireWire packet
sizes varying, this is the easiest way of ensuring that interrupts are
delayed by less than half the period size.
The driver should dynamically reduce the interrupt interval for smaller
periods.
> Also, I believe to remember that you once said that instead of relying on
> periodical interrupts from the OHCI, it might be better to switch to a
> kind of polling scheme (i.e. process the IEEE 1394 packet buffer on an
> own period = ALSA period?).
This is already implemented by calling fw_iso_context_flush_completions().
It helps with PulseAudio (which predicts the correct time to poll), but is
useless when the application relies on the interrupt to wake it up (e.g.,
Jack).
Regards,
Clemens
next prev parent reply other threads:[~2015-12-01 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 0:20 snd-fireworks requires larger period sizes than FFADO Dominic Sacré
2015-11-23 10:40 ` Clemens Ladisch
2015-12-01 14:31 ` Stefan Richter
2015-12-01 17:15 ` Clemens Ladisch [this message]
2015-12-02 0:31 ` Takashi Sakamoto
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=565DD5C2.5040804@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=dominic.sacre@gmx.de \
--cc=o-takashi@sakamocchi.jp \
--cc=stefanr@s5r6.in-berlin.de \
/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.