Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp606171imu; Mon, 26 Nov 2018 15:42:22 -0800 (PST) X-Google-Smtp-Source: AFSGD/V2mZ1Lhk18adCOzn40mGLlgPRuc6luJD6M7JjfnbajkzyO8HQ2r3lHaCuBa7JlD2o5wk34 X-Received: by 2002:a63:7c13:: with SMTP id x19mr26567900pgc.45.1543275742252; Mon, 26 Nov 2018 15:42:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543275742; cv=none; d=google.com; s=arc-20160816; b=c1+NgFl3mhBY/ArvZxIrVMD/2MkRpFGbHlGzeqSW8SPtP1SWHgXBcj/MDlKY3IhmcJ ZSW8ZmkUHum36VbUqC1wylO+3H/4fjcFGZYUrV7JSGFfjTaeCj7mlL16KhNsOZcSBf6m NiW3xmDk1bSYRVbI3/CUqPYzsuO0Uub4hFLeYfTfZZZ5tnt/XsJQQlF6ZJv/WGDnHK2T tFJ6F9BovNK4AO6mYDMfNU3687fk/zQ8CRyMOMrzH5NNm2HMH7N/QEk6QpIdPFEHxPoB l/uBgOimvVtytBMMA809jT1FoXyrOUqir9erUvqVZ3EmFIp4BjlhbvvPq6ppMRWlEnQN k//A== 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=x7RZtOgX9knmDKpjBKJ614Zez1TLfj+ApGc+zCUX82E=; b=qplKWvm/JMLPFe6kBRuyqgvYj2VhdkrqZ4+hzLTyssCfbotKZTYdgFYpTpUvCrXPss y0CitKRDJ7Yur1GeQ1gmuzZL3h71rSYFiT4DQ9TtiH0z2MIonQrQWPn7WSsHATg8yrzU bSTKL7BdKHSoDVShKJAOAh+OUbPz1iPVyuB8tZV5sA7X8SBlwNDFj4OxOynaVGkqzDOw uwcxlQIkVtQ6wOekVFOWzTDFVGvwi+Yf2SHPs/7VT8V8xmNpdlwNx1n6Q0WfUVp/Cubr fy2wetjwvXTTd9i3imuS7Y0HSvehUXijwZyiZzC2IQ5qlAAPKPHJHbyDFgGlv8xB517z m7RQ== 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 p3si1624282plr.376.2018.11.26.15.42.06; Mon, 26 Nov 2018 15:42:22 -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 S1727862AbeK0KhK (ORCPT + 99 others); Tue, 27 Nov 2018 05:37:10 -0500 Received: from muru.com ([72.249.23.125]:55310 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727826AbeK0KhK (ORCPT ); Tue, 27 Nov 2018 05:37:10 -0500 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 3ED998068; Mon, 26 Nov 2018 23:41:21 +0000 (UTC) Date: Mon, 26 Nov 2018 15:41:16 -0800 From: Tony Lindgren To: David Lechner Cc: Roger Quadros , robh+dt@kernel.org, bcousson@baylibre.com, ssantosh@kernel.org, ohad@wizery.com, bjorn.andersson@linaro.org, s-anna@ti.com, nsekhar@ti.com, t-kristo@ti.com, nsaulnier@ti.com, jreeder@ti.com, m-karicheri2@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 01/17] dt-bindings: remoteproc: Add TI PRUSS bindings Message-ID: <20181126234116.GQ53235@atomide.com> References: <1542886753-17625-1-git-send-email-rogerq@ti.com> <1542886753-17625-2-git-send-email-rogerq@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * David Lechner [181126 21:14]: > I haven't looked into Tony's suggestion of using ti-sysc yet, so this may be a > moot point, but how will this work with AM18xx that does not have a PRUSS CFG > register? It seems to me that reg here should be the address and size of the > entire PRUSS IP block and the CFG register should be a syscon node or something > like that. The SoC specific wrapper IP is probably different on am18xx compared to omaps, it might be TIPB like on omap1? If am18xx has something simlar to omaps, there would be revision, sysconfig and sysstatus registers typically at offsets 0x00, 0x10 and 0x14. The wrapper IP code should be independent of the PRU code and just provide services to the PRU. For a minimal wrapper IP driver example that might work for am18xx see for drivers/usb/musb/musb_am335x.c. Regards, Tony