From: Nandor Han <nandor.han@ge.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: =Dan Williams <dan.j.williams@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
dmaengine@vger.kernel.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: EXT: Re: [PATCH RFC 1/4] dma: imx-sdma - reduce transfer latency for DMA cyclic clients
Date: Fri, 1 Jul 2016 17:59:30 +0300 [thread overview]
Message-ID: <57768552.6060407@ge.com> (raw)
In-Reply-To: <20160628143426.GB14945@localhost>
On 28/06/16 17:34, Vinod Koul wrote:
> On Thu, Jun 09, 2016 at 03:16:30PM +0300, Nandor Han wrote:
>> Having the SDMA driver use a tasklet for running the clients
>> callback introduce some issues:
>> - probability to have desynchronized data because of the
>> race condition created since the DMA transaction status
>> is retrieved only when the callback is executed, leaving
>> plenty of time for transaction status to get altered.
>> - inter-transfer latency which can leave channels idle.
>>
>> Move the callback execution, for cyclic channels, to SDMA
>> interrupt (as advised in `Documentation/dmaengine/provider.txt`)
>> to (a)reduce the inter-transfer latency and (b) eliminate the
>> race condition possibility where DMA transaction status might
>> be changed by the time is read.
>>
>> The responsibility of the SDMA interrupt latency
>> is moved to the SDMA clients which case by case should defer
>> the work to bottom-halves when needed.
>
> Both of these look fine. Please change the patch titles to dmaengine: xxxx
>
> Are these going to be merged thru dmaengine tree or serial one?
>
I will send soon a V2 where I will fix the titles. If you are OK with
all the patchset it can be merged to dmaengine tree, otherwise probably
goes to serial one.
Let me know which is the best option.
Thanks,
Nandor
>>
>> Signed-off-by: Nandor Han <nandor.han@ge.com>
>> ---
>> drivers/dma/imx-sdma.c | 36 ++++++++++++++++--------------------
>> 1 file changed, 16 insertions(+), 20 deletions(-)
>>
>> diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c
>> index 0f6fd42..e497847 100644
>> --- a/drivers/dma/imx-sdma.c
>> +++ b/drivers/dma/imx-sdma.c
>> @@ -654,12 +654,6 @@ static void sdma_event_disable(struct sdma_channel *sdmac, unsigned int event)
>> writel_relaxed(val, sdma->regs + chnenbl);
>> }
>>
>> -static void sdma_handle_channel_loop(struct sdma_channel *sdmac)
>> -{
>> - if (sdmac->desc.callback)
>> - sdmac->desc.callback(sdmac->desc.callback_param);
>> -}
>> -
>> static void sdma_update_channel_loop(struct sdma_channel *sdmac)
>> {
>> struct sdma_buffer_descriptor *bd;
>> @@ -678,13 +672,25 @@ static void sdma_update_channel_loop(struct sdma_channel *sdmac)
>> sdmac->status = DMA_ERROR;
>>
>> bd->mode.status |= BD_DONE;
>> +
>> + /*
>> + * The callback is called from the interrupt context in order
>> + * to reduce latency and to avoid the risk of altering the
>> + * SDMA transaction status by the time the client tasklet is
>> + * executed.
>> + */
>> +
>> + if (sdmac->desc.callback)
>> + sdmac->desc.callback(sdmac->desc.callback_param);
>> +
>> sdmac->buf_tail++;
>> sdmac->buf_tail %= sdmac->num_bd;
>> }
>> }
>>
>> -static void mxc_sdma_handle_channel_normal(struct sdma_channel *sdmac)
>> +static void mxc_sdma_handle_channel_normal(unsigned long data)
>> {
>> + struct sdma_channel *sdmac = (struct sdma_channel *) data;
>> struct sdma_buffer_descriptor *bd;
>> int i, error = 0;
>>
>> @@ -711,16 +717,6 @@ static void mxc_sdma_handle_channel_normal(struct sdma_channel *sdmac)
>> sdmac->desc.callback(sdmac->desc.callback_param);
>> }
>>
>> -static void sdma_tasklet(unsigned long data)
>> -{
>> - struct sdma_channel *sdmac = (struct sdma_channel *) data;
>> -
>> - if (sdmac->flags & IMX_DMA_SG_LOOP)
>> - sdma_handle_channel_loop(sdmac);
>> - else
>> - mxc_sdma_handle_channel_normal(sdmac);
>> -}
>> -
>> static irqreturn_t sdma_int_handler(int irq, void *dev_id)
>> {
>> struct sdma_engine *sdma = dev_id;
>> @@ -737,8 +733,8 @@ static irqreturn_t sdma_int_handler(int irq, void *dev_id)
>>
>> if (sdmac->flags & IMX_DMA_SG_LOOP)
>> sdma_update_channel_loop(sdmac);
>> -
>> - tasklet_schedule(&sdmac->tasklet);
>> + else
>> + tasklet_schedule(&sdmac->tasklet);
>>
>> __clear_bit(channel, &stat);
>> }
>> @@ -1739,7 +1735,7 @@ static int sdma_probe(struct platform_device *pdev)
>> dma_cookie_init(&sdmac->chan);
>> sdmac->channel = i;
>>
>> - tasklet_init(&sdmac->tasklet, sdma_tasklet,
>> + tasklet_init(&sdmac->tasklet, mxc_sdma_handle_channel_normal,
>> (unsigned long) sdmac);
>> /*
>> * Add the channel to the DMAC list. Do not add channel 0 though
>> --
>> 2.8.3
>>
>
next prev parent reply other threads:[~2016-07-01 14:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 12:16 [PATCH RFC 0/4] serial,dma: use DMA cyclic for IMX UART driver Nandor Han
2016-06-09 12:16 ` [PATCH RFC 1/4] dma: imx-sdma - reduce transfer latency for DMA cyclic clients Nandor Han
2016-06-28 14:34 ` Vinod Koul
2016-07-01 14:59 ` Nandor Han [this message]
2016-07-02 17:27 ` EXT: " Vinod Koul
2016-07-14 8:32 ` Peter Senna Tschudin
2016-06-09 12:16 ` [PATCH RFC 2/4] dma: imx-sdma - update the residue calculation for cyclic channels Nandor Han
2016-06-09 12:16 ` [PATCH RFC 3/4] serial: imx-serial - update UART IMX driver to use cyclic DMA Nandor Han
2016-06-09 12:16 ` [PATCH RFC 4/4] serial: imx-serial - update RX error counters when DMA is used Nandor Han
2016-08-08 12:38 ` [PATCH 0/4] serial,dmaengine: use DMA cyclic for IMX UART driver Nandor Han
2016-08-08 12:38 ` [PATCH 1/4] dmaengine: imx-sdma - reduce transfer latency for DMA cyclic clients Nandor Han
2016-08-08 12:38 ` [PATCH 2/4] dmaengine: imx-sdma - update the residue calculation for cyclic channels Nandor Han
2016-08-08 12:38 ` [PATCH 3/4] serial: imx-serial - update UART IMX driver to use cyclic DMA Nandor Han
2016-08-08 12:38 ` [PATCH 4/4] serial: imx-serial - update RX error counters when DMA is used Nandor Han
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=57768552.6060407@ge.com \
--to=nandor.han@ge.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=vinod.koul@intel.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;
as well as URLs for NNTP newsgroup(s).