Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Hanh Kieu <hhkieu@gmail.com>
To: geraldogabriel@gmail.com, perex@perex.cz, tiwai@suse.com
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: usb-audio: add Pioneer DJ DDJ-SZ support
Date: Fri,  4 Sep 2026 11:20:23 -0700	[thread overview]
Message-ID: <20260904182023.4486-1-hhkieu@gmail.com> (raw)
In-Reply-To: <CAEsQvcuaNZvLxyxNH_NOy5qwTmkrk-A9QdVtZD0GiCtPwk4A+A@mail.gmail.com>

Geraldo Nascimento wrote:
> Are you sure is_pioneer_implicit_fb() isn't returning false and you're
> picking up on a generic sync ep instead?
>
> You should double-check that function is returning true or false because
> it will return false when USB_ENDPOINT_USAGE_IMPLICIT_FB isn't
> set on bmAttributes of a Isochronous IN EP.

Good catch, thanks -- I checked against the real device rather than
assuming.

lsusb -v on the DDJ-SZ shows both endpoints (0x01 OUT, 0x82 IN) as
Isochronous / Asynchronous with Usage Type = Data (bmAttributes = 0x05).
is_pioneer_implicit_fb() accepts the capture endpoint's usage being
either USB_ENDPOINT_USAGE_DATA or USB_ENDPOINT_USAGE_IMPLICIT_FB, not
IMPLICIT_FB exclusively, so Data usage does pass that check.

I also traced snd_usb_parse_implicit_fb_quirk()'s dispatch order for
this device to make sure nothing generic intercepts first: no fixed or
capture quirk-table entry matches 08e4:0191, it isn't UAC2
(bInterfaceClass is vendor-spec, not USB_CLASS_AUDIO), and it isn't the
Roland vendor ID. So is_pioneer_implicit_fb() is the function actually
being reached and returning true for this device, not a coincidental
generic fallback.

Happy to add a comment near the quirk-table entry noting the real
bmAttributes value if that would help future readers.

Thanks,
Hanh Kieu

  reply	other threads:[~2026-09-04 18:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03 23:16 [PATCH] ALSA: usb-audio: add Pioneer DJ DDJ-SZ support Hanh Kieu
2026-09-04  3:59 ` Geraldo Nascimento
2026-09-04 18:20   ` Hanh Kieu [this message]
2026-09-05  3:30     ` Geraldo Nascimento
     [not found]       ` <CAEWo5SpV6eyHo-tn+hKX4s98uCjGJg5Dz9fMkoWNDNqgofJ5og@mail.gmail.com>
2026-09-05  6:19         ` Geraldo Nascimento

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=20260904182023.4486-1-hhkieu@gmail.com \
    --to=hhkieu@gmail.com \
    --cc=geraldogabriel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    /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