From: punnaia@xilinx.com (punnaiah choudary kalluri)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/2] Documentation: dt: Add Xilinx zynqmp dma device tree binding documentation
Date: Mon, 31 Aug 2015 09:07:00 +0530 [thread overview]
Message-ID: <CAGnW=Ba4PjsEXaxeSPNRgLCNBX02BwnxAfxrRQEwighpC9NOjg@mail.gmail.com> (raw)
In-Reply-To: <CAGnW=BbS0V-avm+oV-V5J0995YUXwP9v0uZFwc4i9587u1SDTg@mail.gmail.com>
On Tue, Aug 25, 2015 at 12:16 PM, punnaiah choudary kalluri
<punnaia@xilinx.com> wrote:
> Hi Rob,
>
> On Tue, Aug 25, 2015 at 12:23 AM, Rob Herring <robherring2@gmail.com> wrote:
>> On Wed, Aug 5, 2015 at 10:19 PM, Punnaiah Choudary Kalluri
>> <punnaiah.choudary.kalluri@xilinx.com> wrote:
>>> Device-tree binding documentation for Xilinx zynqmp dma engine used in
>>> Zynq UltraScale+ MPSoC.
>>>
>>> Signed-off-by: Punnaiah Choudary Kalluri <punnaia@xilinx.com>
>>> ---
>>> Changes in v4:
>>> - None
>>> Changes in v3:
>>> - None
>>> Changes in v2:
>>> - None
>>> ---
>>> .../devicetree/bindings/dma/xilinx/zynqmp_dma.txt | 61 ++++++++++++++++++++
>>> 1 files changed, 61 insertions(+), 0 deletions(-)
>>> create mode 100644 Documentation/devicetree/bindings/dma/xilinx/zynqmp_dma.txt
>>>
>>> diff --git a/Documentation/devicetree/bindings/dma/xilinx/zynqmp_dma.txt b/Documentation/devicetree/bindings/dma/xilinx/zynqmp_dma.txt
>>> new file mode 100644
>>> index 0000000..e4f92b9
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/dma/xilinx/zynqmp_dma.txt
>>> @@ -0,0 +1,61 @@
>>> +Xilinx ZynqMP DMA engine, it does support memory to memory transfers,
>>> +memory to device and device to memory transfers. It also has flow
>>> +control and rate control support for slave/peripheral dma access.
>>> +
>>> +Required properties:
>>> +- compatible: Should be "xlnx,zynqmp-dma-1.0"
>>> +- #dma-cells: Should be <1>, a single cell holding a line request number
>>> +- reg: Memory map for module access
>>> +- interrupt-parent: Interrupt controller the interrupt is routed through
>>> +- interrupts: Should contain DMA channel interrupt
>>> +- xlnx,bus-width: AXI buswidth in bits. Should contain 128 or 64
>>> +
>>> +Optional properties:
>>> +- xlnx,include-sg: Indicates the controller to operate in simple or scatter
>>> + gather dma mode
>>> +- xlnx,ratectrl: Scheduling interval in terms of clock cycles for
>>> + source AXI transaction
>>> +- xlnx,overfetch: Tells whether the channel is allowed to over fetch the data
>>> +- xlnx,src-issue: Number of AXI outstanding transactions on source side
>>> +- xlnx,desc-axi-cohrnt: Tells whether the AXI transactions generated for the
>>> + descriptor read are marked Non-coherent
>>> +- xlnx,src-axi-cohrnt: Tells whether the AXI transactions generated for the
>>> + source descriptor payload are marked Non-coherent
>>> +- xlnx,dst-axi-cohrnt: Tells whether the AXI transactions generated for the
>>> + dst descriptor payload are marked Non-coherent
>>
>> Do you really need 3? dma-coherent property doesn't work for you?
>>
>> Not that it should dictate the binding, but the kernel doesn't support
>> a device needing both coherent and non-coherent DMA ops.
>
> I will get back to you shortly on this
Yes. dma-coherent property works. I will modify the bindings.
Thanks,
Punnaiah
>
>>
>>> +- xlnx,desc-axi-qos: AXI QOS bits to be used for descriptor fetch
>>> +- xlnx,src-axi-qos: AXI QOS bits to be used for data read
>>> +- xlnx,dst-axi-qos: AXI QOS bits to be used for data write
>>> +- xlnx,desc-axi-cache: AXI cache bits to be used for descriptor fetch.
>>> +- xlnx,desc-axi-cache: AXI cache bits to be used for data read
>>> +- xlnx,desc-axi-cache: AXI cache bits to be used for data write
>>
>> These signals are generally part of the coherent or not setting. This
>> allows for potentially invalid combinations.
>>
>> Plus you have a copy/paste error.
>
> I will fix this.
>
> Thanks,
> Punnaiah
>>
>>> +- xlnx,src-burst-len: AXI length for data read. Support only power of 2 values
>>> + i.e 1,2,4,8 and 16
>>> +- xlnx,dst-burst-len: AXI length for data write. Support only power of 2 values
>>> + i.e 1,2,4,8 and 16
>>> +
>>> +Example:
>>> +++++++++
>>> +fpd_dma_chan1: dma at FD500000 {
>>> + compatible = "xlnx,zynqmp-dma-1.0";
>>> + reg = <0x0 0xFD500000 0x1000>;
>>> + #dma_cells = <1>;
>>> + interrupt-parent = <&gic>;
>>> + interrupts = <0 117 4>;
>>> + xlnx,bus-width = <128>;
>>> + xlnx,include-sg;
>>> + xlnx,overfetch;
>>> + xlnx,ratectrl = <0>;
>>> + xlnx,src-issue = <16>;
>>> + xlnx,desc-axi-cohrnt;
>>> + xlnx,src-axi-cohrnt;
>>> + xlnx,dst-axi-cohrnt;
>>> + xlnx,desc-axi-qos = <0>;
>>> + xlnx,desc-axi-cache = <0>;
>>> + xlnx,src-axi-qos = <0>;
>>> + xlnx,src-axi-cache = <2>;
>>> + xlnx,dst-axi-qos = <0>;
>>> + xlnx,dst-axi-cache = <2>;
>>> + xlnx,src-burst-len = <4>;
>>> + xlnx,dst-burst-len = <4>;
>>> +};
>>> --
>>> 1.7.4
>>>
>>>
>>> _______________________________________________
>>> linux-arm-kernel mailing list
>>> linux-arm-kernel at lists.infradead.org
>>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2015-08-31 3:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 3:19 [PATCH v4 1/2] Documentation: dt: Add Xilinx zynqmp dma device tree binding documentation Punnaiah Choudary Kalluri
2015-08-06 3:19 ` [PATCH v4 2/2] dma: Add Xilinx zynqmp dma engine driver support Punnaiah Choudary Kalluri
2015-08-20 6:13 ` Vinod Koul
2015-08-20 6:31 ` punnaiah choudary kalluri
2015-08-23 14:08 ` Vinod Koul
2015-08-23 14:54 ` punnaiah choudary kalluri
2015-08-20 5:52 ` [PATCH v4 1/2] Documentation: dt: Add Xilinx zynqmp dma device tree binding documentation Vinod Koul
2015-08-20 6:11 ` punnaiah choudary kalluri
2015-08-20 6:18 ` Vinod Koul
2015-08-20 6:20 ` Michal Simek
2015-08-21 16:42 ` Moritz Fischer
2015-08-22 10:47 ` punnaiah choudary kalluri
2015-08-24 13:47 ` Lars-Peter Clausen
2015-08-24 18:39 ` punnaiah choudary kalluri
2015-08-24 18:53 ` Rob Herring
2015-08-25 6:46 ` punnaiah choudary kalluri
2015-08-31 3:37 ` punnaiah choudary kalluri [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGnW=Ba4PjsEXaxeSPNRgLCNBX02BwnxAfxrRQEwighpC9NOjg@mail.gmail.com' \
--to=punnaia@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).