Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932721AbcLGQeB (ORCPT ); Wed, 7 Dec 2016 11:34:01 -0500 Received: from mga03.intel.com ([134.134.136.65]:36651 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932520AbcLGQd6 (ORCPT ); Wed, 7 Dec 2016 11:33:58 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,310,1477983600"; d="scan'208";a="1069197196" Date: Wed, 7 Dec 2016 22:13:41 +0530 From: Vinod Koul To: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= Cc: Mason , Russell King , dmaengine@vger.kernel.org, Linus Walleij , Dan Williams , LKML , Linux ARM , Jon Mason , Mark Brown , Lars-Peter Clausen , Lee Jones , Laurent Pinchart , Arnd Bergmann , Maxime Ripard , Dave Jiang , Peter Ujfalusi , Bartlomiej Zolnierkiewicz , Sebastian Frias , Thibaud Cornic Subject: Re: Tearing down DMA transfer setup after DMA client has finished Message-ID: <20161207164341.GX6408@localhost> References: <58356EA8.2010806@free.fr> <20161125045549.GC2698@localhost> <092f44ee-4560-be17-25f7-00948dba3cfa@free.fr> <20fc9020-7278-bc2f-2a8d-43aff5cabff8@free.fr> <20161206051222.GQ6408@localhost> <5846B237.8060409@free.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: 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 Content-Length: 443 Lines: 12 On Tue, Dec 06, 2016 at 01:14:20PM +0000, M?ns Rullg?rd wrote: > > That's not going to work very well. Device drivers typically request > dma channels in their probe functions or when the device is opened. > This means that reserving one of the few channels there will inevitably > make some other device fail to operate. No that doesnt make sense at all, you should get a channel only when you want to use it and not in probe! -- ~Vinod