diff options
| author | Paul Beesley <paul.beesley@arm.com> | 2019-09-16 11:29:03 +0000 |
|---|---|---|
| committer | Manish Pandey <manish.pandey2@arm.com> | 2019-12-20 16:03:02 +0000 |
| commit | 3f3c341ae58321ec1b86162916d80b6db9187759 (patch) | |
| tree | 827da02849f34af25a043b72170ce50dc2d36a57 /docs | |
| parent | b8e17967bb4eaf0a28870ecb3f3b45a1e5479fe0 (diff) | |
| download | platform_external_arm-trusted-firmware-3f3c341ae58321ec1b86162916d80b6db9187759.tar.gz platform_external_arm-trusted-firmware-3f3c341ae58321ec1b86162916d80b6db9187759.tar.bz2 platform_external_arm-trusted-firmware-3f3c341ae58321ec1b86162916d80b6db9187759.zip | |
Remove dependency between SPM_MM and ENABLE_SPM build flags
There are two different implementations of Secure Partition
management in TF-A. One is based on the "Management Mode" (MM)
design, the other is based on the Secure Partition Client Interface
(SPCI) specification. Currently there is a dependency between their
build flags that shouldn't exist, making further development
harder than it should be. This patch removes that
dependency, making the two flags function independently.
Before: ENABLE_SPM=1 is required for using either implementation.
By default, the SPCI-based implementation is enabled and
this is overridden if SPM_MM=1.
After: ENABLE_SPM=1 enables the SPCI-based implementation.
SPM_MM=1 enables the MM-based implementation.
The two build flags are mutually exclusive.
Note that the name of the ENABLE_SPM flag remains a bit
ambiguous - this will be improved in a subsequent patch. For this
patch the intention was to leave the name as-is so that it is
easier to track the changes that were made.
Change-Id: I8e64ee545d811c7000f27e8dc8ebb977d670608a
Signed-off-by: Paul Beesley <paul.beesley@arm.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/getting_started/build-options.rst | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/docs/getting_started/build-options.rst b/docs/getting_started/build-options.rst index 731b87624..87ce94eb4 100644 --- a/docs/getting_started/build-options.rst +++ b/docs/getting_started/build-options.rst @@ -235,8 +235,9 @@ Common build options The default is 1 but is automatically disabled when the target architecture is AArch32. -- ``ENABLE_SPM`` : Boolean option to enable the Secure Partition Manager (SPM). - Refer to :ref:`Secure Partition Manager` for more details about +- ``ENABLE_SPM`` : Boolean option to enable the SPCI-based Secure Partition + Manager (SPM) implementation. + Refer to the :ref:`Secure Partition Manager` guide for more details about this feature. Default is 0. - ``ENABLE_SVE_FOR_NS``: Boolean option to enable Scalable Vector Extension @@ -507,6 +508,9 @@ Common build options firmware images have been loaded in memory, and the MMU and caches are turned off. Refer to the "Debugging options" section for more details. +- ``SPM_MM`` : Boolean option to enable the Management Mode (MM)-based Secure + Partition Manager (SPM) implementation. The default value is ``0``. + - ``SP_MIN_WITH_SECURE_FIQ``: Boolean flag to indicate the SP_MIN handles secure interrupts (caught through the FIQ line). Platforms can enable this directive if they need to handle such interruption. When enabled, |