All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, clemens@ladisch.de
Subject: Re: [PATCH 00/15] ALSA: firewire-tascam/fireface: reserve/release isochronous resources in pcm.hw_params/hw_free callbacks
Date: Tue, 11 Jun 2019 18:59:10 +0900	[thread overview]
Message-ID: <20190611095909.GA19071@workstation> (raw)
In-Reply-To: <s5hblz4bgyy.wl-tiwai@suse.de>

On Tue, Jun 11, 2019 at 11:37:25AM +0200, Takashi Iwai wrote:
> On Sun, 02 Jun 2019 09:12:44 +0200,
> Takashi Sakamoto wrote:
> > 
> > Hi,
> > 
> > This patchset is a part of series of patches for all of drivers in
> > ALSA firewire stack to reserve/release isochronous resources in
> > pcm.hw_params/hw_free callbacks.
> > 
> > In current implementation, the resources are reserved at the same time
> > to start packet streaming, and released at the same time to stop packet
> > streaming. However, once allocated, the resources are available
> > independent of lifetime of packet streaming.
> > 
> > The isochronous resources are the resources of IEEE 1394 bus. On the
> > other side of view, it's a kind of resources of hardware to maintain
> > the bus (isochronous resource manager). For this kind of reservation and
> > release, hw_params and hw_free operations are suitable in ALSA PCM
> > interface.
> > 
> > Ideally, the operation to reserve/release isochronous resource should
> > be separated from the operation to start/stop packet streaming. However,
> > IEEE 1394 bus has reset event. Once reset occurs, isochronous resource
> > manager releases allocated resources. The resources should be
> > reallocated by requesters themselves. For this reason, in this patchset,
> > bus generation is checked before starting packet streaming. If
> > generation is updated, reallocation is requested to isochronous
> > resource manager, then packet streaming starts.
> > 
> > Takashi Sakamoto (15):
> >   ALSA: firewire-tascam: code refactoring for registration of
> >     isochronous channels
> >   ALSA: firewire-tascam: code refactoring for reservation of isochronous
> >     resources
> >   ALSA: firewire-tascam: code refactoring for release of isochronous
> >     resources
> >   ALSA: firewire-tascam: reserve/release isochronous resources in
> >     pcm.hw_params/hw_free callbacks
> >   ALSA: firewire-tascam: update isochronous resources when starting
> >     packet streaming after bus reset
> >   ALSA: firewire-tascam: minor code refactoring to finish streaming
> >     session
> >   ALSA: firewire-tascam: code refactoring for pcm.hw_params/hw_free
> >     callbacks
> >   ALSA: fireface: add protocol-specific operation to allocate
> >     isochronous resources
> >   ALSA: fireface: support allocate_resources operation in ff800 protocol
> >   ALSA: fireface: support allocate_resources operation in ff400 protocol
> >   ALSA: fireface: support allocate_resources operation in latter
> >     protocol
> >   ALSA: fireface: reserve/release isochronous resources in
> >     pcm.hw_params/hw_free callbacks
> >   ALSA: fireface: update isochronous resources when starting packet
> >     streaming after bus-reset
> >   ALSA: fireface: minor code refactoring to finish streaming session
> >   ALSA: fireface: code refactoring for pcm.hw_params/hw_free callbacks
> 
> Applied all 15 patches now.  Thanks.

Welcome back ;)

I've already prepared similar patchsets for the other drivers in ALSA
firewire stack. You'll receive the patchset several times in this week.
I'm happy if you review and apply them.


Thanks

Takashi Sakamoto

      reply	other threads:[~2019-06-11  9:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-02  7:12 [PATCH 00/15] ALSA: firewire-tascam/fireface: reserve/release isochronous resources in pcm.hw_params/hw_free callbacks Takashi Sakamoto
2019-06-02  7:12 ` [PATCH 01/15] ALSA: firewire-tascam: code refactoring for registration of isochronous channels Takashi Sakamoto
2019-06-02  7:12 ` [PATCH 02/15] ALSA: firewire-tascam: code refactoring for reservation of isochronous resources Takashi Sakamoto
2019-06-02  7:12 ` [PATCH 03/15] ALSA: firewire-tascam: code refactoring for release " Takashi Sakamoto
2019-06-02  7:12 ` [PATCH 04/15] ALSA: firewire-tascam: reserve/release isochronous resources in pcm.hw_params/hw_free callbacks Takashi Sakamoto
2019-06-02  7:12 ` [PATCH 05/15] ALSA: firewire-tascam: update isochronous resources when starting packet streaming after bus reset Takashi Sakamoto
2019-06-02  7:12 ` [PATCH 06/15] ALSA: firewire-tascam: minor code refactoring to finish streaming session Takashi Sakamoto
2019-06-02  7:12 ` [PATCH 07/15] ALSA: firewire-tascam: code refactoring for pcm.hw_params/hw_free callbacks Takashi Sakamoto
2019-06-02  7:12 ` [PATCH 08/15] ALSA: fireface: add protocol-specific operation to allocate isochronous resources Takashi Sakamoto
2019-06-02  7:12 ` [PATCH 09/15] ALSA: fireface: support allocate_resources operation in ff800 protocol Takashi Sakamoto
2019-06-02  7:12 ` [PATCH 10/15] ALSA: fireface: support allocate_resources operation in ff400 protocol Takashi Sakamoto
2019-06-02  7:12 ` [PATCH 11/15] ALSA: fireface: support allocate_resources operation in latter protocol Takashi Sakamoto
2019-06-02  7:12 ` [PATCH 12/15] ALSA: fireface: reserve/release isochronous resources in pcm.hw_params/hw_free callbacks Takashi Sakamoto
2019-06-02  7:12 ` [PATCH 13/15] ALSA: fireface: update isochronous resources when starting packet streaming after bus-reset Takashi Sakamoto
2019-06-02  7:12 ` [PATCH 14/15] ALSA: fireface: minor code refactoring to finish streaming session Takashi Sakamoto
2019-06-02  7:12 ` [PATCH 15/15] ALSA: fireface: code refactoring for pcm.hw_params/hw_free callbacks Takashi Sakamoto
2019-06-11  9:37 ` [PATCH 00/15] ALSA: firewire-tascam/fireface: reserve/release isochronous resources in " Takashi Iwai
2019-06-11  9:59   ` Takashi Sakamoto [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=20190611095909.GA19071@workstation \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --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.