All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Geoffrey D. Bennett" <g@b4.vu>
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA: scarlett2: Default on?
Date: Thu, 24 Jun 2021 19:40:53 +0200	[thread overview]
Message-ID: <s5hk0mjkvoa.wl-tiwai@suse.de> (raw)
In-Reply-To: <20210624154739.GA20351@m.b4.vu>

On Thu, 24 Jun 2021 17:47:39 +0200,
Geoffrey D. Bennett wrote:
> 
> On Wed, Jun 23, 2021 at 08:39:24AM +0200, Takashi Iwai wrote:
> [...]
> > OK, now all patches have been merged.
> 
> Thanks!
> 
> I would next like to consider how we can enable this mixer driver by
> default. I originally added the device_setup=1 gate because there were
> reports of the driver making the interface hang. These were all traced
> back to the problem which was resolved with the commit "Fix device
> hang with ehci-pci". That commit fixed the issue for those who had
> reported it and since then there have been no more reports that the
> mixer driver causes any issues.
> 
> Simply removing the device_setup=1 check would leave users with no way
> to disable the driver in case that turns out to be necessary for some
> reason though, so I don't think that's a good idea.

They can blacklist snd-usb-audio, either the module itself (if it's
the only device), or with enable option of snd-usb-audio module, if
there are multiple devices bound with the driver.

> What I think would be the best option would be to have the driver as
> its own loadable module. Does this sound like a good idea to you?

I'm not against splitting, but that is no solution at all, per se.


Takashi

  reply	other threads:[~2021-06-24 17:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24 15:47 ALSA: scarlett2: Default on? Geoffrey D. Bennett
2021-06-24 17:40 ` Takashi Iwai [this message]
2021-06-25  2:11   ` Geoffrey D. Bennett
2021-06-25  7:37     ` 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=s5hk0mjkvoa.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=g@b4.vu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.