From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: CPU_METHOD_OF_DECLARE() with Linux as non-secure OS
Date: Fri, 30 Oct 2015 21:12:26 +0100 [thread overview]
Message-ID: <5633CF2A.4040504@free.fr> (raw)
In-Reply-To: <yw1xeggdd007.fsf@unicorn.mansr.com>
On 29/10/2015 19:04, M?ns Rullg?rd wrote:
> 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? :-)
Regards.
next prev parent reply other threads:[~2015-10-30 20:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 12:36 CPU_METHOD_OF_DECLARE() with Linux as non-secure OS Mason
2015-10-29 4:22 ` Rob Herring
2015-10-29 16:03 ` Måns Rullgård
2015-10-29 17:50 ` Mason
2015-10-29 18:04 ` Måns Rullgård
2015-10-30 20:12 ` Mason [this message]
2015-10-31 15:41 ` Måns Rullgård
2015-11-02 10:10 ` Mason
2015-11-02 13:31 ` Måns Rullgård
2015-11-02 10:17 ` Russell King - ARM Linux
2015-11-02 11:55 ` Mason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5633CF2A.4040504@free.fr \
--to=slash.tmp@free.fr \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).