Home
last modified time | relevance | path

Searched refs:test (Results 1 – 24 of 24) sorted by relevance

/trusted-firmware-a-latest/docs/perf/
Dpsci-performance-methodology.rst12 The tests are based on the ``runtime-instrumentation`` test suite provided by
20 - **Parallel Tests** This type of test powers on all the non-lead CPUs and
22 then initiates the test on all CPUs in parallel.
24 - **Sequential Tests** This type of test powers on each non-lead CPU in
25 sequence. The lead CPU initiates the test on a non-lead CPU then waits for the
26 test to complete before proceeding to the next non-lead CPU. The lead CPU then
27 executes the test on itself.
Dpsci-performance-juno.rst413 test. The ``CPU_SUSPEND`` call powers down to the cluster level, requiring a
450 The ``PSCI_EXIT`` times are generally lower than in the last test because the
451 cluster remains powered on throughout the test and there is less code to execute
457 The test sequence here is as follows:
482 CPUs in that cluster are powerered down during the test. The ``CPU_OFF`` call
502 Since very little code is associated with ``PSCI_VERSION``, this test
Dpsci-performance-n1sdp.rst4 For this test we used the N1 System Development Platform (`N1SDP`_), which
/trusted-firmware-a-latest/plat/marvell/armada/a8k/a70x0/board/
Dmarvell_plat_config.c141 .info.test.cp_ap = CP,
142 .info.test.cp_index = 0,
/trusted-firmware-a-latest/plat/marvell/armada/a8k/a70x0_amc/board/
Dmarvell_plat_config.c138 .info.test.cp_ap = CP,
139 .info.test.cp_index = 0,
/trusted-firmware-a-latest/plat/marvell/armada/a8k/a80x0/board/
Dmarvell_plat_config.c192 .info.test.cp_ap = CP,
193 .info.test.cp_index = 0,
/trusted-firmware-a-latest/include/plat/marvell/armada/a8k/common/
Darmada_common.h58 } test; member
/trusted-firmware-a-latest/docs/process/
Dcontributing.rst85 - Please test your changes. As a minimum, ensure that Linux boots on the
192 for placing all the test scripts which will be executed by the CI Jobs.
236 - Considering this, we have other distinguished CI jobs which run a set of test
239 - ``tf-l1-build-plat`` is the test group, which holds the test configurations
242 in ``tf-l1-build-plat`` test group.
246 test group, illustrated with an example:
259 - Further a test-configuration file ``hikey-default:nil`` need to be added under the
260 test group, ``tf-l1-build-plat`` located at ``tf-a-ci-scripts/group/tf-l1-build-plat``,
Dcommit-style.rst76 | ``test`` | Adding missing tests or correcting existing tests |
Dcoding-style.rst384 #include <a_dir/test/a_header.h>
/trusted-firmware-a-latest/docs/components/
Ddebugfs-design.rst12 TFTF test payload or a Linux kernel module.
73 - This permits direct access to a firmware driver, mainly for test purposes
114 - a test payload, bootloader or hypervisor running at NS-EL2
Drealm-management-extension.rst86 TRP is a small test payload that runs at R-EL2 and implements a subset of
87 the Realm Management Interface (RMI) commands to primarily test EL3 firmware
150 can test Realm world with either `RMM`_ or TRP in R-EL2. In the TRP case,
303 If the NS Host is TF-A-Tests, then the default test suite in TFTF
Dras.rst97 RAS functionality is regularly tested in TF-A CI using `RAS test group`_ which has multiple
/trusted-firmware-a-latest/docs/design_documents/
Ddrtm_poc.rst66 Download EDK2 *FVP_AARCH64_EFI.fd* and UEFI DRTM application *test-disk.img*
79 To run the DRTM test application along with DRTM implementation in BL31,
91 -C bp.virtioblockdevice.image_path=<path/to/test-disk.img> \
Dmeasured_boot_poc.rst39 needed to test that the Event Log was properly created. One of these images will
71 manual to test and verify the correctness of the output generated by the
Dpsci_osi_mode.rst387 The proposed patches add a new CPU Suspend in OSI mode test suite to TF-A Tests.
/trusted-firmware-a-latest/
Dpoetry.lock30 test = ["coverage"]
65 test = ["filelock (>=3)", "pytest (>=6.2.4)", "pytest-cov (>=2.12)", "pytest-mock (>=2)", "pytest-r…
649 test = ["cython", "html5lib", "pytest (>=4.6)", "typed_ast"]
683 test = ["pytest"]
698 test = ["pytest"]
713 test = ["html5lib", "pytest"]
741 test = ["flake8", "mypy", "pytest"]
757 test = ["Pillow", "flake8", "pytest"]
772 test = ["pytest"]
787 test = ["pytest"]
[all …]
/trusted-firmware-a-latest/plat/marvell/armada/a8k/common/
Dplat_ble_setup.c649 switch (skip_im->info.test.cp_ap) { in ble_skip_image_gpio()
651 mpp_address = MVEBU_CP_GPIO_DATA_IN(skip_im->info.test.cp_index, in ble_skip_image_gpio()
/trusted-firmware-a-latest/docs/plat/
Dqemu.rst99 For example, to test the following firmware stack:
118 test key:
169 manually, a `builder`_ job may be triggered with the test configuration
Dqti-msm8916.rst134 Then install the resulting ``build/msm8916/release/bl31/bl31-test-signed.mbn``
/trusted-firmware-a-latest/docs/security_advisories/
Dsecurity-advisory-tfv-6.rst76 This includes the time spent in test code conforming to the SMC Calling
78 test code uses SMCCC v1.1, which reduces the number of general purpose registers
/trusted-firmware-a-latest/docs/plat/arm/juno/
Dindex.rst223 to RAM. For more details refer to section 5.16 of `PSCI`_. To test system suspend
/trusted-firmware-a-latest/docs/
Dchange-log.md2472 …- enable test cases for EL3 SPMC ([15ca1ee](https://review.trustedfirmware.org/plugins/gitiles/TF-…
6386 test, add a function to get non-secure DDR size, add DT helper for reg by
7485 flow, which might be useful in some test environments.
8266 - Enabled the ability for a production ROM with TBBR enabled to boot test
8788 target and supporting test code to the TSP. Also demonstrated non-secure
/trusted-firmware-a-latest/docs/design/
Dfirmware-design.rst401 BL2 loads the BL33 image (e.g. UEFI or other test or boot software) from