Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp194721ybv; Wed, 5 Feb 2020 04:01:20 -0800 (PST) X-Google-Smtp-Source: APXvYqwEZ+IeB2GRDxX57hcmvztrCawroaR4LLo9l1rgMkECRDaxCIJpalWQ+9JxGiJ3s/1u7l8f X-Received: by 2002:aca:ec13:: with SMTP id k19mr2500490oih.22.1580904080668; Wed, 05 Feb 2020 04:01:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1580904080; cv=none; d=google.com; s=arc-20160816; b=b32sAVlEORLaizEZGTQ2WIaTHnQZtqL5B6Bv55SgQ0XtDZZHP6Ym5u9Cf/o44ffE33 wr/kzT2AZzSJdssgH4yLA44dRgD9zpUY8EUKyTr4zs0lbUCKT40n2PMn5BIAcdodIH5R /hy7cQ93hCHhY+cEN3GBRTOKgewgkwhrV8d/EgluNFyeXdI0nV1Dq8Nt0YXcqdTitD76 resPLD+hRGrGb2VwQ24IpVGo5ZRKUivvMyZVNNDEahQxrmh07s8MRHu2/eeRu3mi4jal j8qqjP2peGno2pyowa/nRqUPt9yBXsH4IdJ0Zr8Y9RaqzpQYsOnwCNj/vYZzJSP/KAOo wm3w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=ZrM2U62DYbGdCwQ/G2cJjbO5Z34uzC0Gk2bfV6Np6iQ=; b=C6cLltD8OM1VOQ2cLxvZje2J7Kdu7B0rTDy4PIHgz55veeRY0xIQ1Hqg37TJPMRTQP m21IWFIhJQnAQfaSIf9JtOeoroZeSMOaGxTD57cFONim8598Sy5UvinGxT9xpfP8GIGP az9RtTwwklFr19hAHSK54czdK6SheAprP4aTEOtkwi0trw/bKjBjulaTIDNav4UgI5oN jNmuETiCvC0GyTUmUOUTa0LvK4/+x/LWT4xNi62JBEYG8LhstMpjCK7f0s/4gFfgkuWk Mba+kXVtlWKxyEEBLYhDYGeVUzMFSx+z/Iwc/GYagPgSlyvL6G1mvekkbTjQtlZIu9Za Vdmg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=i+T2aI18; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j65si12816541otc.308.2020.02.05.04.01.07; Wed, 05 Feb 2020 04:01:20 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=i+T2aI18; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727109AbgBEL7L (ORCPT + 99 others); Wed, 5 Feb 2020 06:59:11 -0500 Received: from mail.kernel.org ([198.145.29.99]:47700 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726386AbgBEL7L (ORCPT ); Wed, 5 Feb 2020 06:59:11 -0500 Received: from localhost (unknown [122.178.239.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id E1CB4217F4; Wed, 5 Feb 2020 11:59:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1580903950; bh=e2wpDkaca94WD5/bWbgprPG9Vj1e3ghMDbeVWFnC7pE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=i+T2aI18PEwzwPN66edZzxNyr1exqENkEPYyPzuqFmOkbeMADS1niFPCUm4eumM4g tHOY+IUkpDB9RbEY+KuYCn1gfEKlXNMdbfxIViOy+lN15E3W7rUs37XcfTcFVANG+U 0YAObt+d/CnW2Em9D1vT97V2wrWlREYxu5MB8UnM= Date: Wed, 5 Feb 2020 17:29:06 +0530 From: Vinod Koul To: Peter Ujfalusi Cc: Andy Shevchenko , dmaengine , Linux Kernel Mailing List , Dan Williams Subject: Re: [PATCH 0/3] dmaengine: Stear users towards dma_request_slave_chan() Message-ID: <20200205115906.GF2618@vkoul-mobl> References: <20200203101806.2441-1-peter.ujfalusi@ti.com> <20200204062118.GS2841@vkoul-mobl> <20200205044352.GC2618@vkoul-mobl> <13dcf3d9-06ca-d793-525d-12f6d7cd27c1@ti.com> <20200205113155.GE2618@vkoul-mobl> <7b8d9ab2-1734-d54b-ab6e-b620866ce0ce@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7b8d9ab2-1734-d54b-ab6e-b620866ce0ce@ti.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05-02-20, 13:56, Peter Ujfalusi wrote: > Hi Vinod, > > On 05/02/2020 13.31, Vinod Koul wrote: > >> Looking at the commit which added it and I still don't get the point. > >> If any of the channel is in use then we should not allow the DMA driver > >> to go away at all. > > > > Not really, if the device is already gone, we cant do much about it. We > > have to handle that gracefully rather than oopsing > > Ah, I have not thought about that. True. > > > The important part is that the device is gone. Think about a device on > > PCI card which is yanked off or a USB device unplugged. Device is > > already gone, you can't communicate with it anymore. So all we can do is > > handle the condition and exit, hence the new method to let driver know. > > But for most devices this is not applicable, I also wondered what should > I do in order to silence the print. Just add an empty device_release? I will send a patch removing this before we hit release :) so nothing to be done unless you have a hotpluggable device then would be good to add this. Thanks -- ~Vinod