Home
last modified time | relevance | path

Searched full:derive (Results 1 – 25 of 32) sorted by relevance

12

/Zephyr-latest/dts/bindings/crypto/
Dnordic,nrf-ccm.yaml28 set the PDU header bitmask used to derive the additional authentication
/Zephyr-latest/dts/bindings/usb/uac2/
Dzephyr,uac2.yaml14 # Audio Control entities derive their unique ID from child index (+ 1). For most
/Zephyr-latest/include/zephyr/dt-bindings/reset/
Dintel_socfpga_reset.h12 * derive the register offset and the associated device bit to perform
/Zephyr-latest/subsys/bluetooth/audio/
Dcsip_crypto.c82 * The key derivation function k1 is used to derive a key. The derived key is
/Zephyr-latest/arch/xtensa/core/
Dmmu.c40 /* Derive PTEVADDR from ASID so each domain gets its own PTE area */ in compute_regs()
/Zephyr-latest/include/zephyr/sys/
Dkobject.h127 * as it is possible for such code to derive the addresses of kernel objects
/Zephyr-latest/include/zephyr/dt-bindings/gpio/
Dmicrochip-xec-gpio.h14 * to derive the pin's bit position.
/Zephyr-latest/dts/bindings/ethernet/
Dxlnx,gem.yaml36 applied to the LPD_LSBUS clock in order to derive MDIO interface
/Zephyr-latest/drivers/bluetooth/hci/
Dhci_stm32wba.c407 /* The UID is used by firmware to derive */ in bt_get_ble_addr()
Dipm_stm32wb.c404 /* The UID is used by firmware to derive */ in bt_get_ble_addr()
/Zephyr-latest/boards/st/stm32wb5mmg/doc/
Dstm32wb5mmg.rst148 - IEEE 64-bit unique ID, possibility to derive 802.15.4 64-bit
/Zephyr-latest/drivers/gpio/
Dgpio_mchp_mec5.c497 /* TODO remove port_num. Derive it from pin & pin_num? */
/Zephyr-latest/doc/services/tfm/
Doverview.rst247 to derive new keys, and the **derived keys** don't need to be stored since
/Zephyr-latest/boards/st/nucleo_wb55rg/doc/
Dnucleo_wb55rg.rst125 - 64-bit unique ID. Possibility to derive 802.15.5 64-bit and
/Zephyr-latest/include/zephyr/bluetooth/
Diso.h527 * The code used to derive the session key that is used to encrypt and decrypt BIS payloads.
615 * The code used to derive the session key that is used to encrypt and decrypt BIS payloads.
/Zephyr-latest/include/zephyr/
Ddevice.h651 * controller for communication. Required devices can derive from
685 * sensor driver. Supported devices can derive from statically-defined
/Zephyr-latest/include/zephyr/drivers/
Dmspi.h530 * binding(xxx,mspi-controller.yaml) so that one may derive the settings from
/Zephyr-latest/arch/arm/core/mpu/
Darm_mpu_v8_internal.h538 /* Derive the index of the underlying MPU region, in mpu_configure_regions_and_partition()
/Zephyr-latest/subsys/net/ip/
D6lo.c1028 * Derive addr using context information and in uncompress_sa_ctx()
1237 * Derive addr using context information and in uncompress_da_ctx()
/Zephyr-latest/drivers/espi/
Despi_saf_mchp_xec.c204 * or chip select timing derive user values.
Despi_saf_mchp_xec_v2.c221 * or chip select timing derive user values.
/Zephyr-latest/tests/kernel/timer/timer_api/src/
Dmain.c33 * derive from sources that have slews that sum to +/- 13%.
/Zephyr-latest/subsys/net/l2/ieee802154/
Dieee802154_mgmt.c515 cmd->assoc_req.ci.rx_on = 1U; /* TODO: derive from PM settings */ in ieee802154_associate()
/Zephyr-latest/doc/build/kconfig/
Dtips.rst40 Symbols without prompts can't be configured directly by the user (they derive
/Zephyr-latest/doc/releases/
Dmigration-guide-3.7.rst685 chosen property. The devicetree bindings for all HCI drivers derive from a common

12