linux-kernel - Re: [PATCH] ARM: OMAP: Use ARM SMC Calling Convention when OP-TEE is available

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 17 Dec 2019 09:11:08 -0800
From:   Tony Lindgren <tony@...mide.com>
To:     "Andrew F. Davis" <afd@...com>
Cc:     Mark Rutland <mark.rutland@....com>, linux-omap@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ARM: OMAP: Use ARM SMC Calling Convention when OP-TEE is
 available

* Andrew F. Davis <afd@...com> [191217 17:02]:
> On 12/17/19 10:07 AM, Tony Lindgren wrote:
> > * Andrew F. Davis <afd@...com> [191217 13:14]:
> >> On 12/16/19 5:41 PM, Tony Lindgren wrote:
> >>> Please just add omap_early_initcall() to omap-secure.c while at it
> >>> to deal with this.
> >>
> >> omap_early_initcall()s are not called until after all the SMC calls have
> >> already happened.
> > 
> > Oh OK. Then let's just add omap_secure_init() that's called from
> > *_init_early() as late as possible. We will have more use for that
> > init later on too.
> > 
> 
> 
> You mean add a call to this omap_secure_init() to every boards init
> function?

Yes please. We also have some SoCs that need clocks enabled
and disabled for omap_smc2() so we can then use that to
intialize the clocks as needed.

Regards,

Tony