From: Takashi Iwai <tiwai@suse.de>
To: "Wasko, Michal" <michal.wasko@linux.intel.com>
Cc: nick83ola <nick83ola@gmail.com>,
alsa-devel@alsa-project.org, info@jensverwiebe.de,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Richard Fontana <rfontana@redhat.com>,
Jussi Laako <jussi@sonarnerd.net>,
Thomas Gleixner <tglx@linutronix.de>,
Allison Randal <allison@lohutok.net>
Subject: Re: [alsa-devel] [PATCH] ALSA: usb-audio: fix Line6 Helix audio format rates
Date: Wed, 03 Jul 2019 10:32:08 +0200 [thread overview]
Message-ID: <s5hzhlvmsc7.wl-tiwai@suse.de> (raw)
In-Reply-To: <38462424-4e2b-bdbd-f7cc-ea94385924e0@linux.intel.com>
On Wed, 03 Jul 2019 10:26:31 +0200,
Wasko, Michal wrote:
>
> >> My idea is that if line6 in the future fixes their code (they are quite active
> >> on the helix line) the call will not fail and we get a proper device without
> >> quirks.
> >> But If the driver fail to get the clock this settings works as a "failsafe"
> >> and get the device working.
> >> I also tried to contact their support but they don't care a lot about Linux
> >> for now :-(
> > The fallback might be good, but I'm not sure whether there are many
> > devices that hit the same problem. If we encounter more, let's try to
> > make it as a fallback.
> > thanks,
> >
> > Takashi
> Since there is a chance that the issue will be addressed in USB device FW
> thanthe fallback mechanism will make sense. It would cover eventual future
> scenario withdevices that will have the issue fixed.
Fair enough. Let's handle it as fallback, then.
thanks,
Takashi
prev parent reply other threads:[~2019-07-03 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 0:43 [PATCH] ALSA: usb-audio: fix Line6 Helix audio format rates Nicola Lunghi
2019-07-02 14:37 ` Takashi Iwai
2019-07-02 15:52 ` [alsa-devel] " Wasko, Michal
2019-07-02 15:57 ` Takashi Iwai
[not found] ` <CABPh3UMttE1s7oNt0-JLNm2N3wxb-JXBTLzMYZM42ENiy9NC9Q@mail.gmail.com>
2019-07-03 7:49 ` Takashi Iwai
2019-07-03 8:26 ` Wasko, Michal
2019-07-03 8:32 ` Takashi Iwai [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=s5hzhlvmsc7.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=allison@lohutok.net \
--cc=alsa-devel@alsa-project.org \
--cc=gregkh@linuxfoundation.org \
--cc=info@jensverwiebe.de \
--cc=jussi@sonarnerd.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.wasko@linux.intel.com \
--cc=nick83ola@gmail.com \
--cc=rfontana@redhat.com \
--cc=tglx@linutronix.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