diff options
| author | Zhen Lei <[email protected]> | 2020-10-16 09:08:32 +0000 |
|---|---|---|
| committer | Arnd Bergmann <[email protected]> | 2020-11-17 14:08:43 +0000 |
| commit | 2013a4b684b6eb614ee5c9a3c07b0ae6f5ca96d9 (patch) | |
| tree | 424e0d0dc3cd16b9e268cb6d7029e1abd8abf7fa /fs/jbd2/commit.c | |
| parent | Linux 5.10-rc3 (diff) | |
| download | kernel-2013a4b684b6eb614ee5c9a3c07b0ae6f5ca96d9.tar.gz kernel-2013a4b684b6eb614ee5c9a3c07b0ae6f5ca96d9.zip | |
arm64: dts: broadcom: clear the warnings caused by empty dma-ranges
The scripts/dtc/checks.c requires that the node have empty "dma-ranges"
property must have the same "#address-cells" and "#size-cells" values as
the parent node. Otherwise, the following warnings is reported:
arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning \
(dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but \
its #address-cells (1) differs from / (2)
arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning \
(dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but \
its #size-cells (1) differs from / (2)
Arnd Bergmann figured out why it's necessary:
Also note that the #address-cells=<1> means that any device under
this bus is assumed to only support 32-bit addressing, and DMA will
have to go through a slow swiotlb in the absence of an IOMMU.
Suggested-by: Arnd Bergmann <[email protected]>
Signed-off-by: Zhen Lei <[email protected]>
Link: https://lore.kernel.org/r/[email protected]'
Acked-by: Florian Fainelli <[email protected]>
Signed-off-by: Arnd Bergmann <[email protected]>
Diffstat (limited to 'fs/jbd2/commit.c')
0 files changed, 0 insertions, 0 deletions