From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Osipenko Subject: Re: [RFC 2/2] dt-bindings: firmware: tegra186-bpmp: Document interconnects property Date: Mon, 27 Jan 2020 01:03:57 +0300 Message-ID: References: <20200114181519.3402385-1-thierry.reding@gmail.com> <20200114181519.3402385-2-thierry.reding@gmail.com> <7aefac6c-092c-b5a6-2fa6-e283d2147fc3@linaro.org> <20200120150605.GA712203@ulmo> <57c37b3c-1473-d444-db59-8c6650241188@gmail.com> <20200121141027.GE899558@ulmo> <83d94918-bc01-131b-924c-9750767d3b29@linaro.org> <20200121155432.GA912205@ulmo> <853bb7bd-8e04-38ac-d0d6-a958135a49be@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <853bb7bd-8e04-38ac-d0d6-a958135a49be-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Content-Language: en-US Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Thierry Reding , Georgi Djakov Cc: Rob Herring , Jon Hunter , linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-tegra@vger.kernel.org 27.01.2020 00:56, Dmitry Osipenko пишет: [snip] > Thinking a bit more about how to define the ICC, I'm now leaning to a > variant like this: > > interconnects = > <&mc TEGRA186_MEMORY_CLIENT_BPMP &emc TEGRA_ICC_EMEM>, > <&mc TEGRA186_MEMORY_CLIENT_BPMPR>, > <&mc TEGRA186_MEMORY_CLIENT_BPMPW>, > <&mc TEGRA186_MEMORY_CLIENT_BPMPDMAR>, > <&mc TEGRA186_MEMORY_CLIENT_BPMPDMAW>; I forgot that each ICC path should have SRC and DST, but you got the idea. This should be a more correct variant: <&mc TEGRA186_MEMORY_CLIENT_BPMPR &mc TEGRA_ICC_MC>, <&mc TEGRA186_MEMORY_CLIENT_BPMPW &mc TEGRA_ICC_MC>, <&mc TEGRA186_MEMORY_CLIENT_BPMPDMAR &mc TEGRA_ICC_MC>, <&mc TEGRA186_MEMORY_CLIENT_BPMPDMAW &mc TEGRA_ICC_MC>; > > interconnect-names = "dma-mem", "read", "write", "dma-read", "dma-write"; ...