Home
last modified time | relevance | path

Searched refs:Descriptor (Results 1 – 21 of 21) sorted by relevance

/Zephyr-latest/samples/subsys/bindesc/
Dbindesc.rst2 :name: Binary Descriptor
/Zephyr-latest/drivers/sdhc/
DKconfig.intel35 int "EMMC host controller ADMA Descriptor size"
39 EMMC host controller ADMA Descriptor size.
/Zephyr-latest/samples/subsys/usb/common/
DKconfig.sample_usbd49 bool "Use default USB 2.0 Extension Descriptor"
51 Set bcdUSB value to 0201 and use default USB 2.0 Extension Descriptor.
/Zephyr-latest/drivers/can/
DKconfig.nxp_s3219 Otherwise NXP S32 CANXL uses RX Message Descriptor.
/Zephyr-latest/subsys/usb/device/
DKconfig69 bool "Use Interface Association Descriptor code triple"
73 uses the Interface Association Descriptor.
137 Set bMaxPower value in the Standard Configuration Descriptor,
/Zephyr-latest/subsys/usb/device/class/
DKconfig.cdc48 bool "Force using Interface Association Descriptor"
/Zephyr-latest/subsys/bindesc/
DKconfig42 module-str = Binary Descriptor read
/Zephyr-latest/doc/hardware/peripherals/
Ddma.rst35 Transfer Descriptor Memory Management
/Zephyr-latest/doc/connectivity/bluetooth/api/
Dgatt.rst39 Declares a Descriptor.
/Zephyr-latest/arch/x86/core/
DKconfig.ia3222 Interrupt Descriptor Table (IDT). By default all 256 vectors are
/Zephyr-latest/doc/
Dglossary.rst106 (Interrupt Descriptor Table) a data structure used by the x86
/Zephyr-latest/doc/connectivity/usb/device/
Dusb_device.rst388 The application should register descriptors such as Capability Descriptor
401 * Part of USB Descriptor table
/Zephyr-latest/doc/kernel/services/
Dinterrupts.rst29 An :abbr:`IDT (Interrupt Descriptor Table)` or a vector table is used
680 Descriptor Table (IDT) which must be laid out in a certain way per the x86
/Zephyr-latest/doc/releases/
Drelease-notes-2.1.rst699 * :github:`19544` - make usb power settings in "Configuration Descriptor" setable
Drelease-notes-2.2.rst658 * Make USB Descriptor power options configurable
Drelease-notes-1.14.rst143 * :github:`16602` - Bluetooth: GATT Discovery: Descriptor Discovery by range Seg Fault
343 * :github:`16602` - Bluetooth: GATT Discovery: Descriptor Discovery by range Seg Fault
Drelease-notes-2.0.rst997 * :github:`16602` - Bluetooth: GATT Discovery: Descriptor Discovery by range Seg Fault
Drelease-notes-2.4.rst1683 * :github:`23111` - drivers:usb:device:sam0: Descriptor tables are filled with zeros in attach()
Drelease-notes-3.2.rst2662 * :github:`23111` - drivers:usb:device:sam0: Descriptor tables are filled with zeros in attach()
Drelease-notes-3.3.rst2877 * :github:`54574` - USB RNDIS Reception and Descriptor Issue(s)
/Zephyr-latest/doc/hardware/porting/
Darch.rst353 For example, x86 has the concept of an :abbr:`IDT (Interrupt Descriptor Table)`