diff options
authorJeremy Linton <jeremy.linton@arm.com>2021-01-26 22:42:03 -0600
committerManish Pandey <manish.pandey2@arm.com>2021-05-25 14:49:15 +0200
commit2d31cb079b28bb2bc52572c328c840129670b8b5 (patch)
parent1cdf1eb875ec8622e94493c0a99d21f2e0adeac8 (diff)
TF-A: Document SMC_PCI_SUPPORT option
Add some basic documentation and pointers for the SMCCC PCI build options. Signed-off-by: Jeremy Linton <jeremy.linton@arm.com> Change-Id: Ia35f31d15066ea74135367cde2dce2f26e6ab31e
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/getting_started/build-options.rst b/docs/getting_started/build-options.rst
index 2c3cd6bb50..99fc21db32 100644
--- a/docs/getting_started/build-options.rst
+++ b/docs/getting_started/build-options.rst
@@ -579,6 +579,11 @@ Common build options
``BL31_NOBITS_LIMIT``. When the option is ``0`` (the default), NOBITS
sections are placed in RAM immediately following the loaded firmware image.
+- ``SMC_PCI_SUPPORT``: This option allows platforms to handle PCI configuration
+ access requests via a standard SMCCC defined in `DEN0115`_. When combined with
+ UEFI+ACPI this can provide a certain amount of OS forward compatibility
+ with newer platforms that aren't ECAM compliant.
- ``SPD``: Choose a Secure Payload Dispatcher component to be built into TF-A.
This build option is only valid if ``ARCH=aarch64``. The value should be
the path to the directory containing the SPD source, relative to
@@ -849,3 +854,6 @@ commands can be used:
*Copyright (c) 2019-2021, Arm Limited. All rights reserved.*
+.. _DEN0115: https://developer.arm.com/docs/den0115/latest