All of lore.kernel.org
 help / color / mirror / Atom feed
From: viresh.kumar@st.com (Viresh KUMAR)
To: linux-arm-kernel@lists.infradead.org
Subject: Query dw_dmac driver: All descriptors done, but channel not idle!
Date: Fri, 18 Jun 2010 19:26:02 +0530	[thread overview]
Message-ID: <4C1B7AF2.1060500@st.com> (raw)
In-Reply-To: <20100618155234.1fc40ce7@hskinnemoen-d830>

On 6/18/2010 7:22 PM, Haavard Skinnemoen wrote:
> Viresh KUMAR <viresh.kumar@st.com> wrote:
>> Can somebody please confirm, if it a known issue or not? Or if there
>> are some solutions for this problem.
> 
> I'm not aware of any such issue. The code was added as a purely
> defensive thing; when writing it, I just thought about what might
> happen if we go through all our descriptors without finding the current
> one, and added some code to report the issue and try to recover.
> 
> I suppose it might be caused by some issue with the peripheral itself,
> but I think it's more likely to be caused by some race condition in the
> driver, i.e. something goes wrong when inserting or removing
> descriptors in the chain.
> 
> What might be very good to know at this point is the value of
> the llp variable, and perhaps also the value of the CH_EN register to
> see if the channel is idle or not.
> 

Thanks Haavard,

Will debug it further.

viresh.

WARNING: multiple messages have this Message-ID (diff)
From: Viresh KUMAR <viresh.kumar@st.com>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"'Shiraz HASHIM'" <shiraz.hashim@st.com>,
	Armando VISCONTI <armando.visconti@st.com>
Subject: Re: Query dw_dmac driver: All descriptors done, but channel not idle!
Date: Fri, 18 Jun 2010 19:26:02 +0530	[thread overview]
Message-ID: <4C1B7AF2.1060500@st.com> (raw)
In-Reply-To: <20100618155234.1fc40ce7@hskinnemoen-d830>

On 6/18/2010 7:22 PM, Haavard Skinnemoen wrote:
> Viresh KUMAR <viresh.kumar@st.com> wrote:
>> Can somebody please confirm, if it a known issue or not? Or if there
>> are some solutions for this problem.
> 
> I'm not aware of any such issue. The code was added as a purely
> defensive thing; when writing it, I just thought about what might
> happen if we go through all our descriptors without finding the current
> one, and added some code to report the issue and try to recover.
> 
> I suppose it might be caused by some issue with the peripheral itself,
> but I think it's more likely to be caused by some race condition in the
> driver, i.e. something goes wrong when inserting or removing
> descriptors in the chain.
> 
> What might be very good to know at this point is the value of
> the llp variable, and perhaps also the value of the CH_EN register to
> see if the channel is idle or not.
> 

Thanks Haavard,

Will debug it further.

viresh.

  reply	other threads:[~2010-06-18 13:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18 13:33 Query dw_dmac driver: All descriptors done, but channel not idle! Viresh KUMAR
2010-06-18 13:33 ` Viresh KUMAR
2010-06-18 13:52 ` Haavard Skinnemoen
2010-06-18 13:52   ` Haavard Skinnemoen
2010-06-18 13:56   ` Viresh KUMAR [this message]
2010-06-18 13:56     ` Viresh KUMAR

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=4C1B7AF2.1060500@st.com \
    --to=viresh.kumar@st.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.