[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bb0c3855a121603232d022b4062752a6@mail.gmail.com>
Date: Tue, 25 Jan 2011 17:16:19 +0530
From: Santosh Shilimkar <santosh.shilimkar@...com>
To: Russell King - ARM Linux <linux@....linux.org.uk>,
sen wang <wangchendu@...il.com>
Cc: David Brown <davidb@...eaurora.org>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: RE: questions about arm trustzone
> -----Original Message-----
> From: linux-arm-kernel-bounces@...ts.infradead.org [mailto:linux-
> arm-kernel-bounces@...ts.infradead.org] On Behalf Of Russell King -
> ARM Linux
> Sent: Tuesday, January 25, 2011 3:57 PM
> To: sen wang
> Cc: David Brown; linux-kernel@...r.kernel.org; linux-arm-
> kernel@...ts.infradead.org
> Subject: Re: questions about arm trustzone
>
> On Tue, Jan 25, 2011 at 05:19:16PM +0800, sen wang wrote:
> > It seems linux run in the normal world, and the "scm.c" is the
> path
> > to the monitor mode.
> > where can I find the example code for monitor and secure world?
>
> OMAP also uses smc: arch/arm/mach-omap2/omap44xx-smc.S
>
> There's no interface defined for smc because it's highly vendor and
> implementation specific. It's just like a SWI (or svc) where it
> causes entry via a vector into a priviledged mode, which can be
> thought of being similar to a branch to a vector with a mode switch.
>
The code above won't give major details of how the monitor mode is
implemented. But as Russell said, it's pretty much vendor specific.
On OMAP, We have standard API interfaces to enter into monitor
world. One of the parameter denotes the kind of service, is
requested.
Regards,
Santosh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists