Lines Matching refs:entry

5 …ith Mbed TLS in the future, as well as driver types, operation types, and entry points. As many ke…
10 [Process for Entry Points where auto-generation is implemented](#process-for-entry-points-where-aut…
11 [Process for Entry Points where auto-generation is not implemented](#process-for-entry-points-where…
16 …Operations*. Single-part operations implemented by a driver will have one entry point, while multi…
22 … When a compatible driver is present, the driver wrapper calls the driver entry point function pro…
25 …l have to manually edit the driver dispatch layer and call their driver's entry point functions fr…
27 …he operation entry points specified in the table below. Certain operations are only permitted for …
39 If the driver is accelerating operations whose entry points are in the above table, the instruction…
46 The Mbed TLS driver tests for the aforementioned entry points provide examples of how these deliver…
50 If the driver is accelerating operations whose entry points are not present in the table, a differe…
76 … locate the function in the driver dispatch layer that corresponds to the entry point of that oper…
77 …entry points that have driver wrapper auto-generation implemented, the functions have been replace…
79 **5. If a driver entry point function has been provided then ensure it has the same signature as th…
80 …pe), and end with the entry point name. It should have the same signature as the driver wrapper fu…
88 …* **Transparent drivers:** Calls to driver entry points go under `case PSA_KEY_LOCATION_LOCAL_STOR…
89 …* **Opaque Drivers** Calls to driver entry points go in a separate `case` block corresponding to t…
102 |   |   |   |   ├── foo_driver_transparent_xxx() //call to driver entry point
107 |   |   |   |   ├── bar_driver_transparent_xxx() //call to driver entry point
116 |   |   |   |   ├── baz_driver_opaque_xxx() //call to driver entry point
123 …this block, each individual driver's compatibility checks and call to the entry point must be cont…
141 …TLS as a PSA transparent driver. The source code of p256-m and the driver entry points is located …
152 The p256-m driver implements the following entry points: `"import_key"`, `"export_public_key"`, `"g…
153 …entry points for `"sign_message"` and `"verify_message"`, which are not necessary for a sign-and-h…
154 The driver entry point functions can be found in `p256m_driver_entrypoints.[hc]`. These functions a…
156 …entry points have also been modified. The code block below shows the additions made to `psa_driver…