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=-2.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 0FCEEC432C2 for ; Wed, 25 Sep 2019 09:15:42 +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 D424420673 for ; Wed, 25 Sep 2019 09:15:41 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="tXVuIWJ1"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="LUAdHLEB" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D424420673 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org 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=e+4iuduuklbXYwRLczvEQ1wRDAuAbdm/o0DjxrHTYQM=; b=tXVuIWJ1DSBXv0xZSgZYbYM7U VbiTPpQriwaxYQWkZyDtQyccUVwveU+OcUfPdodMGDGPJSgcHm1hL7on+bdQ80sSZpiWaJ/Jv1EJN 9aU0tTWvVJ+10Ecyml55C3A2Hkiiir4s48mgzAqRTPUA7xeWi3jBdAzc9ppVElEdZXzfcnCd3bgCq J0mCRY3xliiuelYpTlIERBfF28s973XMoMAQLt9RUI5CzFRLQu28/RX14x9IEk3/y6iPsLlktXq+D zphDBmaPdpvm4Wmnes4hg/b3aPICUEieMctd+zkdbx7TapK8X4LU9/rarUKsIWwFou2zGU2RZGfPX BnxU8FmcQ==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.2 #3 (Red Hat Linux)) id 1iD3OW-0003ik-7j; Wed, 25 Sep 2019 09:15:32 +0000 Received: from mail.kernel.org ([198.145.29.99]) by bombadil.infradead.org with esmtps (Exim 4.92.2 #3 (Red Hat Linux)) id 1iD3OR-0003iF-9Q for linux-arm-kernel@lists.infradead.org; Wed, 25 Sep 2019 09:15:29 +0000 Received: from localhost (lfbn-1-10718-76.w90-89.abo.wanadoo.fr [90.89.68.76]) (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 C17A020673; Wed, 25 Sep 2019 09:15:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1569402925; bh=Z2Uag+DwW909ph/1HOySpUCCmNKluWCbwO7QFKK6F8E=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=LUAdHLEB0Njr3vPkEeYEnn9UJ65aNeraXjCw8vvFf6X7fzKvIP2kobELTTOGaz+Ai F/6Pk5OGh6G++u9o8W46kH+kpymk6XLNk9oIVvO3P5dgTlNDCS89SC0ZdQYzlIooNS HHynK47zEbah8oMWrSK4ChXXBYoripfPPxhyqVt0= Date: Wed, 25 Sep 2019 11:15:22 +0200 From: Maxime Ripard To: Stephen Boyd Subject: Re: [RFC PATCH] interconnect: Replace of_icc_get() with icc_get() and reduce DT binding Message-ID: <20190925091522.jf5q2jdo6njfkxto@gilmour> References: <20190925054133.206992-1-swboyd@chromium.org> MIME-Version: 1.0 In-Reply-To: <20190925054133.206992-1-swboyd@chromium.org> User-Agent: NeoMutt/20180716 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190925_021527_837987_48B3C845 X-CRM114-Status: GOOD ( 18.21 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: devicetree@vger.kernel.org, linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org, David Dai , linux-kernel@vger.kernel.org, Evan Green , Bjorn Andersson , Rob Herring , Georgi Djakov , linux-arm-kernel@lists.infradead.org Content-Type: multipart/mixed; boundary="===============5486269731441519147==" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org --===============5486269731441519147== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="aomtcuidegtr2wsv" Content-Disposition: inline --aomtcuidegtr2wsv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi Stephen, On Tue, Sep 24, 2019 at 10:41:33PM -0700, Stephen Boyd wrote: > The DT binding could also be simplified somewhat. Currently a path needs > to be specified in DT for each and every use case that is possible for a > device to want. Typically the path is to memory, which looks to be > reserved for in the binding with the "dma-mem" named path, but sometimes > the path is from a device to the CPU or more generically from a device > to another device which could be a CPU, cache, DMA master, or another > device if some sort of DMA to DMA scenario is happening. Let's remove > the pair part of the binding so that we just list out a device's > possible endpoints on the bus or busses that it's connected to. > > If the kernel wants to figure out what the path is to memory or the CPU > or a cache or something else it should be able to do that by finding the > node for the "destination" endpoint, extracting that node's > "interconnects" property, and deriving the path in software. For > example, we shouldn't need to write out each use case path by path in DT > for each endpoint node that wants to set a bandwidth to memory. We > should just be able to indicate what endpoint(s) a device sits on based > on the interconnect provider in the system and then walk the various > interconnects to find the path from that source endpoint to the > destination endpoint. The dma-mem name is used by the OF core to adjust the mapping of the devices as well. So, any solution needs to be generic (or provide a generic helper). Maxime --aomtcuidegtr2wsv Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCXYswKgAKCRDj7w1vZxhR xe8UAQC3EqIcKg882wsQj/TdlIO/sf9HoBIDnQnVNJ2t2kaPsAD/Qsa+D9ZQUlKc qhYx4agifh1/WXVN4H+Wb39VO4vx5wk= =Z0s1 -----END PGP SIGNATURE----- --aomtcuidegtr2wsv-- --===============5486269731441519147== 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 --===============5486269731441519147==--