Home
last modified time | relevance | path

Searched full:controller (Results 1 – 25 of 2464) sorted by relevance

12345678910>>...99

/Zephyr-latest/drivers/usb/device/
DKconfig7 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"
48 bool "USB device controller driver for STM32 devices"
[all …]
/Zephyr-latest/dts/arm/infineon/cat1a/legacy/
Dpsoc6_cm0.dtsi29 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 …]
/Zephyr-latest/tests/bluetooth/controller/uut/
DCMakeLists.txt10 ${ZEPHYR_BASE}/subsys/bluetooth/controller/util/mem.c
11 ${ZEPHYR_BASE}/subsys/bluetooth/controller/util/memq.c
12 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/ull_tx_queue.c
13 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/ull_conn.c
14 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/ll_feat.c
15 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/ull_llcp_conn_upd.c
16 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/ull_llcp_cc.c
17 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/ull_llcp_pdu.c
18 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/ull_llcp_remote.c
19 ${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/ull_llcp_local.c
[all …]
/Zephyr-latest/drivers/interrupt_controller/
DKconfig.dw5 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 interrupt
19 controller which combines several sources of interrupt into one line
20 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 Controller
36 the ISRs for Designware Interrupt Controller are assigned.
39 int "Init priority for DW interrupt controller"
[all …]
DKconfig.nxp_s321 # Configuration for NXP S32 external interrupt controller
7 bool "External interrupt controller driver for NXP S32 MCUs"
13 External interrupt controller driver for NXP S32 MCUs
22 Number of SIUL2 external interrupts per controller. This is a SoC
35 bool "Wake-up Unit interrupt controller driver for NXP S32 MCUs"
39 Wake-up Unit interrupt controller driver for NXP S32 MCUs
48 Number of WKPU external and internal sources per controller. This is
/Zephyr-latest/dts/xtensa/nxp/
Dnxp_imx8qxp.dtsi10 irqsteer: interrupt-controller@51080000 {
18 master0: interrupt-controller@0 {
21 interrupt-controller;
26 master1: interrupt-controller@1 {
29 interrupt-controller;
34 master2: interrupt-controller@2 {
37 interrupt-controller;
42 master3: interrupt-controller@3 {
45 interrupt-controller;
50 master4: interrupt-controller@4 {
[all …]
Dnxp_imx8qm.dtsi11 irqsteer: interrupt-controller@510a0000 {
19 master0: interrupt-controller@0 {
22 interrupt-controller;
27 master1: interrupt-controller@1 {
30 interrupt-controller;
35 master2: interrupt-controller@2 {
38 interrupt-controller;
43 master3: interrupt-controller@3 {
46 interrupt-controller;
51 master4: interrupt-controller@4 {
[all …]
/Zephyr-latest/samples/drivers/i2c/rtio_loopback/
DREADME.rst5 Perform I2C transfers between I2C controller and custom I2C target using RTIO.
11 using RTIO. It uses up to two I2C controllers, acting as I2C controller and
19 * Two I2C controllers, one supporting the I2C controller role, one supporting the
21 * An I2C controller supporting both I2C controller and peripheral role
33 I2C controller will act as the controller, and which as the peripheral, note
34 that this could be the same controller. This is done using the devicetree
35 aliases ``i2c-controller`` and ``i2c-controller-target`` respectively:
41 i2c-controller = &i2c1;
42 i2c-controller-target = &i2c2;
/Zephyr-latest/drivers/reset/
DKconfig1 # Reset Controller driver configuration options
7 # Reset Controller options
10 bool "Reset Controller drivers"
12 Reset Controller drivers. Reset node represents a region containing
13 information about reset controller device. The typical use-case is
15 controller node together with some reset information.
20 int "Reset Controller driver init priority"
23 This option controls the priority of the reset controller device
28 comment "Reset Controller Drivers"
/Zephyr-latest/dts/bindings/gpio/
Dnxp,s32-gpio.yaml5 NXP S32 GPIO controller.
7 The GPIO controller provides the option to route external input pad interrupts
8 to either the SIUL2 EIRQ interrupt controller or, when available on the SoC,
9 the WKPU interrupt controller. By default, GPIO interrupts are routed to the
10 SIUL2 EIRQ interrupt controller.
12 To route external interrupts to the WKPU interrupt controller, the GPIO
14 the following snippet of devicetree source code instructs the GPIO controller
15 to route the interrupt from pin 9 of `gpioa` to the WKPU interrupt controller:
24 interrupt controller allows for the allocation of distinct interrupt
26 the fact that each interrupt controller features its own interrupt vector.
[all …]
/Zephyr-latest/drivers/sdhc/
DKconfig.intel13 validated using intel's EMMC host controller.
17 bool "EMMC host controller interrupt mode"
20 EMMC host controller interrupt mode support.
23 bool "EMMC host controller DMA mode"
26 EMMC host controller DMA mode support.
29 bool "EMMC host controller ADMA mode"
32 EMMC host controller ADMA mode support.
35 int "EMMC host controller ADMA Descriptor size"
39 EMMC host controller ADMA Descriptor size.
/Zephyr-latest/drivers/i2c/
Di2c_npcx_controller.h17 * @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 …]
/Zephyr-latest/include/zephyr/devicetree/
Dcan.h26 * @brief Get the minimum transceiver bitrate for a CAN controller
29 * controller. If no CAN transceiver is present in the devicetree, the minimum
30 * bitrate will be that of the CAN controller.
42 * compatible = "vnd,can-controller";
47 * compatible = "vnd,can-controller";
56 * compatible = "vnd,can-controller";
71 * @param min minimum bitrate supported by the CAN controller
72 * @return the minimum bitrate supported by the CAN controller/transceiver combination
80 * @brief Get the maximum transceiver bitrate for a CAN controller
83 * controller. If no CAN transceiver is present in the devicetree, the maximum
[all …]
Dinterrupt_controller.h9 * @brief Interrupt controller devicetree macro public API header file.
23 * @defgroup devicetree-interrupt_controller Devicetree Interrupt Controller API
29 * @brief Get the aggregator level of an interrupt controller
34 * @param node_id node identifier of an interrupt controller
36 * @return Level of the interrupt controller
41 * @brief Get the aggregator level of a `DT_DRV_COMPAT` interrupt controller
46 * @param inst instance of an interrupt controller
48 * @return Level of the interrupt controller
/Zephyr-latest/subsys/bluetooth/common/
DKconfig16 Controller. This value does not include the HCI ACL header.
19 Controller.
22 by the Controller and use the smallest value supported by both the
23 Host and the Controller.
27 The Controller will return this value in the HCI LE Read Buffer
29 Layer transmission size then the Controller will perform
42 Controller. This determines the maximum amount of data packets the
43 Host can have queued in the Controller before waiting for the
48 The Controller will return this value in the HCI LE Read Buffer Size
62 Maximum support ACL size of data packets sent from the Controller to
[all …]
/Zephyr-latest/drivers/usb/udc/
DKconfig.virtual5 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.
DKconfig.rpi_pico5 bool "Driver for an Raspberry PI Pico USB device controller"
10 Driver for an Raspberry PI Pico USB device controller.
15 int "UDC controller driver internal thread stack size"
18 Device controller driver internal thread stack size.
21 int "UDC controller driver thread priority"
24 Device controller driver thread priority.
DKconfig.skeleton5 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.
/Zephyr-latest/doc/connectivity/bluetooth/
Dbluetooth-arch.rst30 * **Controller**: The Controller implements the Link Layer (LE LL), the
41 Host Controller Interface
45 communicate with a Controller. This is called the Host Controller Interface
48 can send to a Controller and the events that it can expect in return, and also
50 ensures that different Host and Controller implementations can communicate
60 it possible to implement the Host and Controller on different platforms. The two
66 Controller communicate directly through function calls and queues in RAM. The
73 one running the Application and the Host, and a second one with the Controller
76 Hosts when using the Zephyr OS as a Controller. Since HCI ensures
77 interoperability among Host and Controller implementations, including of course
[all …]
/Zephyr-latest/dts/x86/intel/
Dgpio_common.dtsi7 #include <zephyr/dt-bindings/interrupt-controller/intel-ioapic.h>
17 gpio-controller;
26 gpio-controller;
35 gpio-controller;
44 gpio-controller;
53 gpio-controller;
62 gpio-controller;
71 gpio-controller;
80 gpio-controller;
89 gpio-controller;
[all …]
/Zephyr-latest/drivers/memc/
DKconfig.stm325 bool "STM32 Flexible Memory Controller (FMC)"
10 Enable STM32 Flexible Memory Controller.
15 bool "STM32 FMC SDRAM controller"
21 Enable STM32 FMC SDRAM controller.
24 bool "STM32 FMC NOR/PSRAM controller"
31 Enable STM32 FMC NOR/PSRAM controller.
/Zephyr-latest/include/zephyr/drivers/
Dmspi.h159 * @brief MSPI controller device specific configuration mask
215 * The controller can identify its devices and determine whether the access is
226 * @brief MSPI controller configuration
243 /** @brief Peripheral number from 0 to host controller peripheral limit. */
247 /** @brief Whether to re-initialize controller */
262 * @brief MSPI controller device specific configuration
304 * @brief MSPI controller XIP configuration
320 * @brief MSPI controller scramble configuration
345 * using the controller inner CE logic.
428 /** @brief Pointer to the bus controller */
[all …]
/Zephyr-latest/tests/bluetooth/controller/ctrl_tx_buffer_alloc/
Dtestcase.yaml7 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:
/Zephyr-latest/dts/bindings/mspi/
Dmspi-controller.yaml28 Indicate MSPI controller or peripheral mode of the controller.
29 The controller driver may use this during initialization.
38 The controller driver may check this setting against its
45 The controller driver may check this setting against its
51 Indicate whether the controller driver enables support for
53 At the minimum, the controller driver should use it to allow
82 chip select controller gpio0, pin 23, and devicetree
84 controller gpio1, pin 10, and flags GPIO_ACTIVE_LOW. Additional
93 controller has dedicated CE pin, this field should be defined to
94 help manage multiple devices on the same MSPI controller.
/Zephyr-latest/tests/kernel/interrupt/
Dmultilevel_irq.overlay11 test_cpu_intc: interrupt-controller {
15 interrupt-controller;
18 test_l1_irq: interrupt-controller@bbbbcccc {
21 interrupt-controller;
27 test_l2_irq: interrupt-controller@bbbccccc {
30 interrupt-controller;
44 test_l1_irq_inc: interrupt-controller@bbbbdccc {
47 interrupt-controller;
53 test_l2_irq_inc: interrupt-controller@bbbbdcdc {
56 interrupt-controller;

12345678910>>...99