public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Nuno Santos <nuno.m.santos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Linux timer interrupts not working when booting in normal-world
Date: Wed, 12 Sep 2012 16:01:45 +0200	[thread overview]
Message-ID: <505095C9.5000108@gmail.com> (raw)

Hi

I'm currently playing with the TrustZone technology on the Tegra2 
Harmony board, and my goal is to boot Linux not in the secure world (as 
it is in mainstream Linux), but in the normal world. However, in doing 
this, timer interrupts are not being triggered and the system halts 
early in the bootstrap stage. I'd like to ask if anyone could give me a 
hint for why this is happening.

So far I managed to set up the secure world environment so that we can 
invoke secure services through the SMC instruction from the normal 
world. This configuration step is done by u-boot, after which it enters 
normal world and jumps to Linux. To make sure that Linux can handle 
interrupts freely, in this setup phase, I assign the SCR register 0x3 
(EA, FIQ, and IRQ bit are clear, and AW and FW are set).

Assuming that this configuration is correct, one possible explanation 
for the absence of timer interrupts is that the Harmony board may impose 
some restrictions to the timer re-configuration in the normal world. 
Does anyone have an idea if there are such restrictions? If not, is 
there any other explanation for this? Is there some configuration step 
that I'm missing?

Thank you very much in advance!
--Nuno Santos

             reply	other threads:[~2012-09-12 14:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 14:01 Nuno Santos [this message]
     [not found] ` <505095C9.5000108-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-09-12 19:32   ` Linux timer interrupts not working when booting in normal-world Stephen Warren
2012-09-13  7:22 ` Antti P Miettinen

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=505095C9.5000108@gmail.com \
    --to=nuno.m.santos-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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