Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Mark Hills <mark@xwax.org>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>
Subject: Re: Regression in Final Scratch 'ScratchAmp' quirk (DJ interface)
Date: Wed, 3 Jan 2024 20:53:40 -0300	[thread overview]
Message-ID: <ZZXzhKbCEK04caa2@geday> (raw)
In-Reply-To: <05f7b47d-1762-c6aa-ddb1-3c6f6128cf44@xwax.org>

On Wed, Jan 03, 2024 at 03:54:29PM +0000, Mark Hills wrote:
> The ScratchAmp worked perfectly with a quirk, but now that seems to have 
> regressed and the device is no longer detected [1].
> 
> It's design is from 2002, based on class-compliant (Philips UDA1325H) 
> chips. It hides itself behind a 'vendor specific' description, presumably 
> as it was launched in a closed system with specific hardware and software 
> for DJ'ing.

Hi Mark, great fan of your work with xwax here.

Perhaps adding USB_DEVICE_VENDOR_SPEC(0x103d, 0x0100) and
USB_DEVICE_VENDOR_SPEC(0x103d, 0x0101) to quirks-table.h can do the
trick?

Regards,
Geraldo Nascimento

> 
> So this quirk was introduced in 2007:
> 
> +/* Stanton/N2IT Final Scratch v1 device ('Scratchamp') */
> +{
> +	USB_DEVICE(0x103d, 0x0100),
> +		.driver_info = (unsigned long) & (const struct snd_usb_audio_quirk) {
> +		.vendor_name = "Stanton",
> +		.product_name = "ScratchAmp",
> +		.ifnum = QUIRK_NO_INTERFACE
> +	}
> +},
> +{
> +	USB_DEVICE(0x103d, 0x0101),
> +		.driver_info = (unsigned long) & (const struct snd_usb_audio_quirk) {
> +		.vendor_name = "Stanton",
> +		.product_name = "ScratchAmp",
> +		.ifnum = QUIRK_NO_INTERFACE
> +	}
> +},
> 
> In a modern kernel, the (ineffective) quirk is now in sound/usb/card.c:
> 
> +	/* Stanton/N2IT Final Scratch v1 device ('Scratchamp') */
> +	DEVICE_NAME(0x103d, 0x0100, "Stanton", "ScratchAmp"),
> +	DEVICE_NAME(0x103d, 0x0101, "Stanton", "ScratchAmp"),
> 
> Is there a functional difference between these quirks and/or any reason 
> the device would no longer be detected?
> 
> I noted the commits went via use of QUIRK_RENAME_DEVICE(), perhaps 
> misleading the refactoring to assume the quirk was purely a rename.
> 
> Below is an "lsusb" of the device, dated from 2008; I don't currently have 
> access to my own device, or know exactly when this regressed.
> 
> Many thanks
> 
> [1] https://sourceforge.net/p/xwax/mailman/message/48496984/
> [2] http://www.pogo.org.uk/~mark/linuxdj/scratchamp.html
> [3] https://finalscratch.sourceforge.net/innards/
> 
> -- 
> Mark

  reply	other threads:[~2024-01-03 23:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03 15:54 Regression in Final Scratch 'ScratchAmp' quirk (DJ interface) Mark Hills
2024-01-03 23:53 ` Geraldo Nascimento [this message]
2024-01-04  9:42   ` Takashi Iwai

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=ZZXzhKbCEK04caa2@geday \
    --to=geraldogabriel@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=mark@xwax.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox