Received: by 2002:ac0:8c9a:0:0:0:0:0 with SMTP id r26csp5247895ima; Tue, 5 Feb 2019 08:36:55 -0800 (PST) X-Google-Smtp-Source: AHgI3Iail8ty+K9plCcjRWjYGrdn9T2oqaj99nIN5GcRLuOMFPMqtI5SlAWfZ9W2g62FJ+DIB9jS X-Received: by 2002:a63:c40a:: with SMTP id h10mr3679612pgd.131.1549384615547; Tue, 05 Feb 2019 08:36:55 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549384615; cv=none; d=google.com; s=arc-20160816; b=c7S1ayRUzFYW0qX/2aBdg366LlqyVng/d8/PqKyaofxdAnR+swkVKh4vMR5glGA72N MBBJV7WIOc8ZZlONP03wiY0iaddurGvNXJm7NYDZccg4Igl3avXd30m6L0jIIIYxZhUH xCLlAvNkCU+AWmdGaCy3WDveWNSo2fakjuE7otDNr8w3+Y73IfGNaEwcXQf7Fo9pquAh a5++SfQLEQm1zWrfCTaNYxysCGgyp36RioRQGu+8kFoosDYmwL8pNl8TnfRH0GCwrusN EabYxBBGqm+nNNJnbyMY/wB+IP+jjhw11K9NlMYfzbo9JxuT0Jji/WwFaNhwfoTULBew IG3A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=Qj3hl/Y2qe6nRa68fUanGUzP7P36QkCG8r1Ou9ikBjk=; b=oE08gyTvpW96OGlucGzrevsOJ7Z8eFRkPXYeo/7ItWb4CaoqrkIcTEjhE7JVxJxhRd UDEvALrtH701qX4uBCjRD80Kvwkk2nqH6HRjJFW/GJG2xdYuXo86NFu5/uJ8Sq1RWwwj IBF9CR+DdeoUQxk5LmHoU1P8t+QXgssOgLw9+XXCwXluHmEhXpo8sp5ySUAsypCOgAOG eFfQwreI1PRso1yYiGdqX5XPNMWOERlChyYOHmLGbwI9bcjE5ojvdBQBIZxjtNfrpe05 410h49vP67Sr1odsEhBBKP4QFhRIDYDcjPWX99NQhvfePUnyaRXA1WXZTXJgQIPjPHq0 zsyg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b91si3730922plb.11.2019.02.05.08.36.40; Tue, 05 Feb 2019 08:36:55 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729527AbfBEQTt (ORCPT + 99 others); Tue, 5 Feb 2019 11:19:49 -0500 Received: from muru.com ([72.249.23.125]:37710 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726887AbfBEQTt (ORCPT ); Tue, 5 Feb 2019 11:19:49 -0500 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 124E7809C; Tue, 5 Feb 2019 16:19:56 +0000 (UTC) Date: Tue, 5 Feb 2019 08:19:45 -0800 From: Tony Lindgren 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 Subject: Re: [PATCH v2 01/14] dt-bindings: remoteproc: Add TI PRUSS bindings 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 Content-Disposition: inline In-Reply-To: <124e9f09-fb60-071d-e2ba-ec6f7fb3955c@ti.com> User-Agent: Mutt/1.11.2 (2019-01-07) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@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