From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Vinod Koul <vinod.koul@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Paul Mundt <lethal@linux-sh.org>,
linux-sh@vger.kernel.org, Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 1/9 v3] dmaengine: add an shdma-base library
Date: Fri, 18 May 2012 10:21:21 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.1205171912140.10086@axis700.grange> (raw)
In-Reply-To: <1337055734.16185.5360.camel@vkoul-udesk3>
Hi Vinod
Thanks for your review.
On Tue, 15 May 2012, Vinod Koul wrote:
> On Wed, 2012-05-09 at 17:09 +0200, Guennadi Liakhovetski wrote:
> > This patch extracts code from shdma.c, that does not directly deal with
> > hardware implementation details and can be re-used with diverse DMA
> > controller variants, found on SH-based SoCs.
> Have you see recent Russell's virtual dma patches [1]? I like the idea
> and simplifies things for implementation in each driver.
> Said that, do we need this libarry. Can you see if you can use/enhance
> that one.
No, I haven't seen it. I had a look at it, and it doesn't seem to provide
an immediate solution to our problem. It can be used as a part of one, but
a significant amount of work would still be required to convert shdma to a
virtual-channel based design.
Let me try to describe, what such a virtual channel solution would look
like:
1. One (virtual) DMA channel is allocated per client
2. As clients issue dma_request_channel(), the correct channel is selected
3. The client configures the channel with a call to
dmaengine_slave_config()
4. As transfers are prepared and issued they are queued in per-virtual
channel lists
5. Each virtual channel links to a list of suitable DMA devices and
channels
6. As a new transfer request on a specific virtual channel has to be
processed, a suitable free physical channel is picked up, configured
and the request is sent out
If this my understanding is right, this should be doable, but not within
the current 3.5 time-frame. Further, if we first do this conversion, we'll
still have to split the driver similar to what is proposed by this patch
series, but then it would be largely a new effort, most of the work
invested into this so far will be lost. OTOH, if we now push the shdma
driver split, we enable the merge of the SUDMAC support and porting to the
virtual channel design should also become easier, because the hardware and
the software parts of the driver will already be separated and presumably
the hardware part will not need to be changed.
One more thing, before going into detail and replying to your comments:
this split doesn't change driver's functionality, it simply splits it into
two parts. So, most questions, that you ask in this your review would also
apply to the current driver. This patch just extracts hardware-neutral
code from the shdma driver into a separate file. I think, any functional
changes should be done separately from this driver-split series.
[snip]
> > +static dma_cookie_t shdma_tx_submit(struct dma_async_tx_descriptor *tx)
> > +{
> > + struct shdma_desc *chunk, *c, *desc =
> > + container_of(tx, struct shdma_desc, async_tx),
> > + *last = desc;
> > + struct shdma_chan *schan = to_shdma_chan(tx->chan);
> > + struct shdma_slave *slave = tx->chan->private;
> > + dma_async_tx_callback callback = tx->callback;
> > + dma_cookie_t cookie;
> > + bool power_up;
> > +
> > + spin_lock_irq(&schan->chan_lock);
> > +
> > + power_up = list_empty(&schan->ld_queue);
> > +
> > + cookie = dma_cookie_assign(tx);
> > +
> > + /* Mark all chunks of this descriptor as submitted, move to the queue */
> > + list_for_each_entry_safe(chunk, c, desc->node.prev, node) {
> > + /*
> > + * All chunks are on the global ld_free, so, we have to find
> > + * the end of the chain ourselves
> > + */
> > + if (chunk != desc && (chunk->mark == DESC_IDLE ||
> > + chunk->async_tx.cookie > 0 ||
> > + chunk->async_tx.cookie == -EBUSY ||
> > + &chunk->node == &schan->ld_free))
> > + break;
> > + chunk->mark = DESC_SUBMITTED;
> > + /* Callback goes to the last chunk */
> > + chunk->async_tx.callback = NULL;
> > + chunk->cookie = cookie;
> > + list_move_tail(&chunk->node, &schan->ld_queue);
> > + last = chunk;
> > +
> > + dev_dbg(schan->dev, "submit #%d@%p on %d\n",
> > + tx->cookie, &last->async_tx, schan->id);
> > + }
> > +
> > + last->async_tx.callback = callback;
> > + last->async_tx.callback_param = tx->callback_param;
> > +
> > + if (power_up) {
> > + int ret;
> > + schan->pm_state = SHDMA_PM_BUSY;
> > +
> > + ret = pm_runtime_get(schan->dev);
> any reason why this is here and not in issue pending?
Sorry, we have discussed this multiple times already. See, for example,
http://thread.gmane.org/gmane.linux.kernel/1181989/focus=12187
[snip]
> > +/*
> > + * Drivers, using this library are expected to embed struct shdma_dev,
> > + * struct shdma_chan, struct shdma_desc, and struct shdma_slave
> > + * in their respective device, channel, descriptor and slave objects.
> > + */
> > +
> > +struct shdma_slave {
> > + unsigned int slave_id;
> this should be moved to struct dma_slave_config
Again, this would be a functional change. And struct dma_slave_config
doesn't have a slave-ID field in it, which is the only thing we need for
now. Instead it has a bunch of other fields, of which none is so far used
by this driver.
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
next prev parent reply other threads:[~2012-05-18 8:21 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 15:09 [PATCH 0/9 v3] extract an shdma base library from shdma.c Guennadi Liakhovetski
2012-05-09 15:09 ` [PATCH 1/9 v3] dmaengine: add an shdma-base library Guennadi Liakhovetski
2012-05-15 4:22 ` Vinod Koul
2012-05-18 8:21 ` Guennadi Liakhovetski [this message]
2012-05-25 8:15 ` Vinod Koul
2012-05-25 8:30 ` Guennadi Liakhovetski
2012-06-28 8:52 ` Guennadi Liakhovetski
2012-07-02 20:28 ` Guennadi Liakhovetski
2012-07-02 20:30 ` [PATCH 0.5/9] dma: move shdma driver to an own directory Guennadi Liakhovetski
2012-07-13 3:26 ` [PATCH 1/9 v3] dmaengine: add an shdma-base library Vinod Koul
2012-07-16 5:58 ` Vinod Koul
2012-05-25 10:27 ` Laxman Dewangan
2012-05-25 10:59 ` Guennadi Liakhovetski
2012-05-09 15:09 ` [PATCH 2/9 v3] dma: shdma: prepare for conversion to the shdma base library Guennadi Liakhovetski
2012-05-15 4:23 ` Vinod Koul
2012-05-18 8:21 ` Guennadi Liakhovetski
2012-05-09 15:09 ` [PATCH 3/9 v3] mmc: sh_mmcif: remove unneeded struct sh_mmcif_dma, prepare to shdma conversion Guennadi Liakhovetski
2012-07-05 17:35 ` Chris Ball
2012-05-09 15:09 ` [PATCH 4/9 v3] mmc: sh_mobile_sdhi: prepare for conversion to the shdma base library Guennadi Liakhovetski
2012-07-05 17:37 ` Chris Ball
2012-05-09 15:09 ` [PATCH 5/9 v3] serial: sh-sci: " Guennadi Liakhovetski
2012-05-10 3:09 ` Paul Mundt
2012-05-15 4:27 ` Vinod Koul
2012-05-18 8:21 ` Guennadi Liakhovetski
2012-05-09 15:09 ` [PATCH 6/9 v3] ASoC: siu: " Guennadi Liakhovetski
2012-05-09 15:37 ` Mark Brown
2012-05-09 15:09 ` [PATCH 7/9 v3] usb: renesas_usbhs: " Guennadi Liakhovetski
2012-05-09 23:59 ` kuninori.morimoto.gx
2012-05-10 0:07 ` Greg Kroah-Hartman
2012-05-09 15:09 ` [PATCH 8/9 v3] ASoC: fsi: " Guennadi Liakhovetski
2012-05-09 15:39 ` Mark Brown
2012-05-09 23:59 ` kuninori.morimoto.gx
2012-05-09 15:09 ` [PATCH 9/9 v3] dma: shdma: convert " Guennadi Liakhovetski
2012-07-25 3:59 ` Paul Mundt
2012-07-26 6:49 ` Vinod Koul
2012-07-26 6:58 ` Paul Mundt
2012-07-26 11:20 ` Vinod Koul
2012-07-26 21:39 ` Guennadi Liakhovetski
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=Pine.LNX.4.64.1205171912140.10086@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=vinod.koul@linux.intel.com \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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
all inboxes | Powered by JetHome®