diff options
| author | Andy Shevchenko <andriy.shevchenko@linux.intel.com> | 2016-04-26 12:03:04 +0300 |
|---|---|---|
| committer | Tejun Heo <tj@kernel.org> | 2016-05-10 12:29:18 -0400 |
| commit | 6689dfac00ef3118f88d5b06e1f1d13899b79997 (patch) | |
| tree | 52d6622bc3145f61585513fe6f24736e8ba5e077 /README | |
| parent | a7e6de544c5c238a06935c96d27151432c94d2e6 (diff) | |
| download | linux-6689dfac00ef3118f88d5b06e1f1d13899b79997.tar.gz linux-6689dfac00ef3118f88d5b06e1f1d13899b79997.tar.bz2 linux-6689dfac00ef3118f88d5b06e1f1d13899b79997.zip | |
ata: sata_dwc_460ex: set dma_boundary to 0x1fff
The original code states:
Make sure a LLI block is not created that will span 8K max FIS
boundary. If the block spans such a FIS boundary, there is a chance
that a DMA burst will cross that boundary -- this results in an error
in the host controller.
Since we have switched to generic DMAengine API we satisfy above by setting
dma_boundary value to 0x1fff.
Suggested-by: Mans Rullgard <mans@mansr.com>
Tested-by: Christian Lamparter <chunkeey@googlemail.com>
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions