Hi Vinod,
Thanks for the review...
>
> On Wed, Jun 08, 2016 at 07:40:52AM +0000, Appana Durga Kedareswara Rao
> wrote:
> > > > +static void zynqmp_dma_desc_config_eod(struct zynqmp_dma_chan
> > > > +*chan, void *desc)
> > >
> > > eod? 80 line?
>
> What's eod?
End of descriptor...
>
> > > > +int zynqmp_dma_channel_set_config(struct dma_chan *dchan,
> > > > + struct zynqmp_dma_config *cfg) {
> > > > + struct zynqmp_dma_chan *chan = to_chan(dchan);
> > > > +
> > > > + chan->config.ovrfetch = cfg->ovrfetch;
> > > > + chan->config.has_sg = cfg->has_sg;
> > >
> > > is this HW capability? if so why would anyone not like to use it!
> >
> > Yes it is HW capability. It can be either in simple mode or SG mode
> > Earlier In the driver this configuration is read from the device-tree
> > But as per lars and your suggestion moved it as runtime config parameters.
>
> If sg mode is available why would anyone _not_ want it?
>
> I do not think there is point to have this
You mean always keep the device in SG mode and provide an option
For simple dma mode if user want to use simple DMA mode??
There are few features that are available in the simple DMA mode won't
Available in SG mode like write only DMA , read only DMA mode etc...
>
> >
> > >
> > > > + chan->config.ratectrl = cfg->ratectrl;
> > > > + chan->config.src_issue = cfg->src_issue;
> > > > + chan->config.src_burst_len = cfg->src_burst_len;
> > > > + chan->config.dst_burst_len = cfg->dst_burst_len;
> > >
> > > can you describe these parameters?
> > ratectl:
> > Rate control can be independently enabled per channel. When rate
> > control is enabled, the DMA channel uses the rate control count to schedule
> successive data read transactions.
>
> And how is this used by client?
When rate control is enabled, ZDMA channel uses the rate control count
To schedule successive data read transactions I mean kind of flow control to schedule
Transactions at fixed intervals instead of pumping the transfers without delay or whenever bus is available
Rate control count register definition (11:0):
Scheduling interval for SRC AXI transaction, only used if rate control is enabled
>
> > src_issue:
> > Tells outstanding transaction on SRC.
>
> This should be read only then, right?
It is a Read/Write register
http://www.xilinx.com/html_docs/registers/ug1087/ug1087-zynq-ultrascale-registers.html
By default it is configured for Max transactions.
If user want to limit it they can limit it using this config option.
>
> > Burst_len:
> > Configures the burst length of the src and dst transfers...
>
> Hmmm, but you are on memcpy, so that should be programmed for throughput?
Yes...
>
> > >
> > > How would a client know how to configure them?
> >
> > With the default values of the config parameters driver will work.
>
> But how will client know what is default!
Default values means IP default state after reset.
If user not aware of the above parameters also still the driver will work for basic functionality.
Do you want me to implement one more API get_config so that
Whenever user will call the get_config he will know the default values
Of the config parameters?
>
> > If user has specific requirement to change these parameters they can
> > pass It to the driver using set_config API and all these parameters
> > are Documented in the include/linux/dma/xilinx_dma.h file...
>
> Can you give me an example where user would like to do that
I am using customized dma test client.
There I am calling this set_config API before triggering memcpy/SG operations.
Regards,
Kedar.
>
> --
> ~Vinod
> --
> To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body
> of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at
> http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
