linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: 21cnbao@gmail.com (Barry Song)
To: linux-arm-kernel@lists.infradead.org
Subject: RFC: changing DMA slave configuration API
Date: Sun, 10 Jun 2012 19:19:47 +0800	[thread overview]
Message-ID: <CAGsJ_4xHNdEcfsmtypDHcJ0uyhtFz43xBojgHw2RSvrH8ohRcA@mail.gmail.com> (raw)
In-Reply-To: <20120610102023.GC11404@n2100.arm.linux.org.uk>

2012/6/10 Russell King - ARM Linux <linux@arm.linux.org.uk>:
> Dan, Vinod,
>
> There's a change I would like to do to the DMA slave configuration.
> It's currently a pain to have the source and destination parameters in
> the dma_slave_config structure as separate elements; it means when you
> want to extract them, you end up with code in DMA engine drivers like:
>
> + ? ? ? if (dir == DMA_DEV_TO_MEM) {
> + ? ? ? ? ? ? ? dev_addr = c->src_addr;
> + ? ? ? ? ? ? ? dev_width = c->src_addr_width;
> + ? ? ? ? ? ? ? burst = c->src_maxburst;
> + ? ? ? } else if (dir == DMA_MEM_TO_DEV) {
> + ? ? ? ? ? ? ? dev_addr = c->dst_addr;
> + ? ? ? ? ? ? ? dev_width = c->dst_addr_width;
> + ? ? ? ? ? ? ? burst = c->dst_maxburst;
> + ? ? ? }
>
> If we redefine the structure as below, this all becomes more simple:
>
> + ? ? ? if (dir == DMA_DEV_TO_MEM)
> + ? ? ? ? ? ? ? cfg = &c->dev_src;
> + ? ? ? else if (dir == DMA_MEM_TO_DEV)
> + ? ? ? ? ? ? ? cfg = &c->dev_dst;

it seems that might mean an union in your dma_slave_cfg, but not
co-exitense of both?

struct dma_slave_cfg {
+       union {
              struct dma_dev_cfg dev_src;
              struct dma_dev_cfg dev_dst;
       }
       bool device_fc;
};

>
> and then we can access the data through cfg->{element} rather than having
> to cache each individual elements value in a local variable.
>
> Thoughts?
>
> diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
> index 56377df..e6519f7 100644
> --- a/include/linux/dmaengine.h
> +++ b/include/linux/dmaengine.h
> @@ -367,6 +367,18 @@ struct dma_slave_config {
> ? ? ? ?bool device_fc;
> ?};
>
> +struct dma_dev_cfg {
> + ? ? ? dma_addr_t addr;
> + ? ? ? enum dma_slave_buswidth width;
> + ? ? ? u32 maxburst;
> +};
> +
> +struct dma_slave_cfg {
> + ? ? ? struct dma_dev_cfg dev_src;
> + ? ? ? struct dma_dev_cfg dev_dst;
> + ? ? ? bool device_fc;
> +};
> +
> ?static inline const char *dma_chan_name(struct dma_chan *chan)
> ?{
> ? ? ? ?return dev_name(&chan->dev->device);
>
Thanks
barry

  reply	other threads:[~2012-06-10 11:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-10 10:20 RFC: changing DMA slave configuration API Russell King - ARM Linux
2012-06-10 11:19 ` Barry Song [this message]
2012-06-10 11:22   ` Russell King - ARM Linux
2012-06-11  4:50     ` Vinod Koul
2012-06-11  8:24       ` Russell King - ARM Linux
2012-06-12  6:04         ` Vinod Koul
2012-06-11  9:33       ` Dong Aisheng
2012-06-12  5:54         ` Vinod Koul
2012-06-11 20:36       ` David Brown
2012-08-14 10:55       ` Linus Walleij

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=CAGsJ_4xHNdEcfsmtypDHcJ0uyhtFz43xBojgHw2RSvrH8ohRcA@mail.gmail.com \
    --to=21cnbao@gmail.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).