diff options
author | Ard Biesheuvel <ard.biesheuvel@linaro.org> | 2020-02-21 17:29:04 +0100 |
---|---|---|
committer | Ard Biesheuvel <ard.biesheuvel@linaro.org> | 2020-03-06 17:41:38 +0100 |
commit | f9d42079600cda00e55a88f2baced584f1b95211 (patch) | |
tree | b9cd415b39aa13ea831025633e68966479412112 | |
parent | 28d2f4ecd87da769f8ab4328d047c6a7aae69b67 (diff) |
Platform/DeveloperBox: drop dma-ranges property from DT root node
The dma-ranges DT property describes the DMA translation between a
parent bus and its children, and so having a dma-ranges property in
the root node makes little sense, but it doesn't harm either.
However, recent kernels (v5.5+) have started spewing warnings into
the kernel log of the following nature:
OF: translation of DMA address(0) to CPU address failed node(/uart@2a400000)
OF: translation of DMA address(0) to CPU address failed node(/pmu)
OF: translation of DMA address(0) to CPU address failed node(/pcie@60000000)
OF: translation of DMA address(0) to CPU address failed node(/pcie@60000000)
OF: translation of DMA address(0) to CPU address failed node(/pcie@60000000)
OF: translation of DMA address(0) to CPU address failed node(/pcie@60000000)
OF: translation of DMA address(0) to CPU address failed node(/pcie@60000000)
OF: translation of DMA address(0) to CPU address failed node(/pcie@60000000)
OF: translation of DMA address(0) to CPU address failed node(/pcie@70000000)
OF: translation of DMA address(0) to CPU address failed node(/uart@51040000)
OF: translation of DMA address(0) to CPU address failed node(/gpio@51000000)
OF: translation of DMA address(0) to CPU address failed node(/i2c@51210000)
OF: translation of DMA address(0) to CPU address failed node(/gpio-keys)
OF: translation of DMA address(0) to CPU address failed node(/tpm_tis@10000000)
OF: translation of DMA address(0) to CPU address failed node(/sdhci@52300000)
OF: translation of DMA address(0) to CPU address failed node(/ethernet@522d0000)
OF: translation of DMA address(0) to CPU address failed node(/pcie@60000000)
OF: translation of DMA address(0) to CPU address failed node(/pcie@60000000)
and so we should probably get rid of this bogus dma-ranges property.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Reviewed-by: Leif Lindholm <leif@nuviainc.com>
-rw-r--r-- | Silicon/Socionext/SynQuacer/DeviceTree/SynQuacer.dtsi | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/Silicon/Socionext/SynQuacer/DeviceTree/SynQuacer.dtsi b/Silicon/Socionext/SynQuacer/DeviceTree/SynQuacer.dtsi index f124a223..b11e4303 100644 --- a/Silicon/Socionext/SynQuacer/DeviceTree/SynQuacer.dtsi +++ b/Silicon/Socionext/SynQuacer/DeviceTree/SynQuacer.dtsi @@ -21,7 +21,6 @@ #address-cells = <2>;
#size-cells = <2>;
interrupt-parent = <&gic>;
- dma-ranges = <0x0 0x0 0x0 0x0 0x100 0x0>;
aliases {
serial0 = &soc_uart0;
|