On Wed, Sep 03, 2014 at 12:17:43PM +0530, Srikanth Thokala wrote:
> Hi Vinod,
>
> Apologies for the delay.
>
> On Tue, Aug 19, 2014 at 10:33 PM, Vinod Koul <vinod.koul@xxxxxxxxx> wrote:
> > On Mon, Jul 28, 2014 at 05:47:49PM +0530, Srikanth Thokala wrote:
> >> +struct xilinx_dma_chan {
> >> + struct xilinx_dma_device *xdev;
> >> + u32 ctrl_offset;
> >> + spinlock_t lock;
> >> + struct list_head pending_list;
> >> + struct xilinx_dma_tx_descriptor *active_desc;
> >> + struct xilinx_dma_tx_descriptor *allocated_desc;
> >> + struct list_head done_list;
> >> + struct list_head free_seg_list;
> >> + struct dma_chan common;
> >> + struct xilinx_dma_tx_segment *seg_v;
> >> + dma_addr_t seg_p;
> >> + struct device *dev;
> >> + int irq;
> >> + int id;
> >> + enum dma_transfer_direction direction;
> > This looks suspect. Why should channel have direction, for a descriptor it
> > makes sense though.
>
> The channel only supports transfers in one direction. Either from memory to
> peripheral or from peripheral to memory, that's fixed and can't be changed
> at runtime. So, the driver needs to know which direction the channel supports
> and hence it can reject transfers with the wrong direction.
But you already have this information in descriptor so why duplicate?
> >> +/**
> >> + * xilinx_dma_channel_set_config - Configure DMA channel
> >> + * @dchan: DMA channel
> >> + * @cfg: DMA device configuration pointer
> >> + *
> >> + * Return: '0' on success and failure value on error
> >> + */
> >> +int xilinx_dma_channel_set_config(struct dma_chan *dchan,
> >> + struct xilinx_dma_config *cfg)
> >> +{
> >> + struct xilinx_dma_chan *chan = to_xilinx_chan(dchan);
> >> + u32 reg = dma_ctrl_read(chan, XILINX_DMA_REG_CONTROL);
> >> +
> >> + if (cfg->reset)
> >> + return xilinx_dma_reset(chan);
> >> +
> >> + if (cfg->coalesc <= XILINX_DMA_CR_COALESCE_MAX)
> >> + reg |= cfg->coalesc << XILINX_DMA_CR_COALESCE_SHIFT;
> >> +
> >> + if (cfg->delay <= XILINX_DMA_CR_DELAY_MAX)
> >> + reg |= cfg->delay << XILINX_DMA_CR_DELAY_SHIFT;
> >> +
> >> + dma_ctrl_write(chan, XILINX_DMA_REG_CONTROL, reg);
> > You aren't checking if a transaction is already running on this channel.
> > Also don't you need other slave parameters, I see you have removed the
> > dma_slave_config entirely
>
> All the parameters that are required for this DMA engine are provided by
> SG list, so I don't see the need of dma_slave_config. There are some
> specific IP parameters that are not part of dma_slave_config and these
> are being set by 'dma_channel_set_config' which is exported to slave
> drivers.
And that means you dont have any common parameters between dma_slave_config
right?
--
~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
