From: "Geoffrey D. Bennett" <g@b4.vu>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH V6 RESEND] ALSA: usb-audio: Scarlett Gen 2 mixer interface
Date: Sat, 20 Jul 2019 00:38:48 +0930 [thread overview]
Message-ID: <20190719150848.GA11924@b4.vu> (raw)
In-Reply-To: <s5hd0i7nxue.wl-tiwai@suse.de>
Hi Takashi,
On Thu, Jul 18, 2019 at 05:53:13PM +0200, Takashi Iwai wrote:
[...]
> Thanks, the patch looks almost good, but it's already too late for
> 5.3, so I'm going to queue this for 5.4 after 5.3 merge window is
> closed in this week.
Thank you. I really appreciate your assistance and feedback.
> But, before that, maybe one more refresh would be appreciated.
> Namely,
>
> - We need a verification of the fixed pipe before actually submitting
> urb. scarlett2_usb() calls with usb_sndctrlpipe(), and this pipe
> has to be verified beforehand. See the commit 801ebf1043ae for
> details.
I had a look at that commit, and I think I don't need to change
scarlett2_usb() because it calls snd_usb_ctl_msg() which already calls
the snd_usb_pipe_sanity_check() function to verify the pipe.
I'm thinking though that scarlett2_mixer_status_create() which does
something like this:
struct usb_device *dev = mixer->chip->dev;
unsigned int pipe = usb_rcvintpipe(dev, SCARLETT2_USB_INTERRUPT_ENDPOINT);
...
usb_fill_int_urb(mixer->urb, dev, pipe, ...);
usb_submit_urb(mixer->urb, GFP_KERNEL);
probably needs this added:
if (snd_usb_pipe_sanity_check(dev, pipe))
return -EINVAL;
Do you agree?
> - Some pointers seem to be initialized as "0". Use NULL instead.
Will fix.
Regards,
Geoffrey.
next prev parent reply other threads:[~2019-07-19 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 15:51 [PATCH V6 RESEND] ALSA: usb-audio: Scarlett Gen 2 mixer interface Geoffrey D. Bennett
2019-07-18 15:53 ` Takashi Iwai
2019-07-19 15:08 ` Geoffrey D. Bennett [this message]
2019-07-19 15:13 ` 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=20190719150848.GA11924@b4.vu \
--to=g@b4.vu \
--cc=alsa-devel@alsa-project.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 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.