Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933101Ab0FRNwt (ORCPT ); Fri, 18 Jun 2010 09:52:49 -0400 Received: from relay.atmel.no ([80.232.32.139]:62186 "EHLO relay.atmel.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932913Ab0FRNws (ORCPT ); Fri, 18 Jun 2010 09:52:48 -0400 Date: Fri, 18 Jun 2010 15:52:34 +0200 From: Haavard Skinnemoen To: Viresh KUMAR Cc: Dan Williams , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "'Shiraz HASHIM'" , Armando VISCONTI Subject: Re: Query dw_dmac driver: All descriptors done, but channel not idle! Message-ID: <20100618155234.1fc40ce7@hskinnemoen-d830> In-Reply-To: <4C1B75B7.1080104@st.com> References: <4C1B75B7.1080104@st.com> Organization: Atmel X-Mailer: Claws Mail 3.7.4 (GTK+ 2.20.1; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1073 Lines: 24 Viresh KUMAR 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. Haavard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/