From: Vinod Koul <vinod.koul@intel.com>
To: George Cherian <george.cherian@ti.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
dmaengine@vger.kernel.org, gregkh@linuxfoundation.org,
balbi@ti.com, dan.j.williams@intel.com, msmucr@gmail.com
Subject: Re: [PATCH 0/2] Fix CPPI Warnings during tear down after ISOCH transfers
Date: Tue, 11 Mar 2014 16:23:08 +0530 [thread overview]
Message-ID: <20140311105308.GT1976@intel.com> (raw)
In-Reply-To: <1393478081-14226-1-git-send-email-george.cherian@ti.com>
On Thu, Feb 27, 2014 at 10:44:39AM +0530, George Cherian wrote:
> Warinings are seen after ISOCH transfers, during channel tear down.
> This is mainly beacause we handle ISOCH differently as compared to
> other transfers.
>
> Patch 1: make sure we do channel tear down only if channel is busy.
> If not the tear down will never succeed.
>
> Patch 2: ISOCH completions are done differently, so this might lead to
> reprogram of dma channel on which already a teardown is done.
Applied, Thanks
--
~Vinod
prev parent reply other threads:[~2014-03-11 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 5:14 [PATCH 0/2] Fix CPPI Warnings during tear down after ISOCH transfers George Cherian
2014-02-27 5:14 ` [PATCH 1/2] dma: cppi41: start tear down only if channel is busy George Cherian
2014-02-27 8:47 ` Shevchenko, Andriy
2014-02-28 5:53 ` George Cherian
2014-02-27 5:14 ` [PATCH 2/2] usb: musb: musb_cppi41: Dont reprogram DMA if tear down is initiated George Cherian
2014-03-11 10:53 ` Vinod Koul [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=20140311105308.GT1976@intel.com \
--to=vinod.koul@intel.com \
--cc=balbi@ti.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=george.cherian@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=msmucr@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