From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: clemens@ladisch.de, tiwai@suse.de
Cc: alsa-devel@alsa-project.org,
linux1394-devel@lists.sourceforge.net, ffado-devel@lists.sf.net
Subject: [PATCH 0/4] firewire-lib: purge restriction of synchronization for non-blocking mode
Date: Sat, 16 May 2015 20:22:41 +0900 [thread overview]
Message-ID: <1431775365-25211-1-git-send-email-o-takashi@sakamocchi.jp> (raw)
This patchset allows non-blocking streams to use timestamp synchronization.
In full duplex synchronization mode, current implementation pass the value
of 'syt' field of CIP header in incoming packets to outgoing packet
processing, while the number of data blocks is not passed. Therefore,
this mode is allowed just to blocking streams, because of a lack of
validator for the number which actual devices transfers. As long as the
number is suspicious, it's not reused to outgoing packet processing.
To allow the synchronization mode to non-blocking streams, this patchset:
* adds a validator for the number of data blocks in incoming packets
* adds a flag still to support illegal models (i.e. Behringer FCA202)
* pass the evaluated number from incoming packet processing to outgoing
* remove the restriction
Takashi Sakamoto (4):
ALSA: firewire-lib: add buffer-over-run protection at receiving more
data blocks than expected
ALSA: firewire-lib: simplify function to calculate the number of data
blocks
ALSA: firewire-lib: pass the number of data blocks in incoming packets
to outgoing packets
ALSA: firewire-lib: remove restriction for non-blocking mode
sound/firewire/amdtp.c | 108 ++++++++++++++++++++++++--------------
sound/firewire/amdtp.h | 4 ++
sound/firewire/oxfw/oxfw-stream.c | 10 +++-
3 files changed, 81 insertions(+), 41 deletions(-)
--
2.1.4
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
next reply other threads:[~2015-05-16 11:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-16 11:22 Takashi Sakamoto [this message]
2015-05-16 11:22 ` [PATCH 1/4] ALSA: firewire-lib: add buffer-over-run protection at receiving more data blocks than expected Takashi Sakamoto
2015-05-16 11:30 ` Behringer FCA 202 packet dump (Re: [PATCH 1/4] ALSA: firewire-lib: add buffer-over-run protection at receiving more data blocks than expected) Takashi Sakamoto
2015-05-18 12:54 ` [PATCH 1/4] ALSA: firewire-lib: add buffer-over-run protection at receiving more data blocks than expected Takashi Iwai
2015-05-19 0:25 ` Takashi Sakamoto
2015-05-19 4:48 ` Takashi Iwai
2015-05-16 11:22 ` [PATCH 2/4] ALSA: firewire-lib: simplify function to calculate the number of data blocks Takashi Sakamoto
2015-05-16 11:22 ` [PATCH 3/4] ALSA: firewire-lib: pass the number of data blocks in incoming packets to outgoing packets Takashi Sakamoto
2015-05-16 11:22 ` [PATCH 4/4] ALSA: firewire-lib: remove restriction for non-blocking mode 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=1431775365-25211-1-git-send-email-o-takashi@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=ffado-devel@lists.sf.net \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=tiwai@suse.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.