On 11/8/20 10:18 PM, Leizhen (ThunderTown) wrote:
> Hi, everybody:
>   How do we deal with this problem? I updated the kernel to the latest and 
> the problem still persists.
> 
>   make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j24 dtbs 2>err.txt
>   vim err.txt
> 
> arch/arm64/boot/dts/qcom/ipq6018.dtsi:185.3-14: Warning (dma_ranges_format): 
> /soc:dma-ranges: empty "dma-ranges" property but its #address-cells (1) 
> differs from / (2)
> arch/arm64/boot/dts/qcom/ipq6018.dtsi:185.3-14: Warning (dma_ranges_format): 
> /soc:dma-ranges: empty "dma-ranges" property but its #size-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 
> #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)
> 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)
> 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)

I was hoping that Ray or Scott could give this a try, and TBH, I am
still not a big fan of having to mangle the 'reg' property to be
compatible with #address-cells = <2> and #size-cells = <2>, I would have
preferred omitting the 'dma-ranges' property entirely.

We have plenty of time to get this patch applied for v5.11.
-- 
Florian

Reply via email to