07 Jan, 2009
2 commits
-
Use the general-purpose channel allocation provided by dmaengine.
Reviewed-by: Andrew Morton
Signed-off-by: Dan Williams -
Simply, if a client wants any dmaengine channel then prevent all dmaengine
modules from being removed. Once the clients are done re-enable module
removal.Why?, beyond reducing complication:
1/ Tracking reference counts per-transaction in an efficient manner, as
is currently done, requires a complicated scheme to avoid cache-line
bouncing effects.
2/ Per-transaction ref-counting gives the false impression that a
dma-driver can be gracefully removed ahead of its user (net, md, or
dma-slave)
3/ None of the in-tree dma-drivers talk to hot pluggable hardware, but
if such an engine were built one day we still would not need to notify
clients of remove events. The driver can simply return NULL to a
->prep() request, something that is much easier for a client to handle.Reviewed-by: Andrew Morton
Acked-by: Maciej Sosnowski
Signed-off-by: Dan Williams
04 Oct, 2006
1 commit
-
kbuild explicitly includes this at build time.
Signed-off-by: Dave Jones
03 Aug, 2006
1 commit
-
Signed-off-by: Alexey Dobriyan
Signed-off-by: Andrew Morton
Signed-off-by: David S. Miller
22 Jul, 2006
1 commit
-
Every file should #include the headers containing the prototypes for
its global functions.Especially in cases like this one where gcc can tell us through a
compile error that the prototype was wrong...Signed-off-by: Adrian Bunk
Signed-off-by: David S. Miller
18 Jun, 2006
2 commits
-
Provides for pinning user space pages in memory, copying to iovecs,
and copying from sk_buffs including fragmented and chained sk_buffs.Signed-off-by: Chris Leech
Signed-off-by: David S. Miller -
Attempts to allocate per-CPU DMA channels
Signed-off-by: Chris Leech
Signed-off-by: David S. Miller
