CPU_METHOD_OF_DECLARE() with Linux as non-secure OS

Mason [off-list ref] writes:

On 29/10/2015 19:04, M?ns Rullg?rd wrote:

quoted

There's also something wrong with the L2C-310 aux control register
setting.  The SMC call ID from OMAP (0x109) which is also used in some
Sigma code I found somewhere doesn't seem to do anything, so the
register is left at the value set by the secure boot code.  Perhaps you
can check with your firmware guy if there's another way of writing that
register.

IIRC, only debug firmware allows writes to L2 AUXCTRL (after filtering
some of the bits out), while production firmware ignores them completely.

IME, the smc handler should default to return ENOTSUP; that way, when
a syscall disappears due to ifdef-ery, the caller gets a meaningful
answer.

We just had an interesting internal discussion about L2 AUXCTRL.
For my education, what value would you like to write to AUXCTRL? :-)

The best value to use depends on the workload, so it would be nice to be
able to control all the purely performance related bits.  I see no
possible benefit in restricting the non-secure kernel from writing
these.

-- 
M?ns Rullg?rd
mans at mansr.com