Mack
Subject: [PATCH 2/2] usb: musb: cppi41: fire hrtimer according to
programmed channel length
The musb/cppi41 code installs a hrtimer to work around DMA completion
interrupts that have fired too early on AM335x hardware. This timer
is currently programmed to first fire 140
...@googlemail.com; linux-usb@vger.kernel.org; Daniel
Mack
Subject: [PATCH 2/2] usb: musb: cppi41: fire hrtimer according to
programmed channel length
The musb/cppi41 code installs a hrtimer to work around DMA completion
interrupts that have fired too early on AM335x hardware. This timer
is currently
...@linutronix.de
Cc: sebastian.reim...@googlemail.com; linux-usb@vger.kernel.org; Daniel
Mack
Subject: [PATCH 2/2] usb: musb: cppi41: fire hrtimer according to
programmed channel length
The musb/cppi41 code installs a hrtimer to work around DMA completion
interrupts that have fired
On 06/19/2014 05:53 PM, David Laight wrote:
From: Daniel Mack [mailto:dan...@zonque.org]
On 06/19/2014 05:07 PM, Felipe Balbi wrote:
On Wed, Jun 18, 2014 at 11:36:43AM +0200, Daniel Mack wrote:
On 06/18/2014 11:32 AM, David Laight wrote:
You can't really mean nanoseconds?
Microseconds of
The musb/cppi41 code installs a hrtimer to work around DMA completion
interrupts that have fired too early on AM335x hardware. This timer
is currently programmed to first fire 140 nanoseconds after the DMA
completion callback. According to the commit which introduced it
(a655f481d83, usb: musb:
From: Of Daniel Mack
Sent: 18 June 2014 10:28
To: ba...@ti.com; george.cher...@ti.com; bige...@linutronix.de
Cc: sebastian.reim...@googlemail.com; linux-usb@vger.kernel.org; Daniel Mack
Subject: [PATCH 2/2] usb: musb: cppi41: fire hrtimer according to programmed
channel length
The musb
On 06/18/2014 11:32 AM, David Laight wrote:
From: Of Daniel Mack
Sent: 18 June 2014 10:28
To: ba...@ti.com; george.cher...@ti.com; bige...@linutronix.de
Cc: sebastian.reim...@googlemail.com; linux-usb@vger.kernel.org; Daniel Mack
Subject: [PATCH 2/2] usb: musb: cppi41: fire hrtimer according