Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp3712274ybi; Sun, 2 Jun 2019 21:44:22 -0700 (PDT) X-Google-Smtp-Source: APXvYqw+sOqW3UlIvLIhUlTW0MLg8JUH372BhuhlTr80qHs1uWhJTSRW1OpGQEv3f9VqwjTMJLw7 X-Received: by 2002:a63:cc43:: with SMTP id q3mr26174836pgi.438.1559537062178; Sun, 02 Jun 2019 21:44:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559537062; cv=none; d=google.com; s=arc-20160816; b=gW3rcHYWzMRetUGHNzK1smvOpmcAzQBpwswt8kZOdfaY2Eu+b4UsFhUprF7r2/A0tn dXcbpNe+hR1grX6c2E6joEp5cjGCt3lxTMyIE0C632EH5ha4HKwRlHy4192Rb8PSwBO8 /EB5irLuX9dqyHC3ao06IxvXMNNZQfSykQZE96U5AwAxr6YsVfP7WV73+5NF/RbOVgrF MIZGDcyVlA0TOEvaairkt/+I0Vg3HuPrNDrOBQOIq+STQVmcO17ayX6Out2Pm7msgR0/ wmgMisRRtmydUJFSJN4QoLArHhg6/3AWHYQKKFh1FzHSgYf4D7cLx4b47TIHf50I3e0S 5UfQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=sjQ88yBYOIe8eiogfHAldkgdjEVC1iDfV3zeZY5rh2g=; b=Bdvls0iC89dT40lPBEFzAoL9txtc1A1Wfiq2hgg8HsKW8JW19ULsDzR2Tg1irK706E JhOvzLbKNAAmFl7QHEVSX3DELeQ8wKyW+cQOtfPFrcFTWdL7SbeAkgM8uS6SpP39wK0A 82QHVqNTTM/DOWuxCWEs5HU80IDQ1YC1fveYN8TgKfJFNfMot6LesNcGvcJbXjUKcozM rEDeiRv9vxdFpRcoP5RLpNjSka/nGtGhkDsS6FoflW6e4m3zzVVWplNeDY7quTNU82Yf ktBiNtI+Q5+lYaq6QIN7KV8hlElCO7sWG0Zq9fbzsHw+DRIt9sikS4GxDoecuZQkpmxa rbrA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=WA9TJKkM; 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 t5si16436074pgv.164.2019.06.02.21.44.04; Sun, 02 Jun 2019 21:44:22 -0700 (PDT) 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=WA9TJKkM; 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 S1726565AbfFCEm6 (ORCPT + 99 others); Mon, 3 Jun 2019 00:42:58 -0400 Received: from mail.kernel.org ([198.145.29.99]:49924 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726277AbfFCEm6 (ORCPT ); Mon, 3 Jun 2019 00:42:58 -0400 Received: from localhost (unknown [106.51.109.249]) (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 9297427B7F; Mon, 3 Jun 2019 04:42:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1559536977; bh=b0KkH0Lj6BQEkhVygSpgJ3mJjqE4vfh/Xpt0AD6GEtE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=WA9TJKkMLWxMsSGCBg+GIiPeAkLdPj9QPtUrqyFV53pUeJrwJFb1ZMwRBOM+2ZZPD soo2kg7BO7pclLmv7aHqs95DvajdGpITbc761avkiZAqaLQEOHm3X5z+tG+P0vi/Rj F0jqZWVzFFsLSpaYwDXwWsKnCEtflAKdlqscJcUw= Date: Mon, 3 Jun 2019 10:12:51 +0530 From: Vinod Koul To: Kishon Vijay Abraham I Cc: Alan Mikhak , Gustavo Pimentel , "linux-pci@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "lorenzo.pieralisi@arm.com" , "arnd@arndb.de" , "gregkh@linuxfoundation.org" , "jingoohan1@gmail.com" , "bhelgaas@google.com" , "wen.yang99@zte.com.cn" , "kjlu@umn.edu" , "linux-riscv@lists.infradead.org" , "palmer@sifive.com" , "paul.walmsley@sifive.com" Subject: Re: [PATCH] PCI: endpoint: Add DMA to Linux PCI EP Framework Message-ID: <20190603044251.GS15118@vkoul-mobl> References: <1558650258-15050-1-git-send-email-alan.mikhak@sifive.com> <305100E33629484CBB767107E4246BBB0A6FAFFD@DE02WEMBXB.internal.synopsys.com> <305100E33629484CBB767107E4246BBB0A6FC308@DE02WEMBXB.internal.synopsys.com> <192e3a19-8b69-dfaf-aa5c-45c7087548cc@ti.com> <20190531050727.GO15118@vkoul-mobl> <20190531063247.GP15118@vkoul-mobl> <400a7c28-39b1-f242-7810-a1d38aa51446@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <400a7c28-39b1-f242-7810-a1d38aa51446@ti.com> User-Agent: Mutt/1.11.3 (2019-02-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Kishon, On 03-06-19, 09:54, Kishon Vijay Abraham I wrote: > right. For the endpoint case, drivers/pci/controller should register with the > dmaengine i.e if the controller has aN embedded DMA (I think it should be okay > to keep that in drivers/pci/controller itself instead of drivers/dma) and > drivers/pci/endpoint/functions/ should use dmaengine API's (Depending on the > platform, this will either use system DMA or DMA within the PCI controller). Typically I would prefer the driver to be part of drivers/dma. Would this be a standalone driver or part of the endpoint driver. In former case we can move to dmaengine for latter i guess it makes sense to stay in PCI Thanks -- ~Vinod