dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Murzin <vladimir.murzin@arm.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: dmaengine@vger.kernel.org, Vinod Koul <vkoul@kernel.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>
Subject: Re: 6b41030fdc790 broke dmatest badly
Date: Tue, 15 Sep 2020 15:20:11 +0100	[thread overview]
Message-ID: <63be07b9-721b-44fe-14f5-a52ab36ce954@arm.com> (raw)
In-Reply-To: <20200915135659.GA3956970@smile.fi.intel.com>

On 9/15/20 2:56 PM, Andy Shevchenko wrote:
> On Tue, Sep 15, 2020 at 04:46:25PM +0300, Andy Shevchenko wrote:
>> On Tue, Sep 15, 2020 at 01:46:12PM +0100, Vladimir Murzin wrote:
>>> On 9/15/20 1:35 PM, Andy Shevchenko wrote:
>>>> On Fri, Sep 11, 2020 at 09:34:04AM +0100, Vladimir Murzin wrote:
>>>>> On 9/7/20 5:52 PM, Vladimir Murzin wrote:
>>
>> ...
>>
>>>>> An update on this?
>>>>
>>>> Sorry for delay. I have tested your patch and it works for my case. Though I
>>>> would amend it a bit (commit message is still a due).
>>>
>>>
>>> That's good, but what about behaviour prior d53513d5dc28? Did you (or somebody
>>> else) have a chance to confirm that it won't run with plain defaults?
> 
> Yes, I may confirm this. I have taken dmatest just before that commit as of
>   % git checkout 3f3c75541ffe -- drivers/dma/dmatest.c
> and it simple returns 0 and nothing happens.

Thanks a lot for confirmation!

> 
> So, please provide a commit message to your fix, I'll incorporate it and send as a part of the series.
> 

dmaengine: dmatest: Fix regression in run command with mis-configured channel

Andy reported that commit 6b41030fdc79 ("dmaengine: dmatest:
Restore default for channel") broke his scripts for the case
where "busy" channel is used for configuration with expectation
that run command would do nothing (and return 0). Instead,
behavior was (unintentionally) changed to treat such case as
under-configuration and progress with defaults, i.e. run command
would start a test with default setting for channel (which would
use all channels).

Restore original behavior with tracking status of channel setter
so we can distinguish between mis-configured and under-configured
cases in run command and act accordingly.

Fixes: 6b41030fdc79086db5d673c5ed7169f3ee8c13b9 ("dmaengine: dmatest: Restore default for channel")
Reported-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Tested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Signed-off-by: Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>

Cheers
Vladimir


      reply	other threads:[~2020-09-16  0:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04 17:34 6b41030fdc790 broke dmatest badly Andy Shevchenko
2020-09-07 11:03 ` Vladimir Murzin
2020-09-07 12:04   ` Andy Shevchenko
2020-09-07 13:06     ` Vladimir Murzin
2020-09-07 14:05       ` Andy Shevchenko
2020-09-07 16:52         ` Vladimir Murzin
2020-09-11  8:34           ` Vladimir Murzin
2020-09-15 12:35             ` Andy Shevchenko
2020-09-15 12:46               ` Vladimir Murzin
     [not found]                 ` <20200915134625.GZ3956970@smile.fi.intel.com>
2020-09-15 13:56                   ` Andy Shevchenko
2020-09-15 14:20                     ` Vladimir Murzin [this message]

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=63be07b9-721b-44fe-14f5-a52ab36ce954@arm.com \
    --to=vladimir.murzin@arm.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=peter.ujfalusi@ti.com \
    --cc=vkoul@kernel.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).