From: Felipe Balbi <balbi@ti.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Sergei Shtylyov <sshtylyov@mvista.com>,
"Balbi, Felipe" <balbi@ti.com>, "greg@kroah.com" <greg@kroah.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Brownell <dbrownell@users.sourceforge.net>,
"Gadiyar, Anand" <gadiyar@ti.com>,
Mike Frysinger <vapier@gentoo.org>
Subject: Re: [Discussion] USB: musb-gadget: how to fix ZLP issue in musb_g_tx
Date: Wed, 15 Sep 2010 13:56:41 +0300 [thread overview]
Message-ID: <20100915105641.GO3393@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <AANLkTinPVUBNJoOR496KgSy2TT0f6i1f5xEKVhKod2R=@mail.gmail.com>
Hi,
On Wed, Sep 15, 2010 at 05:53:10AM -0500, Ming Lei wrote:
>1), why is the check for "is_dma" needed here?
>
> if (is_dma || request->actual == request->length) {
> ....
> }
if you programmed dma to request->length (and assuming it worked just
fine) mode1 will only interrupt you when the entire request has been
sent.
>2), why is a zlp needed in the case below?
>
> #ifdef CONFIG_USB_INVENTRA_DMA
> || (is_dma && (!dma->desired_mode ||
> (request->actual & (musb_ep->packet_sz - 1))))
> #endif
in that case, it's not a zlp, it's short packet. Inventra will *NOT*
transfer short packets, you need to set txpktrdy by hand to get it
transfered.
>IMO, it is not difficult to give a good fix for the ZLP problem
>if the two questions are clear.
true, but some re-work needs to be done.
--
balbi
next prev parent reply other threads:[~2010-09-15 10:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 10:53 Ming Lei
2010-09-15 10:56 ` Felipe Balbi [this message]
2010-09-15 11:02 ` Ming Lei
2010-09-15 11:07 ` Felipe Balbi
2010-09-15 13:10 ` Sergei Shtylyov
2010-09-16 6:05 ` Felipe Balbi
2010-09-16 6:15 ` Gadiyar, Anand
2010-09-16 6:22 ` Felipe Balbi
2010-09-16 6:54 ` Ming Lei
2010-09-16 11:03 ` Sergei Shtylyov
2010-09-15 11:14 ` Ming Lei
2010-09-15 13:06 ` Sergei Shtylyov
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=20100915105641.GO3393@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=dbrownell@users.sourceforge.net \
--cc=gadiyar@ti.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sshtylyov@mvista.com \
--cc=tom.leiming@gmail.com \
--cc=vapier@gentoo.org \
/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®