summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRobin Murphy <robin.murphy@arm.com>2019-07-03 14:47:31 +0100
committerRob Herring <robh@kernel.org>2019-10-08 13:50:22 -0500
commitc60bf3eb888a362100aa1bdbea351dab681e262a (patch)
tree9feec3299a80bbbe7d83b2d668b303b9f8aabd59
parent862ab5578f754117742c8b8c8e5ddf98bdb190ba (diff)
downloadlinux-c60bf3eb888a362100aa1bdbea351dab681e262a.tar.bz2
of: address: Follow DMA parent for "dma-coherent"
Much like for address translation, when checking for DMA coherence we should be sure to walk up the DMA hierarchy, rather than the MMIO one, now that we can accommodate them being different. Signed-off-by: Robin Murphy <robin.murphy@arm.com> Tested-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de> Reviewed-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de> Signed-off-by: Rob Herring <robh@kernel.org>
-rw-r--r--drivers/of/address.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/of/address.c b/drivers/of/address.c
index e9188c82fdae..3fd34f7ad772 100644
--- a/drivers/of/address.c
+++ b/drivers/of/address.c
@@ -999,7 +999,7 @@ bool of_dma_is_coherent(struct device_node *np)
of_node_put(node);
return true;
}
- node = of_get_next_parent(node);
+ node = of_get_next_dma_parent(node);
}
of_node_put(node);
return false;