From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932987AbdACD5T (ORCPT ); Mon, 2 Jan 2017 22:57:19 -0500 Received: from mga14.intel.com ([192.55.52.115]:20624 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752258AbdACD5M (ORCPT ); Mon, 2 Jan 2017 22:57:12 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,451,1477983600"; d="scan'208";a="25391693" Date: Tue, 3 Jan 2017 09:27:04 +0530 From: Vinod Koul To: "M'boumba Cedric Madianga" Cc: robh+dt@kernel.org, mark.rutland@arm.com, mcoquelin.stm32@gmail.com, alexandre.torgue@st.com, dan.j.williams@intel.com, dmaengine@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH RESEND] dmaengine: stm32-dma: Rework starting transfer management Message-ID: <20170103035703.GE3573@localhost> References: <1483349607-16870-1-git-send-email-cedric.madianga@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1483349607-16870-1-git-send-email-cedric.madianga@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 02, 2017 at 10:33:27AM +0100, M'boumba Cedric Madianga wrote: > This patch reworks the way to manage transfer starting. > Now, starting DMA is only allowed when the channel is not busy. > Then, stm32_dma_start_transfer is declared as void. > At least, after each transfer completion, we start the next transfer if a > new descriptor as been queued in the issued list during an ongoing > transfer. ah sorry, i missed to push topic/stm32-dma. can you rebase onnthis and resend again. Btw this fails as as well.. -- ~Vinod