[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181126234116.GQ53235@atomide.com>
Date: Mon, 26 Nov 2018 15:41:16 -0800
From: Tony Lindgren <tony@...mide.com>
To: David Lechner <david@...hnology.com>
Cc: Roger Quadros <rogerq@...com>, robh+dt@...nel.org,
bcousson@...libre.com, ssantosh@...nel.org, ohad@...ery.com,
bjorn.andersson@...aro.org, s-anna@...com, nsekhar@...com,
t-kristo@...com, nsaulnier@...com, jreeder@...com,
m-karicheri2@...com, woods.technical@...il.com,
linux-omap@...r.kernel.org, linux-remoteproc@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 01/17] dt-bindings: remoteproc: Add TI PRUSS bindings
* David Lechner <david@...hnology.com> [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
Powered by blists - more mailing lists