From: Kirill Marinushkin <k.marinushkin@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: perex@perex.cz, alsa-devel@alsa-project.org,
Stephen Barber <smbarber@chromium.org>,
Bhumika Goyal <bhumirks@gmail.com>,
Jaejoong Kim <climbbb.kim@gmail.com>,
Julian Scheel <julian@jusst.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: usb-audio: Fix UAC2 get_ctl request with a RANGE attribute
Date: Thu, 8 Feb 2018 07:21:36 +0100 [thread overview]
Message-ID: <40196230-8f73-4cca-08e5-d67bfbea2d6e@gmail.com> (raw)
In-Reply-To: <s5hvaf95p4i.wl-tiwai@suse.de>
On 02/07/18 06:45, Takashi Iwai wrote:
> On Mon, 29 Jan 2018 06:37:55 +0100,
> Kirill Marinushkin wrote:
>> The layout of the UAC2 Control request and response varies depending on
>> the request type. With the current implementation, only the Layout 2
>> Parameter Block (with the 2-byte sized RANGE attribute) is handled
>> properly. For the Control requests with the 1-byte sized RANGE attribute
>> (Bass Control, Mid Control, Tremble Control), the response is parsed
>> incorrectly.
>>
>> This commit:
>> * fixes the wLength field value in the request
>> * fixes parsing the range values from the response
>>
>> Fixes: 23caaf19b11e ("ALSA: usb-mixer: Add support for Audio Class v2.0")
>> Signed-off-by: Kirill Marinushkin <k.marinushkin@gmail.com>
>> Cc: Jaroslav Kysela <perex@perex.cz>
>> Cc: Takashi Iwai <tiwai@suse.com>
>> Cc: Jaejoong Kim <climbbb.kim@gmail.com>
>> Cc: Bhumika Goyal <bhumirks@gmail.com>
>> Cc: Stephen Barber <smbarber@chromium.org>
>> Cc: Julian Scheel <julian@jusst.de>
>> Cc: alsa-devel@alsa-project.org
>> Cc: linux-kernel@vger.kernel.org
> Sorry for the late reply, as I've been (and still) off.
>
> Does this bug actually hit on any real devices, or is it only a
> logical error so far? In the former case, a Cc to stable is
> mandatory.
>
> In anyway, I'll review and merge it properly once after I back to
> work.
>
>
> thanks,
>
> Takashi
Hello Takashi,
Thank you for your answer. I will wait until you are back to work, don't
worry about the late replies.
I did not hit the issue on a real device.
During my UAC2 experiments, I reproduced this issue on the development
board, and then tested my solution on it.
Best Regards,
Kirill
next prev parent reply other threads:[~2018-02-08 6:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 5:37 [PATCH] ALSA: usb-audio: Fix UAC2 get_ctl request with a RANGE attribute Kirill Marinushkin
2018-02-07 5:45 ` Takashi Iwai
2018-02-08 6:21 ` Kirill Marinushkin [this message]
2018-02-12 8:08 ` Takashi Iwai
2018-02-12 19:32 ` Kirill Marinushkin
2018-02-13 5:04 ` Takashi Iwai
2018-02-13 16:27 ` Kirill Marinushkin
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=40196230-8f73-4cca-08e5-d67bfbea2d6e@gmail.com \
--to=k.marinushkin@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=bhumirks@gmail.com \
--cc=climbbb.kim@gmail.com \
--cc=julian@jusst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=smbarber@chromium.org \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).