[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100915110745.GP3393@legolas.emea.dhcp.ti.com>
Date: Wed, 15 Sep 2010 14:07:45 +0300
From: Felipe Balbi <balbi@...com>
To: Ming Lei <tom.leiming@...il.com>
Cc: "Balbi, Felipe" <balbi@...com>,
Sergei Shtylyov <sshtylyov@...sta.com>,
"greg@...ah.com" <greg@...ah.com>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
David Brownell <dbrownell@...rs.sourceforge.net>,
"Gadiyar, Anand" <gadiyar@...com>,
Mike Frysinger <vapier@...too.org>
Subject: Re: [Discussion] USB: musb-gadget: how to fix ZLP issue in
musb_g_tx
Hi,
On Wed, Sep 15, 2010 at 06:02:22AM -0500, Ming Lei wrote:
>If so, once the dma interrupt comes, will request->actual be same
>with request->length in musb_g_tx? And if it is true, could we remove the
>check for 'is_dma'?
see that is_dma is set to true by just checking if dma in enabled in
txcsr, it might be that dma didn't complete everything and you need to
write txpktrdy by hand to send last short packet. So to remove that you
would need to re-work a bit more code.
You need to know when this is a dma IRQ or an endpoint IRQ.
--
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists