The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: [GIT PULL] firewire updates for v6.19
Date: Tue, 2 Dec 2025 08:22:43 +0900	[thread overview]
Message-ID: <20251201232243.GA293104@workstation.local> (raw)

Hi Linus,

Please pull the updates for firewire subsystem to your tree. It includes
core function changes, and all users get affects from them. I would
appreciate receiving any test report from the users.

The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:

  Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git tags/firewire-updates-6.19

for you to fetch changes up to 036176d9dba74e23e3ef358e171a77b75837fee0:

  firewire: core: abort pending transactions at card removal (2025-11-14 04:30:58 +0900)

----------------------------------------------------------------
firewire updates for v6.19

This release includes two changes for core functions, which affects all
use cases of this subsystem.

 - Handle per-device interoperability quirks
   It is well known that some devices have quirks affecting
   interoperability. To identify such quirks at an early stages of
   device detection, the step for reading the configuration ROM contents
   has been changed. As a side effect, the entire detection process is
   now performed at the basic transaction speed (S100), without no trial
   to probe higher supported speeds.
   With this change, the following devices should now work with fewer
   issues:
   - TASCAM FW-1884, FW-1804, and FW-1082
   - MOTU Audio Express

 - Safer removals of host card
   There was a race condition between host card removal and handling of
   bus reset events in the workqueue. This appears to be a long standing
   issue (for a dozen years or so[1]), and recent changes to use more
   workqueues escalate it. To solve it, a new callback has been added to
   the 1394 OHCI PCI driver to unregister the interrupt sources and wait
   for workqueue completions when removing a card instance.

[1] https://sourceforge.net/p/linux1394/mailman/linux1394-devel/thread/20250629024836.GA16759%40workstation.local/#msg59200628

----------------------------------------------------------------
Marco Crivellari (1):
      firewire: core: add WQ_UNBOUND to alloc_workqueue users

Takashi Sakamoto (11):
      firewire: core: detect device quirk when reading configuration ROM
      firewire: core: handle device quirk of MOTU Audio Express
      firewire: core: code refactoring to compute transaction speed
      firewire: core: determine transaction speed after detecting quirks
      firewire: core: handle device quirk of TASCAM FW-1884/FW-1804/FW-1082
      ALSA: firewire-tascam: reserve resources for transferred isochronous packets at S400
      firewire: core: use cleanup function to release cached configuration ROM
      firewire: core: code refactoring to remove transaction entry
      firewire: core: code refactoring to find and pop transaction entry
      firewire: core: clear sources of hardware interrupt at card removal
      firewire: core: abort pending transactions at card removal

 drivers/firewire/core-card.c          |  25 +++++++++-----------
 drivers/firewire/core-device.c        | 194 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-----------------------------------------------
 drivers/firewire/core-transaction.c   |  88 +++++++++++++++++++++++++++++++++++++++++++++++-----------------------
 drivers/firewire/core.h               |   5 ++++
 drivers/firewire/ohci.c               |  78 +++++++++++++++++++++++++++++++++++++++++++++++++++-----------
 include/linux/firewire.h              |  17 ++++++++++++++
 sound/firewire/tascam/tascam-stream.c |  21 +++++++++--------
 7 files changed, 304 insertions(+), 124 deletions(-)


Regards

Takashi Sakamoto

             reply	other threads:[~2025-12-01 23:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01 23:22 Takashi Sakamoto [this message]
2025-12-04 20:41 ` [GIT PULL] firewire updates for v6.19 pr-tracker-bot

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=20251201232243.GA293104@workstation.local \
    --to=o-takashi@sakamocchi.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=torvalds@linux-foundation.org \
    /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