All of lore.kernel.org
 help / color / mirror / Atom feed
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: media clock recovery for syt-aware devices
Date: Tue, 01 Jun 2021 18:37:50 +0200	[thread overview]
Message-ID: <s5hmts9y201.wl-tiwai@suse.de> (raw)
In-Reply-To: <20210601081753.9191-1-o-takashi@sakamocchi.jp>

On Tue, 01 Jun 2021 10:17:50 +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 2.
> 
> The devices are known to have problems when ALSA dice/bebob drivers
> handle. Many of them sometimes transfer packets with discontinued counter,
> corrupt at break of CMP connection, generates bus-reset voluntarily.
> 
> The devices interpret presentation time to decide playback timing. The
> drivers process presentation time expressed in syt field of CIP header for
> outgoing packets. Current implementation of the drivers processes the
> sequence of outgoing packet by computation according to nominal sampling
> transfer frequency, assisted by ALSA IEC 61883-1/6 packet streaming engine.
> 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. For the detail of sequence
> replay, please refer to a commit 39c2649c71d8 ("ALSA: firewire-lib: replay
> sequence of incoming packets for outgoing packets").
> 
> Takashi Sakamoto (3):
>   ALSA: dice: wait just for NOTIFY_CLOCK_ACCEPTED after
>     GLOBAL_CLOCK_SELECT operation
>   ALSA: dice: perform sequence replay for media clock recovery
>   ALSA: bebob: perform sequence replay for media clock recovery

Applied all three patches now.  Thanks.


Takashi

      parent reply	other threads:[~2021-06-01 16:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01  8:17 [PATCH 0/3] ALSA: firewire: media clock recovery for syt-aware devices Takashi Sakamoto
2021-06-01  8:17 ` [PATCH 1/3] ALSA: dice: wait just for NOTIFY_CLOCK_ACCEPTED after GLOBAL_CLOCK_SELECT operation Takashi Sakamoto
2021-06-01  8:17 ` [PATCH 2/3] ALSA: dice: perform sequence replay for media clock recovery Takashi Sakamoto
2021-07-02  4:57   ` Hector Martin
2021-06-01  8:17 ` [PATCH 3/3] ALSA: bebob: " Takashi Sakamoto
2021-06-01 16:37 ` 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=s5hmts9y201.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 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.