From 9a01089df57313a47f7b79194af47579113f1d87 Mon Sep 17 00:00:00 2001 From: Madhukar Pappireddy Date: Thu, 25 Jul 2024 17:46:08 -0500 Subject: [PATCH] docs: fix discrepancies in value type of manifest fields In order to avoid the complexity of supporting value types smaller than u32 and avoid discrepancies for the various manifest fields among different projects, the value type for relevant fields are upgraded to u32. Change-Id: Ib033019b3b8c26bf4b8b50f89b7a6d1a772e5e51 Signed-off-by: Madhukar Pappireddy --- docs/components/ffa-manifest-binding.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/components/ffa-manifest-binding.rst b/docs/components/ffa-manifest-binding.rst index 7761fddc0..9ecdf061a 100644 --- a/docs/components/ffa-manifest-binding.rst +++ b/docs/components/ffa-manifest-binding.rst @@ -91,10 +91,10 @@ Partition Properties - 0x2: 64k - boot-order - - value type: + - value type: - A unique number amongst all partitions that specifies if this partition must be booted before others. The partition with the smaller number will be - booted first. + booted first. Highest vlue allowed for this field is 0xFFFF. - rx-tx-buffer - value type: "memory-regions" node @@ -103,7 +103,7 @@ Partition Properties The "compatible" must be the string "arm,ffa-manifest-rx_tx-buffer". - messaging-method [mandatory] - - value type: + - value type: - Specifies which messaging methods are supported by the partition, set bit means the feature is supported, clear bit - not supported: