[PATCH] cpm: Describe multi-user ram in its own device node.

Kumar Gala galak at kernel.crashing.org
Wed Oct 3 00:43:58 EST 2007


On Sep 28, 2007, at 2:06 PM, Scott Wood wrote:

> The way the current CPM binding describes available multi-user (a.k.a.
> dual-ported) RAM doesn't work well when there are multiple free  
> regions,
> and it doesn't work at all if the region doesn't begin at the start of
> the muram area (as the hardware needs to be programmed with offsets  
> into
> this area).  The latter situation can happen with SMC UARTs on  
> CPM2, as its
> parameter RAM is relocatable, u-boot puts it at zero, and the  
> kernel doesn't
> support moving it.
>
> It is now described with a muram node, similar to QE.  The current CPM
> binding is sufficiently recent (i.e. never appeared in an official  
> release)
> that compatibility with existing device trees is not an issue.
>
> The code supporting the new binding is shared between cpm1 and  
> cpm2, rather
> than remain separated.  QE should be able to use this code as well,  
> once
> minor fixes are made to its device trees.
>
> Signed-off-by: Scott Wood <scottwood at freescale.com>

applied.

- k



More information about the Linuxppc-dev mailing list