Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: ffado-devel@lists.sourceforge.net, alsa-devel@alsa-project.org,
	clemens@ladisch.de
Subject: Re: [PATCH 0/5] ALSA: fireface: add support for Fireface 800 with streaming functionality
Date: Sun, 16 Dec 2018 10:20:07 +0100	[thread overview]
Message-ID: <s5hmup5rfp4.wl-tiwai@suse.de> (raw)
In-Reply-To: <20181216083233.11358-1-o-takashi@sakamocchi.jp>

On Sun, 16 Dec 2018 09:32:28 +0100,
Takashi Sakamoto wrote:
> 
> Hi,
> 
> My former patchset adds support for Fireface 800 with MIDI functionality
> only[1]. This patchset updates driver with packet streaming
> functionality. As a result, both of PCM frames/MIDI messages are
> available.
> 
> This patchset is based on my former patch to fix a bug to switch
> frame fetching mode:
> 
> [alsa-devel] [PATCH] ALSA: fireface: fix for state to fetch PCM frames
> http://mailman.alsa-project.org/pipermail/alsa-devel/2018-December/143150.html
> 
> Unfortunately, my initial commit of ALSA fireface driver in v4.12 kernel
> includes bugs to handle tx isochronous packets. When testing this
> patchset, please apply below patchset in advance:
> 
> [alsa-devel] [PATCH 0/3] ALSA: firewire-lib: fixes for processing packets without CIP header
> http://mailman.alsa-project.org/pipermail/alsa-devel/2018-December/143146.html
> 
> For testers, a remote branch including overall patches is available in
> my remote repository in github.com[2]. They can be backport to Linux
> kernel v4.17 or later.
> 
> I note that this driver can generate hissing noise long-periodically as I
> reported for Fireface 400[3]. The cause is not cleared yet.
> 
> [1] http://mailman.alsa-project.org/pipermail/alsa-devel/2018-December/142826.html
> [2] https://github.com/takaswie/snd-firewire-improve/tree/topic/ff800-pcm
> [3] http://mailman.alsa-project.org/pipermail/alsa-devel/2015-December/102261.html
> 
> Takashi Sakamoto (5):
>   ALSA: fireface: share helper function to switch fetching mode
>   ALSA: fireface: code refactoring to handle multiplier mode
>   ALSA: fireface: allocate isochronous resources in mode-specific
>     implementation
>   ALSA: fireface: add support for packet streaming on Fireface 800
>   ALSA: fireface: code refactoring to handle model-specific registers

Applied all five patches now.  Thanks.


Takashi

      parent reply	other threads:[~2018-12-16  9:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-16  8:32 [PATCH 0/5] ALSA: fireface: add support for Fireface 800 with streaming functionality Takashi Sakamoto
2018-12-16  8:32 ` [PATCH 1/5] ALSA: fireface: share helper function to switch fetching mode Takashi Sakamoto
2018-12-16  8:32 ` [PATCH 2/5] ALSA: fireface: code refactoring to handle multiplier mode Takashi Sakamoto
2018-12-16  8:32 ` [PATCH 3/5] ALSA: fireface: allocate isochronous resources in mode-specific implementation Takashi Sakamoto
2018-12-16  8:32 ` [PATCH 4/5] ALSA: fireface: add support for packet streaming on Fireface 800 Takashi Sakamoto
2018-12-16  8:32 ` [PATCH 5/5] ALSA: fireface: code refactoring to handle model-specific registers Takashi Sakamoto
2018-12-16  9:20 ` 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=s5hmup5rfp4.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=ffado-devel@lists.sourceforge.net \
    --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