Received: by 10.223.185.116 with SMTP id b49csp2916794wrg; Mon, 5 Mar 2018 10:41:59 -0800 (PST) X-Google-Smtp-Source: AG47ELu1WUIj6h6vmKosXQiAYnaU668JsvHoeAxqq7TNhm9kEvof2wV1ZiyZc1O8kcy0U4MNG0wR X-Received: by 10.99.175.8 with SMTP id w8mr12725992pge.390.1520275319389; Mon, 05 Mar 2018 10:41:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520275319; cv=none; d=google.com; s=arc-20160816; b=i65oInif7/vF8O2Tr2l0aQYl1JY5+dYN4Y6KiGUWp3EXbz5AxTulb6FG4Hp6v8GJEO Ar6pRRJpDgPbtIs62AYqQ9r/7n9ytm9riftkMHzbDyEwbhaYo/Zlf9yyHqCkoBLA4iiE 736D0Hx2v0S4E6LTCuvZOJYO5t/rnuh1/WiTdF1HEUWJRPgc0kGQL/3CYJrigdmGXiyh ZG1yk8snLlFYRgzi8OyX9ZSJBoBLZuefAtNgmjNklmkAUOLuu6o3W966XL4qQK3GrxRx tHd7sMAIM7JpmHr8HsrVMu//GIJekW7oRb7BAM5Wwl8kid3qMy0N/YaAks9WXJGS33WP K3Mg== 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:arc-authentication-results; bh=z5NPp+YWU4jMKBUAMKvrsaxARCTdTQ40an47xKUlDpk=; b=exrq+hmpz1y5n49JMl1bceu91Qbd30rn9pg3rKVgDEkC3LEx4K39b9HwWlhs6aKQAN QwQ1HECgCYurd8addO6hIc+9CUJohSgS3YE0tNRBqr+90hg/un2s4gtzXiD7xj+JB55s LyH/qkM+CwnsKrC6Zj8TAEcJcWD2jWXwhEeOsddytKaAulqOcFusMqPtx5m3Cz8i3mYd qEo4vPr/UtNkj544aeox6Q/clOVSiOxYDPBa3yUYSo9DQHI2v8WAtEXnME6f62WcsIO3 92Cjsd2CzbTbxGxuy3foFVHzxSu1G7ZK780jtXt7wWw3z7DTQvn7NOs5TfVO5XBbLztb PGpw== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r12-v6si9989118plj.290.2018.03.05.10.41.45; Mon, 05 Mar 2018 10:41:59 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752630AbeCESjl (ORCPT + 99 others); Mon, 5 Mar 2018 13:39:41 -0500 Received: from verein.lst.de ([213.95.11.211]:48885 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751311AbeCESjk (ORCPT ); Mon, 5 Mar 2018 13:39:40 -0500 Received: by newverein.lst.de (Postfix, from userid 2407) id C025F68DE4; Mon, 5 Mar 2018 19:39:38 +0100 (CET) Date: Mon, 5 Mar 2018 19:39:38 +0100 From: Christoph Hellwig To: Robin Murphy Cc: Christoph Hellwig , Nipun Gupta , will.deacon@arm.com, mark.rutland@arm.com, catalin.marinas@arm.com, iommu@lists.linux-foundation.org, robh+dt@kernel.org, m.szyprowski@samsung.com, gregkh@linuxfoundation.org, joro@8bytes.org, leoyang.li@nxp.com, shawnguo@kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linuxppc-dev@lists.ozlabs.org, bharat.bhushan@nxp.com, stuyoder@gmail.com, laurentiu.tudor@nxp.com Subject: Re: [PATCH 5/6] dma-mapping: support fsl-mc bus Message-ID: <20180305183938.GB20086@lst.de> References: <1520260166-29387-1-git-send-email-nipun.gupta@nxp.com> <1520260166-29387-6-git-send-email-nipun.gupta@nxp.com> <20180305150814.GA15918@lst.de> <7b4f9972-6aaa-fc9d-3854-d48b19a8051c@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7b4f9972-6aaa-fc9d-3854-d48b19a8051c@arm.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 05, 2018 at 03:48:32PM +0000, Robin Murphy wrote: > Unfortunately for us, fsl-mc is conceptually rather like PCI in that it's > software-discoverable and the only thing described in DT is the bus "host", > thus we need the same sort of thing as for PCI to map from the child > devices back to the bus root in order to find the appropriate firmware > node. Worse than PCI, though, we wouldn't even have the option of > describing child devices statically in firmware at all, since it's actually > one of these runtime-configurable "build your own network accelerator" > hardware pools where userspace gets to create and destroy "devices" as it > likes. I really hate the PCI special case just as much. Maybe we just need a dma_configure method on the bus, and move PCI as well as fsl-mc to it.