[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100511150557.GY30801@buzzloop.caiaq.de>
Date: Tue, 11 May 2010 17:05:57 +0200
From: Daniel Mack <daniel@...aq.de>
To: Alan Stern <stern@...land.harvard.edu>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
USB list <linux-usb@...r.kernel.org>, tiwai@...e.de,
gregkh@...e.de, clemens@...isch.de,
Kernel development list <linux-kernel@...r.kernel.org>,
chrisw@...s-sol.org, iommu@...ts.linux-foundation.org,
andi@...stfloor.org, pedrib@...il.com,
Andrew Morton <akpm@...ux-foundation.org>, dwmw2@...radead.org
Subject: Re: [alsa-devel] USB transfer_buffer allocations on 64bit systems
On Tue, May 11, 2010 at 10:57:07AM -0400, Alan Stern wrote:
> There are no calls to any dma_sync_* routines. Daniel will have to
> check me on this, but I believe that urb->transfer_buffer is filled
> before dma_map_single() is called and it isn't touched again until
> after dma_unmap_single() (which occurs before urb's completion handler
> is called).
Yes, that's correct. Sorry fot the misleading information I gave. The
code doesn't to any weird tricks as it currently stands. It fills the
buffer, submits the URB and doesn't touch the buffer contents
afterwards.
Daniel
--
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