Lines Matching refs:a

3 …only been partially implemented. As a result, the deliverables for writing a driver and the method…
6a driver that can be used with Mbed TLS, and the PSA Driver [Integration](https://github.com/Mbed-…
12 [Example: Manually integrating a software accelerator alongside Mbed TLS](#example-manually-integra…
16a signature, are called *Single-Part Operations*. On the other hand, operations that consist of mu…
19a transparent driver is available for a particular combination of parameters (cryptographic algori…
20 …hat can only be used inside a protected environment such as a **secure element**, a hardware secur…
22a **driver dispatch layer** (also called a driver wrapper layer). For each cryptographic operation…
24 The long-term goal is for the driver dispatch layer to be auto-generated using a JSON driver descri…
41 There are three deliverables for creating such a driver. These are:
50a different process is followed where the developer manually edits the driver dispatch layer. The …
52 **1. Choose a driver prefix and a macro name that indicates whether the driver is enabled** \
53 A driver prefix is simply a word (often the name of the driver) that all functions/macros associate…
77 …ctions have been replaced with `jinja` templating logic. While the file has a `.jinja` extension, …
79 **5. If a driver entry point function has been provided then ensure it has the same signature as th…
83 …ut arguments are correct, but the driver does not support the operation. If a transparent driver r…
87 … contains a `switch` statement which checks the location of the key. If the key is stored in local…
89 …* **Opaque Drivers** Calls to driver entry points go in a separate `case` block corresponding to t…
92 The diagram below shows the layout of a driver wrapper function which can dispatch to two transpare…
123a corresponding `#endif`. Within this block, each individual driver's compatibility checks and cal…
126 This guide assumes you are building Mbed TLS from source alongside your project. If building with a
137a user config file.* This is the preferred option when your project requires a custom configuratio…
139 ### Example: Manually integrating a software accelerator alongside Mbed TLS
141a minimalistic implementation of ECDH and ECDSA on the NIST P-256 curve, specifically optimized fo…
153 …ts for `"sign_message"` and `"verify_message"`, which are not necessary for a sign-and-hash algori…
154 …the driver's status codes differ from PSA's, it is recommended to implement a status code translat…
156 …o the defined process, all code related to the driver call is placed within a check for `MBEDTLS_P…
180 Following this, p256-m is now ready to use alongside Mbed TLS as a software accelerator. If `MBEDTL…