[PATCH master 3/4] Documentation: migration-guide: mention TF-A v2.14 compatibility

[Ahmad Fatoum <a.fatoum@pengutronix.de>]

While this is not caused by barebox, it's something worth considering when
doing a migration, so add a short explanation.

The patch that restores TF-A v2.14 SCMI clock compatibility will be
part of the next release.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 Documentation/migration-guides/migration-master.rst | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/Documentation/migration-guides/migration-master.rst b/Documentation/migration-guides/migration-master.rst
index 3fad2f1053c6..4a1de042d589 100644
--- a/Documentation/migration-guides/migration-master.rst
+++ b/Documentation/migration-guides/migration-master.rst
@@ -17,3 +17,14 @@ HABv4-enablement
 
 When the SRK hash is written, the corresponding fuse bank is now locked automatically.
 With that the ``IMX_SRK_HASH_WRITE_LOCK`` flag is removed.
+
+
+TF-A v2.14 compatibility
+------------------------
+
+TF-A v2.14 has `broken compatibility <https://lists.trustedfirmware.org/archives/list/tf-a@lists.trustedfirmware.org/thread/LKJVRDGRH7F73FWSTZC46I7IT3BRYQXC/>`_
+with SCMI consumers that implement only version 2.0 of the clock protocol.
+This includes barebox v2026.03.1, but also Linux v6.6.
+
+barebox v2026.04.0 is the first release that's compatible with both TF-A
+releases older than v2.14 as well as v2.14 itself.
-- 
2.47.3