Searched refs:dispatch (Results  1 – 20 of 20) sorted by relevance
| /openthread-latest/third_party/mbedtls/repo/tests/suites/ | 
| D | test_suite_md.psa.data | 5 PSA dispatch MD5 legacy only9 PSA dispatch MD5 driver only
 13 PSA dispatch MD5 legacy+driver
 17 PSA dispatch RIPEMD160 legacy only
 21 PSA dispatch RIPEMD160 driver only
 25 PSA dispatch RIPEMD160 legacy+driver
 29 PSA dispatch SHA1 legacy only
 33 PSA dispatch SHA1 driver only
 37 PSA dispatch SHA1 legacy+driver
 41 PSA dispatch SHA224 legacy only
 [all …]
 
 | 
| D | helpers.function | 37 #define DISPATCH_TEST_SUCCESS           0   /* Test dispatch successful */
 | 
| D | test_suite_psa_crypto_low_hash.function | 9  * the driver dispatch layer behaves correctly even when not invoked via
 | 
| D | main_test.function | 57 /* Test dispatch code */
 | 
| D | host_test.function | 373  * \param ret                        The test dispatch status (DISPATCH_xxx).
 | 
| /openthread-latest/third_party/mbedtls/repo/scripts/data_files/driver_templates/ | 
| D | OS-template-opaque.jinja | 1 {# One Shot function's dispatch code for opaque drivers.
 | 
| D | OS-template-transparent.jinja | 1 {# One Shot function's dispatch code for transparent drivers.
 | 
| /openthread-latest/src/core/thread/ | 
| D | lowpan.cpp | 1100     uint8_t dispatch;  in ParseFrom()  local1103     dispatch = *aFrame++;  in ParseFrom()
 1105 …VerifyOrExit((dispatch & (kDispatchMask | kSourceShort | kDestShort)) == (kDispatch | kSourceShort…  in ParseFrom()
 1107     mHopsLeft = (dispatch & kHopsLeftMask);  in ParseFrom()
 1162     uint8_t dispatch = (kDispatch | kSourceShort | kDestShort);  in AppendTo()  local
 1166         SuccessOrExit(error = aFrameBuilder.AppendUint8(dispatch | mHopsLeft));  in AppendTo()
 1170         SuccessOrExit(error = aFrameBuilder.AppendUint8(dispatch | kDeepHopsLeft));  in AppendTo()
 
 | 
| /openthread-latest/third_party/mbedtls/repo/docs/ | 
| D | psa-driver-example-and-guide.md | 20 …face.md#lifetimes-and-locations) that the driver is registered for: the dispatch is based on the k…22 Mbed TLS contains a **driver dispatch layer** (also called a driver wrapper layer). For each crypto…
 24 The long-term goal is for the driver dispatch layer to be auto-generated using a JSON driver descri…
 25 …of the driver wrapper, developers will have to manually edit the driver dispatch layer and call th…
 50 …erent process is followed where the developer manually edits the driver dispatch layer. The follow…
 76 **4. For each operation being accelerated, locate the function in the driver dispatch layer that co…
 92 The diagram below shows the layout of a driver wrapper function which can dispatch to two transpare…
 
 | 
| /openthread-latest/third_party/mbedtls/repo/docs/proposed/ | 
| D | psa-driver-developer-guide.md | 22 …ed for the specific key location that the driver is registered for: the dispatch is based on the k…44 …g) can include complex preprocessor definitions to conditionally enable dispatch capabilities for …
 
 | 
| D | psa-driver-interface.md | 25 …ation](#lifetimes-and-locations) that the driver is registered for: the dispatch is based on the k…315 #### Key derivation driver dispatch logic
 317 The core decides whether to dispatch a key derivation operation to a driver based on the location a…
 594 ### PAKE driver dispatch logic
 595 The core decides whether to dispatch a PAKE operation to a driver based on the location of the prov…
 1100 …times-and-locations), or [as a fallback for key derivation](#key-derivation-driver-dispatch-logic).
 1428 Should [dispatch to an opaque driver](#key-derivation-driver-dispatch-logic) allow fallback, so tha…
 
 | 
| D | psa-conditional-inclusion-c.md | 22 …ch as a secure element, for which the core only does key management and dispatch using wrapped key…
 | 
| /openthread-latest/third_party/mbedtls/repo/docs/architecture/psa-migration/ | 
| D | md-cipher-dispatch.md | 80 …er, the goal is to make more code call PSA drivers where available. How dispatch is done is second…195 …s before it calls `psa_crypto_init()`). A possible workaround may be to dispatch to the internal f…
 246 …S_MD_SHA256` and `md` will dispatch to the legacy code, pass a new constant `MBEDTLS_MD_SHA256_USE…
 293 …his would only save at best a very small amount of code size in the PSA dispatch code. This may be…
 295 … PSA. However, this can simplify both the implementation and the use of dispatch code thanks to so…
 352 ### Dual-dispatch for block cipher primitives
 366 …ule, or a subset of the existing Cipher API, extended with the ability to dispatch to a PSA driver.
 372 …ater (such as NIST-KW, CMAC, PKCS5 and PKCS12), we can just extend dual-dispatch support to other …
 501 #### Support for PSA dispatch in hash operations
 503 …orms some hash operation or context management needs to know whether to dispatch via PSA or legacy.
 [all …]
 
 | 
| D | strategy.md | 149 `USE_PSA_CRYPTO` is enabled; see `md-cipher-dispatch.md` in the same directory175 then dispatch to PSA, see `md-cipher-dispatch.md`.
 226   `md-cipher-dispatch.md`.
 251    dispatch to PSA, but not the low-level legacy API, for all operations.
 295 - for hashes and ciphers, see `md-cipher-dispatch.md` in the same directory;
 412 layers compared to the existing (no need to dispatch through function
 
 | 
| /openthread-latest/third_party/mbedtls/repo/docs/architecture/ | 
| D | psa-crypto-implementation-structure.md | 54 The psa_driver_wrapper_<entry_point>() functions dispatch cryptographic operations to accelerator d…131 * For the testing of the driver dispatch code, `tests/include/test/drivers/crypto_config_test_drive…
 142 2. Driver dispatch code in `scripts/data_files/driver_templates/psa_crypto_driver_wrappers.h.jinja`…
 146 …hm/key-type compatibility) and in the built-in implementation, but not in the driver dispatch code.
 173 * For new functions: incorrect function call sequence, driver dispatch (in `tests/suites/test_suite…
 
 | 
| D | psa-shared-memory.md | 121 3. The code of the PSA Crypto dispatch layer (also known as the core), which is provided by Mbed TL…130 …f the PSA Crypto API. Note that this allows two possible levels: in the dispatch layer (independen…
 132 #### Protection in the dispatch layer
 134 The dispatch layer has no control over how the driver layer will access buffers. Therefore the only…
 142 …overall amount of work since there are more driver implementations than dispatch implementations. …
 166 **Design decision: the dispatch layer shall copy all small buffers**.
 196 **Design decision: the dispatch layer shall allocate an intermediate buffer for cipher and AEAD pla…
 202 …o revisit this when we start supporting an SIV mode, at which point the dispatch layer shall copy …
 208 … to revisit this when we start supporting PureEdDSA, at which point the dispatch layer shall copy …
 216 * The core (dispatch layer) shall make a copy of the following buffers, so that drivers do not rece…
 [all …]
 
 | 
| /openthread-latest/third_party/mbedtls/repo/tests/docker/bionic/ | 
| D | Dockerfile | 55 # Jinja2 is required for driver dispatch code generation.
 | 
| /openthread-latest/tests/toranj/ | 
| D | README_CLI.md | 173 …L) model in python) and do not need a separate process to run to handle/dispatch events (which is …
 | 
| /openthread-latest/third_party/mbedtls/repo/docs/architecture/psa-thread-safety/ | 
| D | psa-thread-safety.md | 354 3. Make the dispatch layer public for drivers to call.
 | 
| /openthread-latest/third_party/mbedtls/repo/ | 
| D | ChangeLog | 361    * Don't include the PSA dispatch functions for PAKEs (psa_pake_setup() etc)365      on MBEDTLS_BIGNUM_C, and a driver dispatch layer enabling alternative
 650    * Add a driver dispatch layer for EC J-PAKE, enabling alternative
 888    * Add a driver dispatch layer for raw key agreement, enabling alternative
 
 |