From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org
Subject: Re: [PATCH 0/2] firewire: core: allow unit drivers to schedule work item to process isochronous context
Date: Mon, 9 Sep 2024 09:22:29 +0900 [thread overview]
Message-ID: <20240909002229.GA84487@workstation.local> (raw)
In-Reply-To: <20240908040549.75304-1-o-takashi@sakamocchi.jp>
On Sun, Sep 08, 2024 at 01:05:47PM +0900, Takashi Sakamoto wrote:
> Hi,
>
> ALSA firewire stack uses packet-per-buffer mode for both isochronous
> receive (IR) and transmit (IT) contexts of 1394 OHCI. To process time
> stamp per packet (or per sample in some cases) steadily for media clock
> recovery against unexpected transmission skips in the IR context, it uses
> an IT context to operate all of isochronous contexts by calls of
> fw_iso_context_flush_completions() in the bottom-half of hardIRQ for the
> IT context.
>
> Although it looks well to handle all of isochronous contexts in a single
> bottom-half context, it relatively takes longer time to finish. In the
> future code integration (not yet), it is possible to apply parallelism
> method to process these context. In the case, it is useful to allow unit
> drivers to schedule work items to process these isochronous contexts.
>
> As a preparation, in this series of changes,
> fw_iso_context_schedule_flush_completions() is exposed as a kernel API
> available by unit drivers. It is a counter part of
> fw_iso_context_flush_completions(). This series of changes also includes
> documentation about these kernel APIs.
>
> Takashi Sakamoto (2):
> firewire: core: expose kernel API to schedule work item to process
> isochronous context
> firewire: core: fulfill documentation of
> fw_iso_context_flush_completions()
>
> Documentation/driver-api/firewire.rst | 2 ++
> drivers/firewire/core-iso.c | 11 +++++++++++
> drivers/firewire/core.h | 5 -----
> drivers/firewire/ohci.c | 4 ++--
> include/linux/firewire.h | 17 +++++++++++++++++
> 5 files changed, 32 insertions(+), 7 deletions(-)
Applied to for-next branch.
Regards
Takashi Sakamoto
prev parent reply other threads:[~2024-09-09 0:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 4:05 [PATCH 0/2] firewire: core: allow unit drivers to schedule work item to process isochronous context Takashi Sakamoto
2024-09-08 4:05 ` [PATCH 1/2] firewire: core: expose kernel API " Takashi Sakamoto
2024-09-08 4:05 ` [PATCH 2/2] firewire: core: fulfill documentation of fw_iso_context_flush_completions() Takashi Sakamoto
2024-09-09 0:22 ` 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=20240909002229.GA84487@workstation.local \
--to=o-takashi@sakamocchi.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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.