The docs/index.rst file is the new landing page / entry point
for reading the docs so the top-level content needs to be copied
there.

The existing content in readme.rst cannot be modified to point to
the new page until the hosted copy of the docs has gone live (in
order to have a working URL).

Change-Id: Ifa9e65d463c2887bbd53f7224aa803796aeec68f
Signed-off-by: Paul Beesley <paul.beesley@arm.com>
Signed-off-by: Jimmy Brisson <jimmy.brisson@arm.com>

Signed-off-by: Madhukar Pappireddy <madhukar.pappireddy@arm.com>
Change-Id: Ide56f234752ede1d998bdebd31bf39e0ac7105f9

The issue with the test has been fixed with the TF-A patch:
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/3778


so re-enable it.

Signed-off-by: Zelalem <zelalem.aweke@arm.com>
Change-Id: Ie394b596c7da504c74c684af3ef5f6065a05eef9

For pre-Armv8.4 platform, the supported model is that SPMC runs at
S-EL1. The candidate is OP-TEE with SPCI protocol adaptation. This patch
performs a version check through direct messaging and determines if
OP-TEE runs as SPMC by checking version responses. If this does not
match, then it assumes SPMC runs at S-EL2 with two Cactus instances
running at S-EL1.

Signed-off-by: Olivier Deprez <olivier.deprez@arm.com>
Change-Id: I34194b6e8b3d447a25f2153bbac1be2631cd7a5e

* changes:
  cactus: generate JSON file required by TF-A
  tftf: re-introduce spm tests in the flow
  cactus: update sample manifest to SPCI Beta1 format
  cactus: add symbols relocation fixup
  cactus: update build options and memory map to make it PIE
  cactus: update to SPCI Beta1 and add sample direct messaging test
  tftf: SPCI Beta1 add direct messaging test
  tftf: update SPCI svc header to latest Beta1 spec
  tftf: provide hvc conduit facility

Manish Pandey2 authored Mar 16, 2020 and Olivier Deprez committed Mar 23, 2020

Generate JSON file which is being passed as "SP_LAYOUT_FILE" build
parameter to TF-A build.
Two instances of cactus is used to demonstrate functioning of multiple
SP's. cactus-secondary dts is same as cactus dts except for UUID and
load address.

Signed-off-by: Manish Pandey <manish.pandey2@arm.com>
Change-Id: Ib6d8f7d5d4894495754da0ce39f663263eeb182f

Signed-off-by: Olivier Deprez <olivier.deprez@arm.com>
Change-Id: I3a80e023c71426605abb13303d466a9b93f3123e

Notice, the dtb generation wrapper script had a provision
to automatically generate an "extra" memory description section.
This will be revisited later when SP boot time memory region
is implemented in SPM.

Signed-off-by: Olivier Deprez <olivier.deprez@arm.com>
Change-Id: I4fb9e23004871d74eee4a1d1f4be0826695e3e9f

Signed-off-by: Olivier Deprez <olivier.deprez@arm.com>
Change-Id: Ibde8aadecf6ae6c320d01ee2acab9c3c8db3859d

Signed-off-by: Olivier Deprez <olivier.deprez@arm.com>
Change-Id: I9287361d2a4c81954fae715fef6ba5cc57cc10e0

The scenario is: TFTF (acting as an "hypervisor" at NS-EL2) sends a
direct message request to an SP targetting its SP ID. SPMD/SPMC relays
the message down to SP. SP extracts the message payload, amends it and
sends a direct message response to TFTF that SPMC/SPMD relay back to
TFTF. This sample SP can be instantiated into multiple SPs. The early
main entry flow discriminates the first VM from other secondary VMs by
getting its running id through SPCI_ID_GET. The SP runs an infinite
message loop and waits for a new message by calling SPCI_MSG_WAIT.
Notice SPCI_MSG_WAIT is also the hint to SPMD that the SP initialized
properly. About logging, only PVM for now has direct access to UART.
2nd VMs must use the debug log hypervisor call.

Signed-off-by: Olivier Deprez <olivier.deprez@arm.com>
Change-Id: I001261c3f54e0bc217e43fca6812d6cda1ac4430

This patch strips out former SPCI Alpha sample test code. Removing SPRT
references will be done in another coming patch. Version check is adapted
to SPCI Beta1. Version is now returned in x2.

The first test is a direct messaging test using SPCI_MSG_SEND_DIRECT_REQ
targetting a bare-metal cactus SP. TFTF expects a response from the SP
returning with SPCI_MSG_SEND_DIRECT_RESP.

Note: this patch also provides an initial SPCI_RUN interface. This API
may not be used in the mid-term because VM to SP communication is supposed
to be done only through direct messaging. Though the SPM boot-up for now
is only launching the first SP in the list of declared SP in SPMC manifest.
In order to make 2nd-VM ready, TFTF has to "boot-up" the SP through a single
SPCI_RUN invocation till it reaches SPCI_MSG_WAIT in the SP. Once SPM
implements boot up through all SPs, this SPCI_RUN invocation will no longer
be required.

Signed-off-by: Olivier Deprez <olivier.deprez@arm.com>
Change-Id: I141abd3e348409b3d34a911d0552570f49e85846

Signed-off-by: Olivier Deprez <olivier.deprez@arm.com>
Change-Id: I5b70debe318fe1505c6d56ea347e6c09d1bf9247

Signed-off-by: Olivier Deprez <olivier.deprez@arm.com>
Change-Id: I3ad6e6767c2ca915f4a4fe8c5accc07e3e255387

Change-Id: I6d6ad62ca9979495ce46019f1a354dd36b4fec1e
Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>

This test fails on sgi575 models 11.9 release, the reason for failure
is old SCP firmware version which is 2.3.
With SCP version 2.5 above this issues does not occurs.

This patch can be reverted once the SCP FW binary updated on CI.

Change-Id: I453f3ef3e22272e0b2c61c96c98f1710eec8d1ca
Signed-off-by: Manish Pandey <manish.pandey2@arm.com>

The issue with this test is fixed with the
TF-A patch: https://review.trustedfirmware.org/c/TF-A/


trusted-firmware-a/+/3591, so re-enable it.

Signed-off-by: Zelalem <zelalem.aweke@arm.com>
Change-Id: I343a017eea8a134ce74dedd484faaafdeb65ef13

This test often fails on FVP_Base_Cortex-A55x4+Cortex-A76x2. This is under
investigation. This patch disables the test in the meantime.

Change-Id: I09e5c67ccce51b8dc9843dacb3375b17679df9a8
Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>

* changes:
  Max SPI INTID is 1019
  Switch AARCH32/AARCH64 to __aarch64__

Elements in fvp_power_domain_tree_desc and PLATFORM_CORE_COUNT are
multiplied by FVP_MAX_PE_PER_CPU in order to implement the correct
topology.

Change-Id: Icb979d719a1b4aac39a95b2829fcabaa53bdedaf
Signed-off-by: Imre Kis <imre.kis@arm.com>

Version 2.0202 of XML::LibXML changes the default behaviour regarding
external entities. This results empty tests_list.h and tests_list.c
generated by generate_test_list.pl. By enabling explicitly to expand
entities the script works correctly. The modified initalization of
LibXML is compatible with older versions of the module.

Change-Id: Icb951542e70870bddda44d03030eb1fe49689374
Signed-off-by: Imre Kis <imre.kis@arm.com>

The NODE_HW_STATE tests seem to hang on Juno. This needs to be investigated.
Disable them in the meantime.

Change-Id: I355aa8fea839f2054340f9e7a8a6fdc2f526e63d
Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>

Signed-off-by: Deepika Bhavnani <deepika.bhavnani@arm.com>
Change-Id: I1f99ec379f636cb9c812d7c4ca44f529455dabfd

NOTE: AARCH32/AARCH64 macros are now deprecated in favor of __aarch64__.

All common C compilers pre-define the same macros to signal which
architecture the code is being compiled for: __arm__ for AArch32 (or
earlier versions) and __aarch64__ for AArch64. There's no need for TF-A
to define its own custom macros for this. In order to unify code with
the export headers (which use __aarch64__ to avoid another dependency),
let's deprecate the AARCH32 and AARCH64 macros and switch the code base
over to the pre-defined standard macro. (Since it is somewhat
unintuitive that __arm__ only means AArch32, let's standardize on only
using __aarch64__.)

NOTE: This change is based on below TFA commit
https://github.com/ARM-software/arm-trusted-firmware/commit/402b3cf8766fe2cb4ae462f7ee7761d08a1ba56c



Signed-off-by: Deepika Bhavnani <deepika.bhavnani@arm.com>
Change-Id: If2c3dbaeb01d4a9d8cfd95d906e5eaf4ae94417f

This patch adds support for storing fw_config and hw_config
addresses passed as arg0 and arg1 parameters in x0, x1 from
BL31.

Signed-off-by: Alexei Fedorov <Alexei.Fedorov@arm.com>
Change-Id: I58ae379bb4a7ef1b6ce60a4e252c65d34dc14464

Signed-off-by: Deepika Bhavnani <deepika.bhavnani@arm.com>
Change-Id: I8b288cd886ee8e5483d3b4d266f986515a7ad8ce

The model has been updated to a newer version which fixed the
issues causing the PMU tests to fail, so they are being re-enabled
on this platform.

Signed-off-by: Petre-Ionut Tudor <petre-ionut.tudor@arm.com>
Change-Id: Ie2c7a610432a13edb05630d319cd0e8d7148b834