Home
last modified time | relevance | path

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

12

/rk3399_ARM-atf/docs/perf/
H A 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.
H A Dpsci-performance-juno.rst386 test. The ``CPU_SUSPEND`` call powers down to the cluster level, requiring a
423 The ``PSCI_EXIT`` times are generally lower than in the last test because the
424 cluster remains powered on throughout the test and there is less code to execute
430 The test sequence here is as follows:
455 CPUs in that cluster are powerered down during the test. The ``CPU_OFF`` call
475 Since very little code is associated with ``PSCI_VERSION``, this test
H A Dpsci-performance-n1sdp.rst4 For this test we used the N1 System Development Platform (`N1SDP`_), which
/rk3399_ARM-atf/tools/cot_dt2c/tests/
H A Dtest2.dtsi10 #if test
20 #if defined (test)
H A Dtest.dtsi17 #if defined(test)
/rk3399_ARM-atf/plat/marvell/armada/a8k/a70x0/board/
H A Dmarvell_plat_config.c141 .info.test.cp_ap = CP,
142 .info.test.cp_index = 0,
/rk3399_ARM-atf/plat/marvell/armada/a8k/a70x0_amc/board/
H A Dmarvell_plat_config.c138 .info.test.cp_ap = CP,
139 .info.test.cp_index = 0,
/rk3399_ARM-atf/plat/marvell/armada/a8k/a80x0/board/
H A Dmarvell_plat_config.c192 .info.test.cp_ap = CP,
193 .info.test.cp_index = 0,
/rk3399_ARM-atf/include/plat/marvell/armada/a8k/common/
H A Darmada_common.h58 } test; member
/rk3399_ARM-atf/
H A Dpoetry.lock69 test = ["build[uv,virtualenv]", "filelock (>=3)", "pytest (>=6.2.4)", "pytest-cov (>=2.12)", "pytes…
240 test = ["flake8 (==3.7.8)", "hypothesis (==3.55.3)"]
389 test = ["Pillow (>=9)", "cairocffi (>=1.2.0)", "matplotlib (>=3.6.0)", "networkx (>=2.5)", "numpy (…
390 test-musl = ["cairocffi (>=1.2.0)", "networkx (>=2.5)", "pytest (>=7.0.1)", "pytest-timeout (>=2.1.…
426 test = ["flufl.flake8", "importlib-resources (>=1.3)", "jaraco.test (>=5.4)", "packaging", "pyfakef…
684 test = ["appdirs (==1.4.4)", "covdefaults (>=2.3)", "pytest (>=8.3.2)", "pytest-cov (>=5)", "pytest…
962 test = ["build[virtualenv] (>=1.0.3)", "filelock (>=3.4.0)", "ini2toml[lite] (>=0.14)", "jaraco.dev…
1035 test = ["cython", "html5lib", "pytest (>=4.6)", "typed_ast"]
1071 test = ["pytest"]
1087 test = ["pytest"]
[all …]
/rk3399_ARM-atf/docs/components/
H A 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
H A Drealm-management-extension.rst85 TRP is a small test payload that runs at R-EL2 and implements a subset of
86 the Realm Management Interface (RMI) commands to primarily test EL3 firmware
117 and test suite originates from TF-a-tests project.
/rk3399_ARM-atf/docs/about/
H A Dlts.rst115 taking into account the test-and-debug phase before LTS is cut (see below) --
136 ** A note about test coverage from TF.org **
140 members, see the project charter for more details). This automated test coverage
151 The TFTF LTS branch will be used to regression test the corresponding TF-A LTS
193 ideally it coincides with TF-A November release which means that our test
215 isn’t as much to test and debug as an annual LTS release has. Also companies
331 #. Request all platform-owners to test and debug the RC branch
332 #. Gather feedback from the test and debug cycle
344 #. The maintainers shall publish a well-defined test specification for any
359 #. The CI/CD infrastructure shall provide test support for all “live” LTS
/rk3399_ARM-atf/docs/process/
H A Dcontributing.rst89 - Please test your changes. As a minimum, ensure that Linux boots on the
232 for placing all the test scripts which will be executed by the CI Jobs.
273 We have CI jobs which run a set of test configurations on every TF-A patch
278 the case, we maintain a set of build tests. ``tf-l1-build-plat`` is the test
280 verify that your newly added files are covered by such a build test.
298 of this test group. ``group/tf-l1-build-plat/hikey-default:nil`` file just
313 to add more complex tests beyond a simple build test, please refer to the `TF-A
/rk3399_ARM-atf/plat/marvell/armada/a8k/common/
H A 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()
/rk3399_ARM-atf/docs/plat/
H A 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
/rk3399_ARM-atf/tools/cot_dt2c/
H A Dpoetry.lock45 test = ["pytest (>=6)"]
105 test = ["Pillow (>=9) ; platform_python_implementation != \"PyPy\"", "cairocffi (>=1.2.0)", "matplo…
106 test-musl = ["cairocffi (>=1.2.0)", "networkx (>=2.5)", "pytest (>=7.0.1)", "pytest-timeout (>=2.1.…
284 test = ["pytest", "tornado (>=4.5)", "typeguard"]
H A D.gitignore43 # Unit test / coverage reports
/rk3399_ARM-atf/docs/
H A Darchitecture_features.rst548 ``test_smccc_arch_feature_availability`` test in TFTF, otherwise CI will
572 - Optionally, although recommended, is to add a test in TFTF. This should only
574 is not necessary to add a test for functionality that does not have EL3
/rk3399_ARM-atf/tools/tlc/
H A Dpoetry.lock45 test = ["beautifulsoup4 (>=4.8.0)", "coverage (>=4.5.4)", "fixtures (>=3.0.0)", "flake8 (>=4.0.0)",…
71 test = ["beautifulsoup4 (>=4.8.0)", "coverage (>=4.5.4)", "fixtures (>=3.0.0)", "flake8 (>=4.0.0)",…
310 test = ["flake8 (==3.7.8)", "hypothesis (==3.55.3)"]
468 test = ["pytest (>=6)"]
809 test = ["appdirs (==1.4.4)", "covdefaults (>=2.3)", "pytest (>=8.3.2)", "pytest-cov (>=5)", "pytest…
991 test = ["assertpy (>=1.1)", "beautifulsoup4 (>=4.11.1)", "black (>=22.1.0)", "flake8 (>=4.0.1)", "p…
996 description = "pytest plugin for test session metadata"
1009 test = ["black (>=22.1.0)", "flake8 (>=4.0.1)", "pre-commit (>=2.17.0)", "tox (>=3.24.5)"]
1253 test = ["build[virtualenv] (>=1.0.3)", "filelock (>=3.4.0)", "ini2toml[lite] (>=0.14)", "jaraco.dev…
1377 description = "tox is a generic virtualenv management and test command line tool"
[all …]
/rk3399_ARM-atf/docs/security_advisories/
H A Dsecurity-advisory-tfv-6.rst77 This includes the time spent in test code conforming to the SMC Calling
79 test code uses SMCCC v1.1, which reduces the number of general purpose registers
/rk3399_ARM-atf/docs/tools/
H A Dcot-dt2c.rst61 cot-dt2c convert-to-c fdts/tbbr_cot_descriptors.dts test.c
/rk3399_ARM-atf/docs/plat/qti/
H A Drb3gen2.rst47 the OEM test signature to allow it to work on devices in non-secure mode. In
/rk3399_ARM-atf/fdts/
H A Dtc-base.dtsi645 test {
646 compatible = "android,trusty-test-v1";
/rk3399_ARM-atf/docs/threat_model/
H A Dsupply_chain_threat_model.rst105 These are binaries used to test TF-A based systems. Below is a brief
113 Reference Platforms depending on the test configuration.
118 Other software components used to test TF-A include U-Boot, Linux kernel, RSE,
124 The TF-A project uses several tools to build, analyze and test the TF-A source

12