lkml.org 
[lkml]   [2016]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: [PATCH v7 1/2] Documentation: DT: dma: Add Xilinx zynqmp dma device tree binding documentation
Date

Hi Vinod,

>
> PLEASE strip the crap from your MUA, better use a linux MUA

OK will fix Sorry for the noise...

>
>
> > >>>>> +- 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,src-burst-len : AXI length for data read. Support only power
> of
> > >>>>> + 2 byte values.
> > >>>>> +- xlnx,dst-burst-len : AXI length for data write. Support only power
> of
> > >>>>
> > >>>> These are all software runtime configuration parameters that you'd
> > >>>> want to change at runtime depending on which peripheral you are
> > >>>> targeting with a specific DMA transfer. These really do not belong into

> > Sorry, but that is just as broken. You need to derive those parameters from
> > the DMA transfer as they are transfer specific.
>
> Right, for memcpy you should derive the parameters. Frankly burst size
> and lengths, rate control should be set to maximun to achives best
> performance on mecpy. People want memcpy to be done asap

Ok Will fix in the next version of the patch...

Regards,
Kedar.

\
 
 \ /
  Last update: 2016-05-03 11:41    [W:0.067 / U:0.036 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site