linux-kernel - Re: [alsa-devel] [PATCH] ALSA: usb-audio: fix Line6 Helix audio format rates

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <s5hzhlvmsc7.wl-tiwai@suse.de>
Date:   Wed, 03 Jul 2019 10:32:08 +0200
From:   Takashi Iwai <tiwai@...e.de>
To:     "Wasko, Michal" <michal.wasko@...ux.intel.com>
Cc:     nick83ola <nick83ola@...il.com>, alsa-devel@...a-project.org,
        info@...sverwiebe.de,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org,
        Richard Fontana <rfontana@...hat.com>,
        Jussi Laako <jussi@...arnerd.net>,
        Thomas Gleixner <tglx@...utronix.de>,
        Allison Randal <allison@...utok.net>
Subject: Re: [alsa-devel] [PATCH] ALSA: usb-audio: fix Line6 Helix audio format rates

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