diff options
author | Soby Mathew <soby.mathew@arm.com> | 2018-10-02 14:01:03 +0100 |
---|---|---|
committer | Soby Mathew <soby.mathew@arm.com> | 2018-10-02 14:03:37 +0100 |
commit | fad365dfc8b0cb4f085ad27e6294aae9645f8392 (patch) | |
tree | c8394c37befc60860ac01dab1390f6b33ec45b00 /docs/platform-compatibility-policy.rst | |
parent | 5eb48849c73b3c2c70adde5fae0cf6c6fb98c2ee (diff) | |
download | platform_external_arm-trusted-firmware-fad365dfc8b0cb4f085ad27e6294aae9645f8392.tar.gz platform_external_arm-trusted-firmware-fad365dfc8b0cb4f085ad27e6294aae9645f8392.tar.bz2 platform_external_arm-trusted-firmware-fad365dfc8b0cb4f085ad27e6294aae9645f8392.zip |
docs: Fixup filename and links to compatibility policy
Change-Id: I9d14faa7294578443233b84d5459fa7b62a30c07
Signed-off-by: Soby Mathew <soby.mathew@arm.com>
Diffstat (limited to 'docs/platform-compatibility-policy.rst')
-rw-r--r-- | docs/platform-compatibility-policy.rst | 45 |
1 files changed, 45 insertions, 0 deletions
diff --git a/docs/platform-compatibility-policy.rst b/docs/platform-compatibility-policy.rst new file mode 100644 index 000000000..b33c4e7c2 --- /dev/null +++ b/docs/platform-compatibility-policy.rst @@ -0,0 +1,45 @@ +TF-A Platform Compatibility Policy +====================================================== + + +.. section-numbering:: + :suffix: . + +.. contents:: + +-------------- + +Introduction +------------ + +This document clarifies the project's policy around compatibility for upstream +platforms. + +Platform compatibility policy +----------------------------- + +Platform compatibility is mainly affected by changes to Platform APIs (as +documented in the `Porting Guide`_), driver APIs (like the GICv3 drivers) or +library interfaces (like xlat_table library). The project will try to maintain +compatibility for upstream platforms. Due to evolving requirements and +enhancements, there might be changes affecting platform compatibility which +means the previous interface needs to be deprecated and a new interface +introduced to replace it. In case the migration to the new interface is trivial, +the contributor of the change is expected to make good effort to migrate the +upstream platforms to the new interface. + +The `Release information`_ documents the deprecated interfaces and the intended +release after which it will be removed. When an interface is deprecated, the +page must be updated to indicate the release after which the interface will be +removed. This must be at least 1 full release cycle in future. For non-trivial +interface changes, a `tf-issue`_ should be posted to notify platforms that they +should migrate away from the deprecated interfaces. Platforms are expected to +migrate before the removal of the deprecated interface. + +-------------- + +*Copyright (c) 2018, Arm Limited and Contributors. All rights reserved.* + +.. _Porting Guide: ./porting-guide.rst +.. _Release information: https://github.com/ARM-software/arm-trusted-firmware/wiki/TF-A-Release-information#2removal-of-deprecated-interfaces +.. _tf-issue: https://github.com/ARM-software/tf-issues/issues |