From: Vinod Koul <vinod.koul@intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>
Cc: linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
Sudeep Dutt <sudeep.dutt@intel.com>,
Nikhil Rao <nikhil.rao@intel.com>,
Siva Yerramreddy <yshivakrishna@gmail.com>,
Saurabh Sengar <saurabh.truth@gmail.com>
Subject: Re: [PATCH] dma: Revert "dmaengine: mic_x100: add missing spin_unlock"
Date: Mon, 4 Jan 2016 09:05:26 +0530 [thread overview]
Message-ID: <20160104033526.GA2940@localhost> (raw)
In-Reply-To: <1450841723-6227-1-git-send-email-ashutosh.dixit@intel.com>
On Tue, Dec 22, 2015 at 07:35:23PM -0800, Ashutosh Dixit wrote:
> This reverts commit e958e079e254 ("dmaengine: mic_x100: add missing
> spin_unlock").
>
> The above patch is incorrect. There is nothing wrong with the original
> code. The spin_lock is acquired in the "prep" functions and released
> in "submit".
And going by dmaengine sematics, I do not think that is entrely right.
A user may choose to prepare multiple desciptors and then sumbit later,
looking at code I do not see how that will work.
Please fix that
>
> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> ---
> drivers/dma/mic_x100_dma.c | 15 +++++----------
> 1 file changed, 5 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/dma/mic_x100_dma.c b/drivers/dma/mic_x100_dma.c
> index cddfa8d..068e920 100644
> --- a/drivers/dma/mic_x100_dma.c
> +++ b/drivers/dma/mic_x100_dma.c
> @@ -317,7 +317,6 @@ mic_dma_prep_memcpy_lock(struct dma_chan *ch, dma_addr_t dma_dest,
> struct mic_dma_chan *mic_ch = to_mic_dma_chan(ch);
> struct device *dev = mic_dma_ch_to_device(mic_ch);
> int result;
> - struct dma_async_tx_descriptor *tx = NULL;
>
> if (!len && !flags)
> return NULL;
> @@ -325,13 +324,10 @@ mic_dma_prep_memcpy_lock(struct dma_chan *ch, dma_addr_t dma_dest,
> spin_lock(&mic_ch->prep_lock);
> result = mic_dma_do_dma(mic_ch, flags, dma_src, dma_dest, len);
> if (result >= 0)
> - tx = allocate_tx(mic_ch);
> -
> - if (!tx)
> - dev_err(dev, "Error enqueueing dma, error=%d\n", result);
> -
> + return allocate_tx(mic_ch);
> + dev_err(dev, "Error enqueueing dma, error=%d\n", result);
> spin_unlock(&mic_ch->prep_lock);
> - return tx;
> + return NULL;
> }
>
> static struct dma_async_tx_descriptor *
> @@ -339,14 +335,13 @@ mic_dma_prep_interrupt_lock(struct dma_chan *ch, unsigned long flags)
> {
> struct mic_dma_chan *mic_ch = to_mic_dma_chan(ch);
> int ret;
> - struct dma_async_tx_descriptor *tx = NULL;
>
> spin_lock(&mic_ch->prep_lock);
> ret = mic_dma_do_dma(mic_ch, flags, 0, 0, 0);
> if (!ret)
> - tx = allocate_tx(mic_ch);
> + return allocate_tx(mic_ch);
> spin_unlock(&mic_ch->prep_lock);
> - return tx;
> + return NULL;
> }
>
> /* Return the status of the transaction */
> --
> 2.0.0.rc3.2.g998f840
>
--
~Vinod
next prev parent reply other threads:[~2016-01-04 3:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 3:35 [PATCH] dma: Revert "dmaengine: mic_x100: add missing spin_unlock" Ashutosh Dixit
2015-12-23 5:45 ` Saurabh Sengar
2015-12-23 6:14 ` Ashutosh Dixit
2016-01-04 3:35 ` Vinod Koul [this message]
2016-01-04 14:35 ` Lars-Peter Clausen
2016-01-04 15:07 ` Vinod Koul
2016-01-04 22:40 ` Ashutosh Dixit
2016-01-06 10:11 ` Vinod Koul
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=20160104033526.GA2940@localhost \
--to=vinod.koul@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhil.rao@intel.com \
--cc=saurabh.truth@gmail.com \
--cc=sudeep.dutt@intel.com \
--cc=yshivakrishna@gmail.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).