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=-6.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,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 04192C43381 for ; Thu, 7 Mar 2019 15:48:12 +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 C2FDC20652 for ; Thu, 7 Mar 2019 15:48:11 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="UQfj3qVN" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C2FDC20652 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=mdNsaNHhLfy5LYNwAg/CfjMHFdfCCLZPgUuhEbnzLlE=; b=UQfj3qVNXbo7RzjEKDgekWpNt ogqAMaBzMPoqoeWWPPx60mye7hUKP0evaZxum843hSMKFAPWU1bd7vjbTgbpTtIiOsWReHyOmyrPL kSPlIfDX9m5rMg05sp7Gt6Tp/+9CKI/JfA5+wpI0ctDcyR2Ib5Zv9uPpY5qYPuNYLLCzUUJgq2Xlc GIoLprIuDcWfGXBu8Mol0f4aWQfuPCD1rzM+GruSYPN4cc++tTIX78FY3aeakxgvEcOWN0Eyx9nna yJd79YN01IGzjDPddyTjlj0eBuX2+dBoH+WYWA+E+X9l/NulfngNxXplxX13O7DaDEyEG4oFBaQ45 bihjdlpcw==; 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 1h1vFc-00032Y-6B; Thu, 07 Mar 2019 15:48:04 +0000 Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1h1vFX-00031w-SF for linux-arm-kernel@lists.infradead.org; Thu, 07 Mar 2019 15:48:01 +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 relay3-d.mail.gandi.net (Postfix) with ESMTPSA id D0B9A6000D; Thu, 7 Mar 2019 15:47:55 +0000 (UTC) Date: Thu, 7 Mar 2019 16:47:55 +0100 From: Maxime Ripard To: Georgi Djakov Subject: Re: [PATCH v3 1/7] dt-bindings: interconnect: Add a dma interconnect name Message-ID: <20190307154755.5kgc7oh4b5bhg2fj@flea> References: <43eeca13733faefe62f9facc25b8e88f7e593f61.1549897336.git-series.maxime.ripard@bootlin.com> <553c987c-da9a-1f85-fb16-4b9fe17dd14b@linaro.org> <20190305155337.glfvgyddvnkv774m@flea> <0e72fbf7-b100-ddc5-3c19-32f71c37f76f@arm.com> <477995b0-9ac3-b6ca-f5f2-856e4af926f1@linaro.org> MIME-Version: 1.0 In-Reply-To: <477995b0-9ac3-b6ca-f5f2-856e4af926f1@linaro.org> User-Agent: NeoMutt/20180716 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190307_074800_208273_3C217E48 X-CRM114-Status: GOOD ( 22.40 ) 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="===============4356048265756220023==" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org --===============4356048265756220023== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="5pwrr5aoove3hn6w" Content-Disposition: inline --5pwrr5aoove3hn6w Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 07, 2019 at 05:15:20PM +0200, Georgi Djakov wrote: > Hi, >=20 > On 3/5/19 18:14, Robin Murphy wrote: > > On 05/03/2019 15:53, Maxime Ripard wrote: > >> 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 the > >>>> address translation using dma-ranges. > >>>> > >>>> However, some SoCs have devices that will perform DMA through > >>>> another bus, > >>>> with separate address translation rules. We therefore need to > >>>> express that > >>>> relationship, through the special interconnect name "dma". > >>>> > >>>> Signed-off-by: Maxime Ripard > >>>> --- > >>>> =A0 Documentation/devicetree/bindings/interconnect/interconnect.txt | > >>>> 3 +++ > >>>> =A0 1 file changed, 3 insertions(+) > >>>> > >>>> diff --git > >>>> a/Documentation/devicetree/bindings/interconnect/interconnect.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 strings sorted in the same > >>>> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 interconnect-names to mat= ch interconnect paths with > >>>> interconnect > >>>> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 specifier pairs. > >>>> =A0 +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Re= served interconnect names: > >>>> +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0 * dma: Path from the device to the main > >>>> memory of the system > >>> > >>> Bikeshed: As it's from the device to the main memory, maybe here we c= an > >>> 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 a= nd > >>> 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? > >=20 > > Hmm, yes, it's not like "dma" describes an actual source or destination > > either :/ >=20 > IIUC, it's a path (bus) that a dma device use to access some memory > (read or/and write). So i have used source-destination above more in the > sense of initiator-target or master-slave. My suggestion was just to > change the reserved interconnect name from "dma" to "dma-mem" or > "dma-memory". If dma is an issue in itself, maybe we can call it "device-memory" ? Maxime --=20 Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com --5pwrr5aoove3hn6w Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCXIE9KwAKCRDj7w1vZxhR xaLPAP97G3Gb2gq5LO0FvcRpl2j4snXLX7412+cYlkBa71I/oAD/YKCBpiqzTVGQ C7R1CnHQKyFoNDJhh+gnvnOCUSH9cgI= =/Ya7 -----END PGP SIGNATURE----- --5pwrr5aoove3hn6w-- --===============4356048265756220023== 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 --===============4356048265756220023==--