diff options
| author | Ezequiel Garcia <[email protected]> | 2013-12-10 09:57:15 -0300 |
|---|---|---|
| committer | Brian Norris <[email protected]> | 2013-12-12 15:02:04 -0800 |
| commit | 15b540c71cac840f0a3e8b1b4b7a773deb847ffb (patch) | |
| tree | 36633b7abe131264da0ca4826351a58e988998b8 /tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace | |
| parent | 9c59ac616137fb62f6cb3f1219201b09cbcf30be (diff) | |
mtd: nand: pxa3xx: Use info->use_dma to release DMA resources
In commit:
commit 62e8b851783138a11da63285be0fbf69530ff73d
Author: Ezequiel Garcia <[email protected]>
Date: Fri Oct 4 15:30:38 2013 -0300
mtd: nand: pxa3xx: Allocate data buffer on detected flash size
the way the buffer is allocated was changed: the first READ_ID is issued
with a small kmalloc'ed buffer. Only once the flash page size is detected
the DMA buffers are allocated, and info->use_dma is set.
Currently, if the device detection fails, the driver checks the 'use_dma'
module parameter and tries to release unallocated DMA resources.
Fix this by checking the proper indicator of the DMA allocation, which
is 'info->use_dma'.
Signed-off-by: Ezequiel Garcia <[email protected]>
Signed-off-by: Brian Norris <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace')
0 files changed, 0 insertions, 0 deletions