From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Simek Subject: Re: Remoteproc device-tree node description proposal Date: Fri, 29 Jun 2012 07:01:00 +0200 Message-ID: <4FED368C.1070201@monstr.eu> References: <4FEA974F.9050908@monstr.eu> Reply-To: monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Sender: "devicetree-discuss" To: Ohad Ben-Cohen Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org, Rob Herring , John Williams List-Id: devicetree@vger.kernel.org On 06/28/2012 09:54 AM, Ohad Ben-Cohen wrote: > On Wed, Jun 27, 2012 at 8:17 AM, Michal Simek wrote: >> Ohad: What properties are required by TI to describe firmware? >> I would like to add together all requirements and create any formal >> remoteproc description. > > I'm not so sure about this. > > The low level remoteproc driver is platform specific and may look > completely different on different platforms.. > > I suggest you go ahead and add DTS remoteproc support for your > platform, and when TI or others will get to it too, we will see if any > commonality is in place. ok. Thanks, Michal -- Michal Simek, Ing. (M.Eng) w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/ Microblaze U-BOOT custodian