alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mailing Lists <maillist@superlative.org>
Cc: alsa-devel@alsa-project.org, Mike Oliphant <oliphant@nostatic.org>
Subject: Re: [alsa-devel] [PATCH] ALSA: usb-audio: Disable quirks for BOSS Katana amplifiers
Date: Wed, 14 Oct 2020 15:47:57 +0200	[thread overview]
Message-ID: <s5hpn5kkjg2.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAPMdQDnDOF7a9vwuFa1GyFQmZQY4GvDKPeY_NMu2kUDQfqo7fg@mail.gmail.com>

On Wed, 14 Oct 2020 15:33:03 +0200,
Mailing Lists wrote:
> 
> Thanks for the response Takashi,
> 
> How should this be distinguishing between Roland and BOSS? They both have the
> vendor ID 0x0582.

Ah, right, I missed that point :-<

So the question would be rather how to detect BOSS devices
effectively...


thanks,

Takashi

> 
> Cheers,
> 
> Keith
> 
> On Wed, 14 Oct 2020 at 14:09, Takashi Iwai <tiwai@suse.de> wrote:
> 
>     On Wed, 14 Oct 2020 14:17:35 +0200,
>     Mailing Lists wrote:
>     >
>     > Following up on this, it appears there are a bunch of the
>     newer-generation
>     > Roland/Boss devices which need similar treatment.
>     >
>     > So far I have tested the GT-1, the GT-001, and the BR-80, and others
>     have
>     > reported the RC-300 as working with similar modifications. I have been
>     using
>     > the following change to the code in pcm.c set_sync_ep_implicit_fb_quirk:
>     >
>     >     case USB_ID(0x0582, 0x01d8): /* BOSS Katana */
>     >     case USB_ID(0x0582, 0x0130): /* BOSS Micro BR-80 */
>     >     case USB_ID(0x0582, 0x0138): /* BOSS RC-300 */
>     >     case USB_ID(0x0582, 0x01d6): /* BOSS GT-1 */
>     >     case USB_ID(0x0582, 0x01e5): /* BOSS GT-001 */
>     > /* BOSS Katana amplifiers and many other newer BOSS devices do not need
>     quirks
>     > */
>     >
>     > There's probably others too, such as the GT-100 (I believe the GT-001
>     and
>     > GT-100 have similar hardware).
>     >
>     > My question is, should this just be submitted as a patch to pcm.c or
>     would it
>     > be better handled in quirks and, if so, how?
>     >
>     > Or something else?
>    
>     Do we really need this change at all?  I looked at the code again, and
>     I noticed that basically the function should return 0 without setting
>     anything else even if you don't have the explicit ID checks there.
>    
>     The function looks like:
>    
>     static int set_sync_ep_implicit_fb_quirk(struct snd_usb_substream *subs,
>                                              struct usb_device *dev,
>                                              struct usb_interface_descriptor
>     *altsd,
>                                              unsigned int attr)
>     {
>             ....
>             switch (subs->stream->chip->usb_id) {
>             ....
>             case USB_ID(0x0582, 0x01d8): /* BOSS Katana */
>                     /* BOSS Katana amplifiers do not need quirks */
>                     return 0;
>             }
>    
>             if (attr == USB_ENDPOINT_SYNC_ASYNC &&
>                 altsd->bInterfaceClass == USB_CLASS_VENDOR_SPEC &&
>                 altsd->bInterfaceProtocol == 2 &&
>                 altsd->bNumEndpoints == 1 &&
>                 USB_ID_VENDOR(subs->stream->chip->usb_id) == 0x0582 /* Roland
>     */ &&
>                 search_roland_implicit_fb(dev, altsd->bInterfaceNumber + 1,
>                                           altsd->bAlternateSetting,
>                                           &alts, &ep) >= 0) {
>                     goto add_sync_ep;
>             }
>    
>             /* No quirk */
>             return 0;
>    
>     ... and the lengthy if-conditions after the switch/case is applied
>     only for Roland devices, hence it shouldn't influence on BOSS
>     devices.  After that point, the immediate return with 0, which is the
>     same as we do in switch/case.  So the explicit check of BOSS devices
>     there looks superfluous.
> 
>     thanks,
>    
>     Takashi
> 
> --
> --
> Keith A Milner
> 
> 

  reply	other threads:[~2020-10-14 13:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191011171937.8013-1-szszoke.code@gmail.com>
2019-10-17  8:19 ` [alsa-devel] [PATCH] ALSA: usb-audio: Disable quirks for BOSS Katana amplifiers Takashi Iwai
2019-10-17 14:38   ` Szabolcs Szőke
2020-10-14 12:17   ` Mailing Lists
2020-10-14 13:09     ` Takashi Iwai
2020-10-14 13:33       ` Mailing Lists
2020-10-14 13:47         ` Takashi Iwai [this message]
2020-10-14 13:56           ` Mailing Lists
2020-10-14 14:00             ` Takashi Iwai
2020-10-14 14:31               ` Mailing Lists
2020-10-14 14:55                 ` Takashi Iwai
2020-10-14 15:19     ` Mike Oliphant
2020-10-14 15:35       ` Mailing Lists
2020-10-14 16:11         ` Mike Oliphant
2020-10-14 16:34           ` Mailing Lists
2020-10-14 16:46             ` Mike Oliphant
2020-10-14 17:23               ` Mailing Lists
2020-10-14 18:17                 ` Mike Oliphant
2020-10-14 20:57                   ` Keith Milner
2020-10-14 21:49                     ` Mike Oliphant
2020-10-15 12:37                       ` Takashi Iwai
2020-10-16  1:21                         ` Mike Oliphant

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=s5hpn5kkjg2.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=maillist@superlative.org \
    --cc=oliphant@nostatic.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;
as well as URLs for NNTP newsgroup(s).