mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ashutosh Dixit <ashutosh.dixit@intel.com>
To: Saurabh Sengar <saurabh.truth@gmail.com>
Cc: "Koul\, Vinod" <vinod.koul@intel.com>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dmaengine\@vger.kernel.org" <dmaengine@vger.kernel.org>, "Dutt\,
	Sudeep" <sudeep.dutt@intel.com>, "Rao\,
	Nikhil" <nikhil.rao@intel.com>,
	Siva Yerramreddy <yshivakrishna@gmail.com>
Subject: Re: [PATCH] dma: Revert "dmaengine: mic_x100: add missing spin_unlock"
Date: Wed, 23 Dec 2015 01:14:20 -0500	[thread overview]
Message-ID: <tnm1tbn9hd743.fsf@phwtpriv05.ph.intel.com> (raw)
In-Reply-To: <CAA8avJ9e68P2L+cR-PCptwFguPmTuC5ptutsopTMpWmfeWz0Fg@mail.gmail.com> (Saurabh Sengar's message of "Tue, 22 Dec 2015 22:45:31 -0700")

On Wed, Dec 23 2015 at 12:45:31 AM, Saurabh Sengar <saurabh.truth@gmail.com> wrote:
> On 23 December 2015 at 09:05, Ashutosh Dixit <ashutosh.dixit@intel.com> 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".
>
> Hi Ashutosh,
>
> If it is need to be released by submit function, we don't require the
> spin_unlock on success case as well.
> am I correct ?

No, you are wrong. In the prep functions, we are not using spin_unlock in
success cases but in failure ones.

>> 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);
>
> This spin_unlock shouldn't be required as explained it is getting
> released by submit function

This is a failure case. Submit will not be called in this case so
spin_unlock needs to be called here.

>> -       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);
>
> and this too ?

Yes, this too.

>> -       return tx;
>> +       return NULL;
>>  }
>>
>>  /* Return the status of the transaction */
>> --
>> 2.0.0.rc3.2.g998f840
>>

  reply	other threads:[~2015-12-23  6:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-23  3:35 Ashutosh Dixit
2015-12-23  5:45 ` Saurabh Sengar
2015-12-23  6:14   ` Ashutosh Dixit [this message]
2016-01-04  3:35 ` Vinod Koul
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=tnm1tbn9hd743.fsf@phwtpriv05.ph.intel.com \
    --to=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=vinod.koul@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

Powered by JetHome