From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC PATCH] ARM: Make a compile trustzone conditionally
Date: Mon, 18 Jun 2012 14:10:39 +0000 [thread overview]
Message-ID: <201206181410.39267.arnd@arndb.de> (raw)
In-Reply-To: <CAH9JG2X=15G6wDX5SGJkDEVohkQQkzfBoL3Qv7HVuBUMqYnwRg@mail.gmail.com>
On Monday 18 June 2012, Kyungmin Park wrote:
> > I would prefer to see this handled by using the smp_ops patchset that
> > Marc Zyngier has been posting instead, replacing the boot_secondary
> > function pointer during early boot depending on whether trustzone is
> > enabled or not.
> I understand your request, but it's not only boot_secondary but also
> exynos pm common code and so on.even more it's used at devfreq to
> adjust the RAM bus timings.
>
> Now these files are covered.
>
Would it help to have a trustzone_ops structure with pointers to
functions if needed, similar to but separate from smp_ops?
Instead of checking for trustzone_enabled() in each place where
we call into smc, we can have a generic implementation that
we call for the disabled case, and provide a vendor specific
version of that struct with functions that call into smp
where necessary.
Arnd
next prev parent reply other threads:[~2012-06-18 14:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 5:15 [RFC PATCH] ARM: Make a compile trustzone conditionally Kyungmin Park
2012-06-18 0:58 ` Kyungmin Park
2012-06-18 1:10 ` Olof Johansson
2012-06-18 4:37 ` Kyungmin Park
2012-06-18 14:10 ` Arnd Bergmann [this message]
2012-06-19 6:50 ` Kyungmin Park
2012-06-20 11:14 ` Arnd Bergmann
2012-06-20 14:41 ` Dave Martin
2012-06-20 16:01 ` Arnd Bergmann
2012-06-20 1:22 ` Stephen Boyd
2012-06-20 9:43 ` Will Deacon
2012-06-20 10:51 ` Bindings for SMC/HVC firmware interfaces on ARM (Re: [RFC PATCH] ARM: Make a compile trustzone conditionally) Dave Martin
2012-06-20 15:14 ` Rob Herring
2012-06-20 15:34 ` Dave Martin
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=201206181410.39267.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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