From: Tony Lindgren <tony@atomide.com>
To: "Andrew F. Davis" <afd@ti.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP: Use ARM SMC Calling Convention when OP-TEE is available
Date: Tue, 17 Dec 2019 09:11:08 -0800 [thread overview]
Message-ID: <20191217171108.GY35479@atomide.com> (raw)
In-Reply-To: <8d5d098f-26cb-c436-ec7b-bed0ed0a9ced@ti.com>
* Andrew F. Davis <afd@ti.com> [191217 17:02]:
> On 12/17/19 10:07 AM, Tony Lindgren wrote:
> > * Andrew F. Davis <afd@ti.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
next prev parent reply other threads:[~2019-12-17 17:11 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 16:52 [PATCH] ARM: OMAP: Use ARM SMC Calling Convention when OP-TEE is available Andrew F. Davis
2019-11-18 16:52 ` Andrew F. Davis
2019-11-18 21:57 ` Tony Lindgren
2019-11-18 22:13 ` Andrew F. Davis
2019-11-18 22:13 ` Andrew F. Davis
2019-11-18 22:31 ` Tony Lindgren
2019-11-19 1:13 ` Andrew F. Davis
2019-11-19 1:13 ` Andrew F. Davis
2019-11-19 16:21 ` Tony Lindgren
2019-11-19 16:21 ` Tony Lindgren
2019-11-19 16:30 ` Tony Lindgren
2019-11-19 16:30 ` Andrew F. Davis
2019-11-19 16:30 ` Andrew F. Davis
2019-11-19 16:42 ` Tony Lindgren
2019-11-19 18:05 ` Tony Lindgren
2019-11-19 18:20 ` Andrew F. Davis
2019-11-19 18:20 ` Andrew F. Davis
2019-11-19 18:32 ` Tony Lindgren
2019-11-19 18:50 ` Andrew F. Davis
2019-11-19 18:50 ` Andrew F. Davis
2019-11-19 19:07 ` Tony Lindgren
2019-11-19 19:12 ` Andrew F. Davis
2019-11-19 19:12 ` Andrew F. Davis
2019-11-19 19:20 ` Tony Lindgren
2019-11-19 19:35 ` Andrew F. Davis
2019-11-19 19:35 ` Andrew F. Davis
2019-11-19 19:44 ` Tony Lindgren
2019-11-19 19:59 ` Andrew F. Davis
2019-11-19 19:59 ` Andrew F. Davis
2019-12-16 20:56 ` Andrew F. Davis
2019-12-16 20:56 ` Andrew F. Davis
2019-12-16 21:04 ` Tony Lindgren
2019-12-16 22:34 ` Andrew F. Davis
2019-12-16 22:34 ` Andrew F. Davis
2019-12-16 22:41 ` Tony Lindgren
2019-12-17 13:14 ` Andrew F. Davis
2019-12-17 13:14 ` Andrew F. Davis
2019-12-17 15:07 ` Tony Lindgren
2019-12-17 17:01 ` Andrew F. Davis
2019-12-17 17:01 ` Andrew F. Davis
2019-12-17 17:11 ` Tony Lindgren [this message]
2019-12-17 17:18 ` Tony Lindgren
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=20191217171108.GY35479@atomide.com \
--to=tony@atomide.com \
--cc=afd@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.