platform-compatibility-policy.rst 1.61 KB
Newer Older
Paul Beesley's avatar
Paul Beesley committed
1
2
Platform Compatibility Policy
=============================
3
4
5
6
7
8
9
10
11
12
13

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
14
documented in the :ref:`Porting Guide`), driver APIs (like the GICv3 drivers) or
15
16
17
18
19
20
21
22
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.

23
The deprecated interfaces are listed inside :ref:`Release Processes` as well as
24
25
26
27
28
29
30
the release after which each one 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, an email should be sent out to the `TF-A
public mailing list`_ to notify platforms that they should migrate away from the
deprecated interfaces. Platforms are expected to migrate before the removal of
the deprecated interface.
31
32
33

--------------

34
*Copyright (c) 2018-2019, Arm Limited and Contributors. All rights reserved.*
35

36
.. _TF-A public mailing list: https://lists.trustedfirmware.org/mailman/listinfo/tf-a