From: Takashi Iwai <tiwai@suse.de>
To: Daniel Mack <zonque@gmail.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Florian Mickler <florian@mickler.org>,
Oliver Neukum <oliver@neukum.org>,
linux-usb@vger.kernel.org, alsa-devel@alsa-project.org,
Clemens Ladisch <clemens@ladisch.de>,
pedrib@gmail.com, William Light <wrl@illest.net>,
Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
Robert Hancock <hancockrwd@gmail.com>
Subject: Re: Allocating buffers for USB transfers (again)
Date: Wed, 10 Aug 2011 20:06:48 +0200 [thread overview]
Message-ID: <s5hk4alxhs7.wl%tiwai@suse.de> (raw)
In-Reply-To: <4E42A4AE.4020008@gmail.com>
At Wed, 10 Aug 2011 17:33:02 +0200,
Daniel Mack wrote:
>
> On 08/10/2011 04:32 PM, Alan Stern wrote:
> > Looking at the driver's current code, it appears that your patch
> > does not fix the bug properly. Using discontiguous regions in the
> > transfer buffer is perfectly okay. The real problem is later on,
> > where you do:
> >
> > if (send_it) { out->number_of_packets = FRAMES_PER_URB;
> >
> > This should be
> >
> > out->number_of_packets = outframe;
> >
> > The way it is now, the USB stack will try to use data from all the
> > frame descriptors, and the last few will be stale because the loop
> > doesn't set them.
>
> That's actually true, even though it doesn't seem to cause any trouble.
> I tested everything here of course, and the output URBs return back from
> the USB stack with their length fields zeroed out, which then
> causes the stack to send packets with zero-length fields at the end.
>
> However, doing it right doesn't harm either. Thanks for spotting.
>
> Takashi, can you apply this version?
Yep, applied now. Thanks.
Takashi
next prev parent reply other threads:[~2011-08-10 18:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 11:53 Daniel Mack
2011-07-07 12:14 ` Clemens Ladisch
2011-07-07 12:29 ` Daniel Mack
2011-07-07 12:33 ` Oliver Neukum
2011-07-07 12:38 ` Daniel Mack
2011-07-07 13:08 ` Oliver Neukum
2011-07-08 15:13 ` Daniel Mack
2011-07-07 15:06 ` Alan Stern
2011-07-07 15:16 ` Florian Mickler
2011-08-10 7:51 ` Daniel Mack
2011-08-10 14:32 ` Alan Stern
2011-08-10 15:33 ` Daniel Mack
2011-08-10 18:06 ` Takashi Iwai [this message]
2011-08-10 23:15 ` Sarah Sharp
2011-08-11 0:57 ` Daniel Mack
2011-08-11 16:45 ` Sarah Sharp
2011-08-11 17:27 ` Daniel Mack
2011-08-11 18:05 ` Sarah Sharp
2011-08-11 21:39 ` Daniel Mack
2011-08-11 23:29 ` Matěj Laitl
2011-08-11 23:40 ` Daniel Mack
2011-08-11 23:50 ` Matěj Laitl
2011-08-12 1:28 ` Daniel Mack
2011-08-12 4:46 ` Sarah Sharp
2011-08-12 9:55 ` Daniel Mack
2011-08-11 3:22 ` Andiry Xu
2011-08-11 14:36 ` Alan Stern
2011-07-07 13:53 ` Johannes Stezenbach
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=s5hk4alxhs7.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=florian@mickler.org \
--cc=greg@kroah.com \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=pedrib@gmail.com \
--cc=stern@rowland.harvard.edu \
--cc=wrl@illest.net \
--cc=zonque@gmail.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
all inboxes | Powered by JetHome®