Searched full:controller (Results 1 – 25 of 2566) sorted by relevance
12345678910>>...103
7 bool "USB device controller drivers"9 Enable USB device controller drivers.14 bool "USB device controller supports high speed"16 USB device controller supports high speed.21 USB device controller supports remote wakeup feature.24 bool "Designware USB Device Controller Driver"28 Designware USB Device Controller Driver.31 bool "DesignWare Controller and PHY support for USB specification 2.0"37 bool "USB device controller driver for Raspberry Pi Pico devices"47 bool "USB device controller driver for STM32 devices"[all …]
29 intmux_ch0: interrupt-controller@0 {33 interrupt-controller;37 intmux_ch1: interrupt-controller@1 {41 interrupt-controller;45 intmux_ch2: interrupt-controller@2 {49 interrupt-controller;53 intmux_ch3: interrupt-controller@3 {57 interrupt-controller;61 intmux_ch4: interrupt-controller@4 {65 interrupt-controller;[all …]
10 ${ZEPHYR_BASE}/subsys/bluetooth/controller/util/mem.c11 ${ZEPHYR_BASE}/subsys/bluetooth/controller/util/memq.c12 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/ull_tx_queue.c13 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/ull_conn.c14 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/ll_feat.c15 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/ull_llcp_conn_upd.c16 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/ull_llcp_cc.c17 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/ull_llcp_pdu.c18 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/ull_llcp_remote.c19 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/ull_llcp_local.c[all …]
5 bool "Designware Interrupt Controller for ACE"10 Designware Interrupt Controller used by ACE.13 bool "Designware Interrupt Controller"18 Designware Interrupt Controller can be used as a 2nd level interrupt19 controller which combines several sources of interrupt into one line20 that is then routed to the 1st level interrupt controller.26 string "Name for Designware Interrupt Controller"29 Give a name for the instance of Designware Interrupt Controller36 the ISRs for Designware Interrupt Controller are assigned.39 int "Init priority for DW interrupt controller"[all …]
1 # interrupt controller configuration options6 menu "Interrupt controller drivers"20 bool "SweRV EH1 Programmable Interrupt Controller (PIC)"24 Programmable Interrupt Controller for the SweRV EH1 RISC-V CPU.27 bool "VexRiscv LiteX Interrupt controller"34 bool "GRLIB IRQMP interrupt controller"41 int "Interrupt controller init priority"44 Interrupt controller device initialization priority.49 int "XEX GIRQ Interrupt controller init priority"52 XEC GIRQ Interrupt controller device initialization priority.
1 # Reset Controller driver configuration options7 # Reset Controller options10 bool "Reset Controller drivers"12 Reset Controller drivers. Reset node represents a region containing13 information about reset controller device. The typical use-case is15 controller node together with some reset information.20 int "Reset Controller driver init priority"23 This option controls the priority of the reset controller device28 comment "Reset Controller Drivers"
15 Controller. This value does not include the HCI ACL header.16 The Host will segment the data transmitted to the Controller so that17 packets sent to the Controller will contain data up to this size.19 Controller.21 by the Controller and use the smallest value supported by both the22 Host and the Controller.25 The Controller will return this value in the HCI LE Read Buffer27 Layer transmission size then the Controller will perform39 Controller. This determines the maximum amount of data packets the40 Host can have queued in the Controller before waiting for the[all …]
17 * @brief Lock the mutex of npcx i2c controller.19 * @param i2c_dev Pointer to the device structure for i2c controller instance.24 * @brief Unlock the mutex of npcx i2c controller.26 * @param i2c_dev Pointer to the device structure for i2c controller instance.31 * @brief Configure operation of a npcx i2c controller.33 * @param i2c_dev Pointer to the device structure for i2c controller instance.35 * for the I2C controller.44 * @brief Get I2C controller speed.46 * @param i2c_dev Pointer to the device structure for i2c controller instance.51 * @retval -EIO Controller is not configured.[all …]
5 bool "Virtual USB device controller driver"10 Virtual USB device controller driver.13 int "Virtual controller driver internal thread stack size"17 Virtual device controller driver internal thread stack size.20 int "Virtual controller driver thread priority"24 Virtual device controller driver thread priority.
5 bool "Skeleton for an USB device controller driver"9 Skeleton for an USB device controller driver.12 int "UDC controller driver internal thread stack size"16 Skeleton device controller driver internal thread stack size.19 int "Skeleton controller driver thread priority"23 Skeleton device controller driver thread priority.
5 bool "STM32 Flexible Memory Controller (FMC)"9 Enable STM32 Flexible Memory Controller.14 bool "STM32 FMC SDRAM controller"20 Enable STM32 FMC SDRAM controller.23 bool "STM32 FMC NOR/PSRAM controller"30 Enable STM32 FMC NOR/PSRAM controller.
7 bluetooth.controller.ctrl_tx_buffer_alloc.test_0_per_conn:10 bluetooth.controller.ctrl_tx_buffer_alloc.test_1_per_conn:14 bluetooth.controller.ctrl_tx_buffer_alloc.test_2_per_conn:18 bluetooth.controller.ctrl_tx_buffer_alloc.test_3_per_conn:22 bluetooth.controller.ctrl_tx_buffer_alloc.test_max_per_conn_alloc:26 bluetooth.controller.ctrl_tx_buffer_alloc.test_max_common_alloc:
6 #include <zephyr/dt-bindings/interrupt-controller/openisa-intmux.h>17 zephyr,flash-controller = &ftfe;58 pcc0: clock-controller@4002b000 {64 pcc1: clock-controller@41027000 {70 event0: interrupt-controller@e0041000 {74 interrupt-controller;78 event1: interrupt-controller@4101f000 {82 interrupt-controller;96 intmux0_ch0: interrupt-controller@0 {100 interrupt-controller;[all …]
19 Devices on the bus can operate in three roles: as a Controller that22 Controller, that provides the main interface to the system's CPU.23 Zephyr has API for the Controller role.25 SMBus peripheral devices can initiate communication with Controller29 protocol behaves as a Controller to perform the notification. It writes33 request attention from the Controller. The Controller needs to read one byte43 .. _smbus-controller-api:45 SMBus Controller API48 Zephyr's SMBus controller API is used when an SMBus device controls the bus,
47 hlic0: interrupt-controller {51 interrupt-controller;61 hlic1: interrupt-controller {65 interrupt-controller;75 hlic2: interrupt-controller {79 interrupt-controller;89 hlic3: interrupt-controller {93 interrupt-controller;103 hlic4: interrupt-controller {107 interrupt-controller;[all …]
9 * @brief USB host controller (UHC) driver API22 * @brief USB host controller (UHC) driver API23 * @defgroup uhc_api USB host controller driver API55 /** Flag marks request buffer claimed by the controller */66 * @brief USB host controller event types95 * USB host controller event100 * by higher layer during controller initialization (uhc_init).115 /** Pointer to controller's device struct */134 * USB host controller capabilities139 /** USB high speed capable controller */[all …]
9 * @brief New USB device controller (UDC) driver API22 * @brief Maximum packet size of control endpoint supported by the controller.32 * USB device controller capabilities37 /** USB high speed capable controller */39 /** Controller supports USB remote wakeup */41 /** Controller performs status OUT stage automatically */62 * USB device controller endpoint capabilities82 * USB device controller endpoint status98 * USB device controller endpoint configuration123 * @brief USB device controller event types[all …]
1 # Bluetooth Controller configuration options6 # The following symbols are enabled depending if the controller actually105 bool "Bluetooth Controller"107 Enables support for SoC native controller implementations.124 comment "BLE Controller configuration"127 bool "Crypto functions in Controller"132 provided by the controller.208 Set the number of Rx PDUs to be buffered in the controller. In a 7.5ms219 controller. Number of required RX buffers would worst-case be234 in the controller.[all …]
26 * @brief Get the maximum transceiver bitrate for a CAN controller29 * controller. If no CAN transceiver is present in the devicetree, the maximum30 * bitrate will be that of the CAN controller.41 * compatible = "vnd,can-controller";46 * compatible = "vnd,can-controller";60 * @param max maximum bitrate supported by the CAN controller61 * @return the maximum bitrate supported by the CAN controller/transceiver combination69 * @brief Get the maximum transceiver bitrate for a DT_DRV_COMPAT CAN controller71 * @param max maximum bitrate supported by the CAN controller72 * @return the maximum bitrate supported by the CAN controller/transceiver combination
5 STM32 Flexible Memory Controller (FMC).11 controller. Each external device is accessed by means of a unique chip select.14 The flexible memory controller includes three memory controllers:16 - NOR/PSRAM memory controller17 - NAND memory controller (some devices also support PC Card)18 - Synchronous DRAM (SDRAM/Mobile LPSDR SDRAM) controller20 Each memory controller is defined below the FMC DeviceTree node and is managed
30 Enable STM32Cube Controller Area Network (CAN) HAL module driver35 Enable STM32Cube HDMI-CEC controller (CEC) HAL module driver108 Enable STM32Cube Direct Memory Access controller (DMA) HAL module114 Enable STM32Cube Chrom-Art Accelerator™ controller (DMA2D) HAL module120 Enable STM32Cube Extended Direct Memory Access controller (DMA) HAL141 Enable STM32Cube Extended interrupt and event controller (EXTI) HAL147 Enable STM32Cube Controller area network with flexible data rate218 Enable STM32Cube Host Controller device (HCD) HAL module driver255 Enable STM32Cube Inter-Processor communication controller (IPCC) HAL276 Enable STM32Cube LCD controller (LCD) HAL module driver[all …]
12 Zephyr application issues commands to one controller that are responded13 to by the simulated EEPROM connected through the other controller.16 controller and target behavior simultaneously. This is not true of all28 * Issue commands on one bus controller (operating as the bus controller) and29 verify that the data supplied by the other controller (target) match34 Transfer of commands from one bus controller to the other is40 or the controller driver has bugs, the test will fail one or more I2C
9 Expose the Zephyr Bluetooth controller support over UART to another device/CPU20 By default the controller builds use the following settings:32 Using the controller with emulators and BlueZ36 controller and expose it to Linux's BlueZ. This can be very useful for testing37 the Zephyr Link Layer with the BlueZ Host. The Zephyr BLE controller can also38 provide a modern BLE 5.0 controller to a Linux-based machine for native58 Using the controller with QEMU and Native POSIX61 In order to use the HCI UART controller with QEMU or Native POSIX you will need71 ``/dev/ttyACM0`` string to point to the serial device your controller is80 interacting with the controller and instead just be aware of it in order[all …]
10 bool "System Controller (SYSCON) drivers"12 SYSCON (System Controller) drivers. System controller node represents26 bool "Generic SYSCON (System Controller) driver"30 Enable generic SYSCON (System Controller) driver33 int "SYSCON (System Controller) driver init priority"
15 # Include paths to allow access to functions implemented in BLE controller19 ${ZEPHYR_BASE}/subsys/bluetooth/controller)21 ${ZEPHYR_BASE}/subsys/bluetooth/controller/include)23 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw)25 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/nordic)27 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/nordic/lll)
