[meta-xilinx] remoteproc resource table TYPE_MMU entries

[Edward Wingate]

On Wed, Oct 14, 2015 at 11:53 PM, Magnus Olsson <Mago at hms.se> wrote:
> It is the responsibility of the remoteproc app to iterate through its own resource table, and for
> each RSC_MMU entry, configure the MMU of CPU #1 accordingly. It is recommended that you
> lock down the address space in such way that the application cannot access peripherals other
> than those explicitly unlocked by RSC_MMU. This will provide a type of safety-net for the entire
> system, and to some degree ensure mutual exclusion for peripherals between Linux and your
> app.

Magnus, Thanks for the clear explanation.  In my case, most
peripherals will actually be used by the remote processor (CPU1).  Is
it possible to do the equivalent lockdown for Linux on CPU0?  Would
simply excluding the peripheral from the DTB or declaring it "invalid"
do the trick?