cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
franzforstmayr
Contributor
Contributor
405 Views
Registered: ‎09-20-2017

device-tree-xlnx fails to generate axi_dma node

When i use DMA IP in vivado in asynchronous mode (two different clocks for ps side and stream side) the devicetree generator delivers strange results for axi_dma devicetree node.

axi_dma_0: dma@a0040000 {

            #dma-cells = <1>;
            clock-names = "s_axi_lite_aclk", "m_axi_sg_aclk", "m_axi_mm2s_aclk", "m_axi_s2mm_aclk";
            clocks = <&misc_clk_0>,>, <&<&misc_clk_0>;
            compatible = "xlnx,axi-dma-1.00.a";
            interrupt-names = "mm2s_introut", "s2mm_introut";
            interrupt-parent = <&gic>;
            interrupts = <0 90 4 0 91 4>;
            reg = <0x0 0xa0040000 0x0 0x1000>;
            xlnx,addrwidth = <0x40>;
            xlnx,include-sg ;
            xlnx,sg-length-width = <0x12>;
            dma-channel@a0040000 {
                compatible = "xlnx,axi-dma-mm2s-channel";
                dma-channels = <0x1>;
                interrupts = <0 90 4>;
                xlnx,datawidth = <0x100>;
                xlnx,device-id = <0x0>;
            };
            dma-channel@a0040030 {
                compatible = "xlnx,axi-dma-s2mm-channel";
                dma-channels = <0x1>;
                interrupts = <0 91 4>;
                xlnx,datawidth = <0x100>;
                xlnx,device-id = <0x0>;
            };
        };
 
The complier is obviously failing when parsing the clocks property.
I thought that this patch
would fix this, but it doesn't work either. Is there any other solution?
(I'm using vivado 2018.2 right now)
Tags (2)
0 Kudos
0 Replies