Home
last modified time | relevance | path

Searched full:formats (Results 1 – 25 of 34) sorted by relevance

12

/trusted-firmware-m-3.6.0/lib/ext/t_cose/inc/
Dt_cose_mac0_sign.h173 * in the IANA CoAP Content-Formats registry.
179 * The IANA CoAP Content-Formats registry is found
180 * [here](https://www.iana.org/assignments/core-parameters/core-parameters.xhtml#content-formats).
Dt_cose_sign1_sign.h170 * in the IANA CoAP Content-Formats registry.
177 * The IANA CoAP Content-Formats registry is found
178 * [here](https://www.iana.org/assignments/core-parameters/core-parameters.xhtml#content-formats).
/trusted-firmware-m-3.6.0/
D.readthedocs.yaml28 formats:
/trusted-firmware-m-3.6.0/lib/ext/cryptocell-312-runtime/codesafe/src/psa_driver_api/include/
Dcc3xx_internal_rsa_util.h11 * to manipulate RSA types and key formats
/trusted-firmware-m-3.6.0/lib/ext/t_cose/src/
Dt_cose_util.h184 * algorithm ID and a few other things. This formats that structure
/trusted-firmware-m-3.6.0/docs/contributing/
Ddoc_guidelines.rst141 Mixing two different code-block formats in the same document will break
/trusted-firmware-m-3.6.0/interface/include/psa/
Dcrypto.h597 * Implementations may support other formats as long as the standard
598 * format is supported. Implementations that support other formats
599 * should ensure that the formats are clearly unambiguous so as to
619 * formats, but should be conservative: implementations
665 * If the implementation of psa_import_key() supports other formats
759 * Implementations may support other formats as long as the standard
760 * format is supported. Implementations that support other formats
761 * should ensure that the formats are clearly unambiguous so as to
3537 * private key is on. The standard formats for public
3930 * accepts. The standard formats for public
/trusted-firmware-m-3.6.0/lib/ext/mbedcrypto/mbedcrypto_config/
Dtfm_mbedcrypto_config_default.h161 * Disable if you only need to support RFC 5915 + 5480 key formats.
Dtfm_mbedcrypto_config_profile_large.h162 * Disable if you only need to support RFC 5915 + 5480 key formats.
/trusted-firmware-m-3.6.0/lib/ext/cryptocell-312-runtime/codesafe/src/psa_driver_api/src/
Dcc3xx_internal_rsa_util.c11 * to manipulate RSA types and key formats
/trusted-firmware-m-3.6.0/platform/ext/target/nxp/common/Native_Driver/utilities/str/
Dfsl_str.c827 /* Start parsing apart the format string and display appropriate formats and data. */ in StrFormatPrintf()
837 * All formats begin with a '%' marker. Special chars like in StrFormatPrintf()
/trusted-firmware-m-3.6.0/docs/design_docs/
Dff_isolation.rst157 the difference in practical register formats, which is not described in this
/trusted-firmware-m-3.6.0/platform/ext/target/stm/common/stm32l5xx/hal/Src/
Dstm32l5xx_hal_uart_ex.c124 8-bit or 9-bit), the possible UART formats are listed in the
Dstm32l5xx_hal_dma.c22 Channel request, Transfer Direction, Source and Destination data formats,
/trusted-firmware-m-3.6.0/platform/ext/target/nxp/common/Native_Driver/drivers/
Dfsl_usart.h437 * same as the parity bit when parity is enabled for 8 bit and 9 bit data formats.
/trusted-firmware-m-3.6.0/platform/ext/target/stm/common/stm32u5xx/hal/Inc/
Dstm32u5xx_hal_rtc.h289 /** @defgroup RTC_Hour_Formats RTC Hour Formats
/trusted-firmware-m-3.6.0/platform/ext/target/stm/common/stm32u5xx/hal/Src/
Dstm32u5xx_hal_uart_ex.c124 8-bit or 9-bit), the possible UART formats are listed in the
/trusted-firmware-m-3.6.0/platform/ext/target/stm/common/stm32h5xx/hal/Inc/
Dstm32h5xx_hal_rtc.h295 /** @defgroup RTC_Hour_Formats RTC Hour Formats
/trusted-firmware-m-3.6.0/platform/ext/target/stm/common/stm32h5xx/hal/Src/
Dstm32h5xx_hal_uart_ex.c124 8-bit or 9-bit), the possible UART formats are listed in the
/trusted-firmware-m-3.6.0/docs/doxygen/
DDoxyfile.in2340 # generated by dot. For an explanation of the image formats see the section
2341 # output formats in the documentation of the dot tool (Graphviz (see:
/trusted-firmware-m-3.6.0/lib/ext/cryptocell-312-runtime/shared/include/crypto_api/
Dcc_ffcdh.h690 @brief This function formats the UserInfo according to the user role (PartyU or PartyV) and NIST SP…
/trusted-firmware-m-3.6.0/lib/ext/cryptocell-312-runtime/doxygen/
Ddoxygen_cc312.conf2419 # generated by dot. For an explanation of the image formats see the section
2420 # output formats in the documentation of the dot tool (Graphviz (see:
/trusted-firmware-m-3.6.0/lib/ext/cryptocell-312-runtime/shared/include/mbedtls/
Dconfig-cc312-mps2-freertos.h1024 * Disable if you only need to support RFC 5915 + 5480 key formats.
Dconfig-cc312-mps2-no-os.h1026 * Disable if you only need to support RFC 5915 + 5480 key formats.
Dconfig-cc312-musca_b1-no-os.h1026 * Disable if you only need to support RFC 5915 + 5480 key formats.

12