From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_PASS,USER_AGENT_NEOMUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5FFAFC43381 for ; Tue, 5 Mar 2019 15:54:06 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 2F1EB20684 for ; Tue, 5 Mar 2019 15:54:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="KBF2qGKl" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2F1EB20684 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=bootlin.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender:Content-Type:Cc: List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id: In-Reply-To:MIME-Version:References:Message-ID:Subject:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=GZdByF0j7M4s+jHgX0X4hpz/8E76F6g1joFqC/L5rNs=; b=KBF2qGKlkthkW+1mo45OJXgi1 nmsUXGu6fi90y/hMlWBFfgmpp4MobLl7okhxAl4HBVPRFB7HXecuC59qNYjDksqsc+SGp/P0dp58K QzARjaa0FjIeofAXdGfWIgeU/6U4HB+ukDZICnR0j6CwUtmfu6CgXTogYvjlgn2/0FpvL7f2BnwY1 K80aYdLb+t8GRp/pE93h2doTpbm12sNmiq1l7sVxdUeBSX2CSbwJmD7LD6mFDGOqjLONSm+t2hIin u1MSnu9BYTkvvxWMkgF/muxrMb1JzFyx3GqrlRx0++3tdgBmP+4DLDb9iIe7zUMlD3v2WYnpjDMh6 JxeY0ZTvw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1h1COH-0006le-CV; Tue, 05 Mar 2019 15:54:01 +0000 Received: from relay7-d.mail.gandi.net ([217.70.183.200]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1h1CO8-0006Xu-DR for linux-arm-kernel@lists.infradead.org; Tue, 05 Mar 2019 15:53:59 +0000 X-Originating-IP: 90.88.150.179 Received: from localhost (aaubervilliers-681-1-31-179.w90-88.abo.wanadoo.fr [90.88.150.179]) (Authenticated sender: maxime.ripard@bootlin.com) by relay7-d.mail.gandi.net (Postfix) with ESMTPSA id 5366D20006; Tue, 5 Mar 2019 15:53:38 +0000 (UTC) Date: Tue, 5 Mar 2019 16:53:37 +0100 From: Maxime Ripard To: Georgi Djakov Subject: Re: [PATCH v3 1/7] dt-bindings: interconnect: Add a dma interconnect name Message-ID: <20190305155337.glfvgyddvnkv774m@flea> References: <43eeca13733faefe62f9facc25b8e88f7e593f61.1549897336.git-series.maxime.ripard@bootlin.com> <553c987c-da9a-1f85-fb16-4b9fe17dd14b@linaro.org> MIME-Version: 1.0 In-Reply-To: <553c987c-da9a-1f85-fb16-4b9fe17dd14b@linaro.org> User-Agent: NeoMutt/20180716 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190305_075353_067097_A4025DC3 X-CRM114-Status: GOOD ( 20.68 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , devicetree@vger.kernel.org, Thomas Petazzoni , Arnd Bergmann , Robin Murphy , dri-devel@lists.freedesktop.org, Paul Kocialkowski , Chen-Yu Tsai , Rob Herring , Yong Deng , Frank Rowand , Dave Martin , linux-arm-kernel@lists.infradead.org Content-Type: multipart/mixed; boundary="===============7362003942655275190==" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org --===============7362003942655275190== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="cksvmpp7zr6b4jhf" Content-Disposition: inline --cksvmpp7zr6b4jhf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Fri, Mar 01, 2019 at 07:48:15PM +0200, Georgi Djakov wrote: > On 2/11/19 17:02, Maxime Ripard wrote: > > The current DT bindings assume that the DMA will be performed by the > > devices through their parent DT node, and rely on that assumption for t= he > > address translation using dma-ranges. > >=20 > > However, some SoCs have devices that will perform DMA through another b= us, > > with separate address translation rules. We therefore need to express t= hat > > relationship, through the special interconnect name "dma". > >=20 > > Signed-off-by: Maxime Ripard > > --- > > Documentation/devicetree/bindings/interconnect/interconnect.txt | 3 +++ > > 1 file changed, 3 insertions(+) > >=20 > > diff --git a/Documentation/devicetree/bindings/interconnect/interconnec= t.txt b/Documentation/devicetree/bindings/interconnect/interconnect.txt > > index 5a3c575b387a..e69fc2d992c3 100644 > > --- a/Documentation/devicetree/bindings/interconnect/interconnect.txt > > +++ b/Documentation/devicetree/bindings/interconnect/interconnect.txt > > @@ -51,6 +51,9 @@ interconnect-names : List of interconnect path name s= trings sorted in the same > > interconnect-names to match interconnect paths with interconnect > > specifier pairs. > > =20 > > + Reserved interconnect names: > > + * dma: Path from the device to the main memor= y of the system >=20 > Bikeshed: As it's from the device to the main memory, maybe here we can > also denote this my calling the path dma-mem or dma-memory. For other > paths, we are trying to mention both the source and the destination and > maybe it would be good to be consistent although this is special one. I'm not sure I understand what you mean. You'd like two interconnect names, one called dma-memory, and one memory-dma? Thanks! Maxime --=20 Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com --cksvmpp7zr6b4jhf Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCXH6bgQAKCRDj7w1vZxhR xThCAQD6PHnyKDoKrnJEYd0OjuOIJThkCCKFBjXXscGqXBnrggD/eFCzZGMEyleu iG1PCRKn4Bp6bl8xBlfk3QB8wSEBWAw= =KfvE -----END PGP SIGNATURE----- --cksvmpp7zr6b4jhf-- --===============7362003942655275190== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel --===============7362003942655275190==--