From: Takashi Iwai <tiwai@suse.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org, clemens@ladisch.de
Subject: Re: [PATCH 0/3] ALSA: firewire-motu: media clock recovery for sph-aware devices
Date: Wed, 02 Jun 2021 09:00:18 +0200 [thread overview]
Message-ID: <s5heedkycn1.wl-tiwai@suse.de> (raw)
In-Reply-To: <20210602013406.26442-1-o-takashi@sakamocchi.jp>
On Wed, 02 Jun 2021 03:34:03 +0200,
Takashi Sakamoto wrote:
>
> Hi,
>
> In a commit f9e5ecdfc2c2 ("ALSA: firewire-lib: add replay target to cache
> sequence of packet"), I categorize devices supported by drivers in ALSA
> firewire stack in terms of the way to deliver effective sampling
> transfer frequency. This patchset is for the devices in group 3.
>
> The devices are known to have problems when ALSA firewire-motu driver
> handles. Many of them generate sound with noise. In the worst case, it
> generates no sound.
>
> The devices interpret presentation time to decide playback timing.
> Unlike the syt-aware devices, the devices interpret the presentation
> time in source packet header (SPH) per data block, instead of the
> presentation time in syt field of CIP header.
>
> Current implementation of the driver processes the sequence of outgoing
> packet by computation according to nominal sampling transfer frequency.
> However, the ideal sequence is not adequate to the devices, actually.
>
> With this patchset, the drivers are going to replay the sequence of
> incoming packets for media clock recovery, instead of nominal sampling
> transfer frequency. For the detail of sequence replay, please refer to a
> commit 39c2649c71d8 ("ALSA: firewire-lib: replay sequence of incoming
> packets for outgoing packets"). The sequence replay is done by two levels;
> the sequence of the number of data blocks per packet, and the sequence of
> SPH per data blocks in the packet.
>
> Takashi Sakamoto (3):
> ALSA: firewire-motu: use macro for magic numbers relevant to IEC
> 61883-1
> ALSA: firewire-motu: cache event ticks in source packet header per
> data block
> ALSA: firewire-motu: sequence replay for source packet header
Applied all three patches now. Thanks.
Takashi
prev parent reply other threads:[~2021-06-02 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 1:34 [PATCH 0/3] ALSA: firewire-motu: media clock recovery for sph-aware devices Takashi Sakamoto
2021-06-02 1:34 ` [PATCH 1/3] ALSA: firewire-motu: use macro for magic numbers relevant to IEC 61883-1 Takashi Sakamoto
2021-06-02 1:34 ` [PATCH 2/3] ALSA: firewire-motu: cache event ticks in source packet header per data block Takashi Sakamoto
2021-06-02 1:34 ` [PATCH 3/3] ALSA: firewire-motu: sequence replay for source packet header Takashi Sakamoto
2021-06-02 7:00 ` Takashi Iwai [this message]
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=s5heedkycn1.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=o-takashi@sakamocchi.jp \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).