On Wed, Oct 16, 2013 at 06:46:58PM +0100, Mark Brown wrote:
On Wed, Oct 16, 2013 at 06:33:52PM +0200, Lars-Peter Clausen wrote:
On 10/16/2013 01:58 PM, Mark Brown wrote:
Also is iram the best name? It makes me think of the dedicated fast instruction RAM that some processors have. sram perhaps (for static RAM)?
Using IRAM (internal SRAM) for this seems to be quite popular (`grep IRAM arch/arm -r`). Existing devicetree bindings also seem to use the 'iram' property to refer to the on-chip SRAM (Documentation/devicetree/bindings/media/coda.txt). It's probably a good idea to stay consistent with the existing bindings.
Oh, I wonder when that changed - it always used to get called SRAM (or TCM when that was what was used).
Do I still need to change the name to SRAM? I think both name make sense to me. I use IRAM just because using different name for phandle and macro/functions might confuse people when reviewing the patch. But it looks like IRAM is still not the perfect choice.
Looking forward to your reply, Nicolin Chen