Lines Matching refs:to
15 Drivers exposing this interface need to be registered at compile time by declaring their JSON descr…
21 …ntains function pointers, pointing to the driver's methods. All calls to a driver function are tri…
25 This section describes unit tests that must be implemented to validate the secure element driver in…
31 This applies to dynamic drivers only.
34 * Make at least one failing call to `psa_register_se_driver` followed by a successful call.
35 * Make at least one test that successfully registers the maximum number of drivers and fails to reg…
37 #### Dispatch to SE driver
39 For each API function that can lead to a driver call (more precisely, for each driver method call s…
44 …at does not have the substructure containing that method (i.e. the pointer to the substructure is …
45 …This does not need to be done for all operations (use a white-box approach to determine if operati…
52 For each API function that can lead to a driver call (more precisely, for each driver method call s…
56 …n a test that checks the outputs if the only realistic way to obtain the correct outputs is to sta…
60 For each API function that leads to a driver call, call it with parameters that cause a driver to b…
87 …ossible flow, including error cases (e.g. a key creation that fails midway due to `OUT_OF_MEMORY`).
89 * Two things need to be tested: the key that is being created or destroyed, and the driver's persis…
90 …he expected content (this can be done by e.g. using a key that is supposed to be present) and does…
92 …her to force it to fail at each point or to record successive storage states and replay each of th…
98 We must have at least one driver that is close to real-world conditions:
129 …est runs with two or more drivers available with driver A configured to fall back to driver B, wit…