mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] firewire: core: add device quirk detection
Date: Thu, 16 Oct 2025 09:06:29 +0900	[thread overview]
Message-ID: <20251016000629.GA208195@workstation.local> (raw)
In-Reply-To: <20251013140311.97159-1-o-takashi@sakamocchi.jp>

On Mon, Oct 13, 2025 at 11:03:09PM +0900, Takashi Sakamoto wrote:
> Hi,
> 
> In the history of this subsystem, we have experienced some device-specific
> quirks. For example:
> 
> * afa1282a35d3 ("firewire: core: check for 1394a compliant IRM, fix inaccessibility of Sony camcorder").
> * a509e43ff338 ("firewire: core: fix unstable I/O with Canon camcorder").
> * 3a93d082bacf ("ALSA: firewire-motu: add support for MOTU Audio Express")
> 
> However, there is no common mechanism to handle such quirks. This patchset
> adds a consistent approach for detecting and managing device-specific
> quirks within the subsystem.
> 
> Takashi Sakamoto (2):
>   firewire: core: detect device quirk when reading configuration ROM
>   firewire: core: handle device quirk of MOTu Audio Express
> 
>  drivers/firewire/core-card.c   | 21 +++------
>  drivers/firewire/core-device.c | 78 +++++++++++++++++++++++++++++++++-
>  drivers/firewire/ohci.c        | 29 +++++++++++++
>  include/linux/firewire.h       | 14 ++++++
>  4 files changed, 126 insertions(+), 16 deletions(-)

Applied to for-next branch.


Regards

Takashi Sakamoto

      parent reply	other threads:[~2025-10-16  0:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13 14:03 Takashi Sakamoto
2025-10-13 14:03 ` [PATCH 1/2] firewire: core: detect device quirk when reading configuration ROM Takashi Sakamoto
2025-10-13 14:03 ` [PATCH 2/2] firewire: core: handle device quirk of MOTU Audio Express Takashi Sakamoto
2025-10-16  0:06 ` 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=20251016000629.GA208195@workstation.local \
    --to=o-takashi@sakamocchi.jp \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®