On Wed, Aug 28, 2013 at 12:13:51AM +0200, Heiko Stübner wrote:
> This adds a new driver to support the s3c24xx dma using the dmaengine
> and makes the old one in mach-s3c24xx obsolete in the long run.
> 
> Conceptually the s3c24xx-dma feels like a distant relative of the pl08x
> with numerous virtual channels being mapped to a lot less physical ones.
> The driver therefore borrows a lot from the amba-pl08x driver in this
> regard. Functionality-wise the driver gains a memcpy ability in addition
> to the slave_sg one.
> 
> The driver supports both the method for requesting the peripheral used
> by SoCs before the S3C2443 and the different method for S3C2443 and later.
> 
> On earlier SoCs the hardware channels usable for specific peripherals is
> constrainted while on later SoCs all channels can be used for any peripheral.
> 
> Tested on a s3c2416-based board, memcpy using the dmatest module and
> slave_sg partially using the spi-s3c64xx driver.
> 

> +static int s3c24xx_dma_control(struct dma_chan *chan, enum dma_ctrl_cmd cmd,
> +                      unsigned long arg)
> +{
> +     struct s3c24xx_dma_chan *s3cchan = to_s3c24xx_dma_chan(chan);
> +     struct s3c24xx_dma_engine *s3cdma = s3cchan->host;
> +     unsigned long flags;
> +     int ret = 0;
> +
> +     /* Controls applicable to inactive channels */
> +     if (cmd == DMA_SLAVE_CONFIG)
> +             return s3c24xx_dma_set_runtime_config(s3cchan,
> +                                           (struct dma_slave_config *)arg);
> +
> +     /*
> +      * Anything succeeds on channels with no physical allocation and
> +      * no queued transfers.
> +      */
> +     spin_lock_irqsave(&s3cchan->vc.lock, flags);
> +     if (!s3cchan->phy && !s3cchan->at) {
> +             spin_unlock_irqrestore(&s3cchan->vc.lock, flags);
> +             return 0;
this can be bad cmd or terminating already closed channel, return 0 doesnt make
sense
> +     }
> +
> +     switch (cmd) {
> +     case DMA_TERMINATE_ALL:
why not DMA_SLAVE_CONFIG in this switch to make it look simpler...


> +static enum dma_status s3c24xx_dma_tx_status(struct dma_chan *chan,
> +             dma_cookie_t cookie, struct dma_tx_state *txstate)
> +{
> +     struct s3c24xx_dma_chan *s3cchan = to_s3c24xx_dma_chan(chan);
> +     struct virt_dma_desc *vd;
> +     unsigned long flags;
> +     enum dma_status ret;
> +     size_t bytes = 0;
> +
> +     ret = dma_cookie_status(chan, cookie, txstate);
> +     if (ret == DMA_SUCCESS)
> +             return ret;
> +
> +     /*
> +      * There's no point calculating the residue if there's
> +      * no txstate to store the value.
> +      */
> +     if (!txstate)
> +             return ret;
> +
> +     spin_lock_irqsave(&s3cchan->vc.lock, flags);
> +     ret = dma_cookie_status(chan, cookie, txstate);
you are checking the cookie status twice, if you check txstate (which should be
valid anyways), then you avoid the duplication

> +     if (ret != DMA_SUCCESS) {
> +             struct s3c24xx_txd *txd;
> +             struct s3c24xx_sg *dsg;
> +
> +             vd = vchan_find_desc(&s3cchan->vc, cookie);
> +             if (vd) {
> +                     /* On the issued list, so hasn't been processed yet */
> +                     txd = to_s3c24xx_txd(&vd->tx);
> +
> +                     list_for_each_entry(dsg, &txd->dsg_list, node)
> +                             bytes += dsg->len;
> +             } else {
> +                     /*
> +                      * Currently running, so sum over the pending sg's and
> +                      * the currently active one.
> +                      */
> +                     txd = s3cchan->at;
> +
> +                     dsg = list_entry(txd->at, struct s3c24xx_sg, node);
> +                     list_for_each_entry_from(dsg, &txd->dsg_list, node);
> +                             bytes += dsg->len;
> +
> +                     bytes += s3c24xx_dma_getbytes_chan(s3cchan);
> +             }
> +     }
> +     spin_unlock_irqrestore(&s3cchan->vc.lock, flags);
> +
> +     /*
> +      * This cookie not complete yet
> +      * Get number of bytes left in the active transactions and queue
> +      */
> +     dma_set_residue(txstate, bytes);
> +
> +     /* Whether waiting or running, we're in progress */
> +     return ret;
> +}
> +
> +/*
> + * Initialize a descriptor to be used by memcpy submit
> + */
> +static struct dma_async_tx_descriptor *s3c24xx_dma_prep_memcpy(
> +             struct dma_chan *chan, dma_addr_t dest, dma_addr_t src,
> +             size_t len, unsigned long flags)
> +{
> +     struct s3c24xx_dma_chan *s3cchan = to_s3c24xx_dma_chan(chan);
> +     struct s3c24xx_dma_engine *s3cdma = s3cchan->host;
> +     struct s3c24xx_txd *txd;
> +     struct s3c24xx_sg *dsg;
> +
> +     dev_dbg(&s3cdma->pdev->dev, "prepare memcpy of %d bytes from %s\n",
> +                     len, s3cchan->name);
> +
> +     if ((len & S3C24XX_DCON_TC_MASK) != len) {
> +             dev_err(&s3cdma->pdev->dev, "memcpy size %d to large\n", len);
> +             return NULL;
> +     }
> +
> +     txd = s3c24xx_dma_get_txd();
> +     if (!txd)
> +             return NULL;
> +
> +     dsg = kzalloc(sizeof(struct s3c24xx_sg), GFP_NOWAIT);
sizeof(*dsg)

~Vinod
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to