From: Takashi Iwai <tiwai@suse.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org, Nicolas DEFFAYET <nicolas@deffayet.com>
Subject: Re: [PATCH] ALSA: usb-audio: work around KEF X300A firmware bug
Date: Mon, 17 Feb 2014 10:12:16 +0100 [thread overview]
Message-ID: <s5hob2614sv.wl%tiwai@suse.de> (raw)
In-Reply-To: <5300E31E.9070600@ladisch.de>
At Sun, 16 Feb 2014 17:11:10 +0100,
Clemens Ladisch wrote:
>
> When the driver tries to access Function Unit 10, the KEF X300A
> speakers' firmware apparently locks up, making even PCM streaming
> impossible. Work around this by ignoring this FU.
>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Clemens Ladisch <clemens@ladisch.de>
Thanks, applied.
Takashi
> ---
> sound/usb/mixer_maps.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/sound/usb/mixer_maps.c b/sound/usb/mixer_maps.c
> index 32af6b7..d1d72ff 100644
> --- a/sound/usb/mixer_maps.c
> +++ b/sound/usb/mixer_maps.c
> @@ -328,6 +328,11 @@ static struct usbmix_name_map gamecom780_map[] = {
> {}
> };
>
> +static const struct usbmix_name_map kef_x300a_map[] = {
> + { 10, NULL }, /* firmware locks up (?) when we try to access this FU */
> + { 0 }
> +};
> +
> /*
> * Control map entries
> */
> @@ -419,6 +424,10 @@ static struct usbmix_ctl_map usbmix_ctl_maps[] = {
> .id = USB_ID(0x200c, 0x1018),
> .map = ebox44_map,
> },
> + {
> + .id = USB_ID(0x27ac, 0x1000),
> + .map = kef_x300a_map,
> + },
> { 0 } /* terminator */
> };
>
next prev parent reply other threads:[~2014-02-17 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1392284545.11227.4.camel@srv31.corp.novso.com>
2014-02-16 16:11 ` [PATCH] ALSA: usb-audio: work around KEF X300A firmware bug Clemens Ladisch
2014-02-17 9:12 ` Takashi Iwai [this message]
2015-11-26 16:45 Patrick Laughlin
2015-11-27 9:23 ` Clemens Ladisch
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=s5hob2614sv.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=nicolas@deffayet.com \
/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