From: Daniel Mack <zonque@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Vinod Koul <vinod.koul@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org, Felipe Balbi <balbi@ti.com>,
linux-usb@vger.kernel.org, kishon@ti.com
Subject: Re: [PATCH 1/2] dma: cppi41: redo descriptor collection in abort case
Date: Mon, 28 Oct 2013 12:10:44 +0100 [thread overview]
Message-ID: <526E4634.1070505@gmail.com> (raw)
In-Reply-To: <5260F961.1000308@gmail.com>
On 10/18/2013 11:03 AM, Daniel Mack wrote:
> Hi Sebastian,
>
> On 10/17/2013 04:36 PM, Sebastian Andrzej Siewior wrote:
>> On 10/17/2013 04:23 PM, Daniel Mack wrote:
>>>> Daniel, could please look if this solves your suspend / resume warnings?
>
> Looking very good :)
>
>> dma: cppi41: add support for suspend and resume
>> dma: cppi41: restore more registers
>> dma: cppi41: use cppi41_pop_desc() where possible
>> dma: cppi41: redo descriptor collection in abort case
>> dma: cppi41: return code > 0 of pm_runtime_get_sync() is not an error
>
> Tested with those patches applied, and did dozens of sleep/resume cycley
> - no problem seen.
>
> Thanks a bunch again. Vinod, you can add my
>
> Tested-by: Daniel Mack <zonque@gmail.com>
>
> if you want.
Vinod, in case you're ok with these changes, it would be good to have
them for 3.13. Sebastian recently resent them all again (3 from me, 2
from him).
Thanks,
Daniel
prev parent reply other threads:[~2013-10-28 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 14:19 [PATCH 1/2] dma: cppi41: redo descriptor collection in abort case Sebastian Andrzej Siewior
2013-10-17 14:19 ` [PATCH 2/2] dma: cppi41: return code > 0 of pm_runtime_get_sync() is not an error Sebastian Andrzej Siewior
2013-10-17 14:20 ` [PATCH 1/2] dma: cppi41: redo descriptor collection in abort case Sebastian Andrzej Siewior
2013-10-17 14:23 ` Daniel Mack
2013-10-17 14:36 ` Sebastian Andrzej Siewior
[not found] ` <5260F961.1000308@gmail.com>
2013-10-28 11:10 ` Daniel Mack [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=526E4634.1070505@gmail.com \
--to=zonque@gmail.com \
--cc=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=dan.j.williams@intel.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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