RFC Migrate more OMAP DMA code to DMA engine
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest0 of 26 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 26 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH RFC 00/26] Migrate more OMAP DMA code to DMA engine
Quoted 3 lines · Russell King - ARM Linux
The following patch series moves code to setup the DMA hardware and service interrupts from the hardware to the DMA engine driver. This reduces the dependency on the legacy DMA implementation.
Didnt the code getting removed from legacy, are there any users still of the legacy driver in mainline?
--
~Vinod
Quoted 20 lines
This series does not remove the channel allocation/freeing hooks which are used to manage the allocation of physical channels - this is the next step in the evolution.
The patches which move the interrupt handling are currently less than perfect since they're writing to
ENABLE_L0under a different spinlock, and hence RFC only at the moment.arch/arm/mach-omap1/dma.c | 183 +++++-------- arch/arm/mach-omap2/dma.c | 183 ++++++-------- arch/arm/plat-omap/dma.c | 17 +- drivers/dma/omap-dma.c | 653 ++++++++++++++++++++++++++++++++++++++++----- include/linux/omap-dma.h | 25 ++- 5 files changed, 774 insertions(+), 287 deletions(-)Signature · 3 lines
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad. Estimate before purchase was "up to 13.2Mbit".