From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH v2 01/14] dt-bindings: remoteproc: Add TI PRUSS bindings Date: Tue, 5 Feb 2019 08:19:45 -0800 Message-ID: <20190205161945.GS5720@atomide.com> References: <1549290167-876-1-git-send-email-rogerq@ti.com> <1549290167-876-2-git-send-email-rogerq@ti.com> <20190204163312.GI5720@atomide.com> <5C5959DB.2090608@ti.com> <5C59AEA3.1080400@ti.com> <124e9f09-fb60-071d-e2ba-ec6f7fb3955c@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <124e9f09-fb60-071d-e2ba-ec6f7fb3955c@ti.com> Sender: linux-kernel-owner@vger.kernel.org To: Murali Karicheri Cc: Roger Quadros , s-anna@ti.com, ohad@wizery.com, bjorn.andersson@linaro.org, david@lechnology.com, nsekhar@ti.com, t-kristo@ti.com, nsaulnier@ti.com, jreeder@ti.com, woods.technical@gmail.com, linux-omap@vger.kernel.org, linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org List-Id: devicetree@vger.kernel.org * Murali Karicheri [190205 16:13]: > On 02/05/2019 10:41 AM, Roger Quadros wrote: > > What I'm suggesting here is that kernel remoteproc driver should have nothing to do > > with the other PRU's data RAM. > > > > The application driver if needs both PRUs then it can obviously access both DRAMs > > as it has a phandle to both PRUs. > > > That should be fine. That sounds good to me too. For dts, yeah please allocate the resources for the modules where the resources belong to on the PRUSS internal interconnect :) Devices can move around on the interconnect between SoCs and the modules can get swapped or added. Regards, Tony