summaryrefslogtreecommitdiffstats
path: root/target/linux/mvebu/patches-3.8/003-dma_mv_xor_fix_error_handling_clocks.patch
diff options
context:
space:
mode:
Diffstat (limited to 'target/linux/mvebu/patches-3.8/003-dma_mv_xor_fix_error_handling_clocks.patch')
-rw-r--r--target/linux/mvebu/patches-3.8/003-dma_mv_xor_fix_error_handling_clocks.patch35
1 files changed, 0 insertions, 35 deletions
diff --git a/target/linux/mvebu/patches-3.8/003-dma_mv_xor_fix_error_handling_clocks.patch b/target/linux/mvebu/patches-3.8/003-dma_mv_xor_fix_error_handling_clocks.patch
deleted file mode 100644
index 9bee8acde..000000000
--- a/target/linux/mvebu/patches-3.8/003-dma_mv_xor_fix_error_handling_clocks.patch
+++ /dev/null
@@ -1,35 +0,0 @@
-From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
-When a channel fails to initialize, we release all ressources,
-including clocks. However, a XOR unit is not necessarily associated to
-a clock (some variants of Marvell SoCs have a clock for XOR units,
-some don't), so we shouldn't unconditionally be releasing the clock.
-
-Instead, just like we do in the mv_xor_remove() function, we should
-check if one clock was found before releasing it.
-
-Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
----
- drivers/dma/mv_xor.c | 7 +++++--
- 1 file changed, 5 insertions(+), 2 deletions(-)
-
-diff --git a/drivers/dma/mv_xor.c b/drivers/dma/mv_xor.c
-index cc5d23d..e17fad0 100644
---- a/drivers/dma/mv_xor.c
-+++ b/drivers/dma/mv_xor.c
-@@ -1366,8 +1366,11 @@ err_channel_add:
- irq_dispose_mapping(xordev->channels[i]->irq);
- }
-
-- clk_disable_unprepare(xordev->clk);
-- clk_put(xordev->clk);
-+ if (!IS_ERR(xordev->clk)) {
-+ clk_disable_unprepare(xordev->clk);
-+ clk_put(xordev->clk);
-+ }
-+
- return ret;
- }
-
---
-1.7.10.4