Home
last modified time | relevance | path

Searched +full:on +full:- +full:bus (Results 1 – 25 of 1014) sorted by relevance

12345678910>>...41

/Zephyr-latest/dts/bindings/sensor/
Dti,ina237.yaml4 # SPDX-License-Identifier: Apache-2.0
9 The <zephyr/dt-bindings/sensor/ina237.h> file should be included in the
15 include: ti,ina23x-common.yaml
24 e.g shunt voltage and bus voltage ADC conversion
31 adc-config:
41 alert-config:
43 description: Diag alert register, default matches the power-on reset value
45 adc-mode:
49 Default is the power-on reset value.
50 default: "Temperature, bus, and shunt voltage continuous"
[all …]
Dti,ina230.yaml5 # SPDX-License-Identifier: Apache-2.0
10 The <zephyr/dt-bindings/sensor/ina230.h> file should be included in the
16 include: ti,ina23x-common.yaml
25 e.g shunt voltage and bus voltage ADC conversion
28 alert-config:
30 description: Diag alert register, default matches the power-on reset value
32 adc-mode:
36 Default is the power-on reset value.
37 default: "Bus and shunt voltage continuous"
39 - "Shutdown single shot"
[all …]
Dti,ina226.yaml2 # SPDX-License-Identifier: Apache-2.0
6 The <zephyr/dt-bindings/sensor/ina226.h> file should be included in the
12 include: [sensor-device.yaml, i2c-device.yaml]
15 avg-count:
19 Default is the power-on reset value.
23 vbus-conversion-time-us:
27 Default is the power-on reset value.
31 vshunt-conversion-time-us:
35 Default is the power-on reset value.
39 operating-mode:
[all …]
/Zephyr-latest/scripts/dts/python-devicetree/tests/test-bindings/
Ddevice-on-bar-bus.yaml1 # SPDX-License-Identifier: BSD-3-Clause
3 description: Device on bar bus
5 compatible: "on-bus"
7 on-bus: "bar"
Ddevice-on-foo-bus.yaml1 # SPDX-License-Identifier: BSD-3-Clause
3 description: Device on foo bus
5 compatible: "on-bus"
7 on-bus: "foo"
Ddevice-on-any-bus.yaml1 # SPDX-License-Identifier: BSD-3-Clause
3 description: Device on any bus
5 compatible: "on-any-bus"
/Zephyr-latest/drivers/i2c/
DKconfig.stm322 # SPDX-License-Identifier: Apache-2.0
7 depends on DT_HAS_ST_STM32_I2C_V1_ENABLED || DT_HAS_ST_STM32_I2C_V2_ENABLED
10 Enable I2C support on the STM32 SoCs
17 depends on DT_HAS_ST_STM32_I2C_V1_ENABLED
20 Driver variant matching `st,stm32-i2c-v1` compatible.
25 depends on DT_HAS_ST_STM32_I2C_V2_ENABLED
28 Driver variant matching `st,stm32-i2c-v2` compatible.
34 depends on I2C_STM32_V1 || I2C_STM32_V2
41 depends on I2C_STM32_INTERRUPT
47 bool "Bus recovery support"
[all …]
DKconfig4 # SPDX-License-Identifier: Apache-2.0
10 bool "Inter-Integrated Circuit (I2C) bus drivers"
18 depends on SHELL
22 The I2C shell supports scanning, bus recovery, I2C read and write
27 depends on STATS
33 depends on LOG
34 depends on I2C_LOG_LEVEL_DBG
40 depends on I2C_DUMP_MESSAGES
41 depends on DT_HAS_ZEPHYR_I2C_DUMP_ALLOWLIST_ENABLED
45 "zephyr,i2c-dump-allowlist" and phandles to the devices that need to be traced.
[all …]
/Zephyr-latest/dts/bindings/video/
Dvideo-interfaces.yaml2 # SPDX-License-Identifier: Apache-2.0
8 data receivers, video data processors, etc. Data interfaces on these devices are
9 described by their child 'port' nodes. Configuration of a port depends on other
12 If a port can be configured to work with more than one remote device on the same
13 bus, an 'endpoint' child node must be provided for each of them. If more than one
16 scheme using '#address-cells', '#size-cells' and 'reg' properties is used.
19 specify #address-cells, #size-cells properties independently for the 'port' and
25 #address-cells = <1>;
26 #size-cells = <0>;
37 Two 'endpoint' nodes must be linked with each other via their 'remote-endpoint'
[all …]
/Zephyr-latest/doc/hardware/peripherals/
Dw1.rst3 1-Wire Bus
9 1-Wire is a low speed half-duplex serial bus using only a single wire plus
11 Similarly to I2C, 1-Wire uses a bidirectional open-collector data line,
12 and is a single master multidrop bus. This means one master initiates all data
14 The 1-Wire bus supports longer bus lines than I2C, while it reaches speeds of up
17 over a bus length of 100 meters. Using overdrive speed, 3 nodes on a bus of
19 fewer nodes on the bus may allow to reach larger bus extents.
23 .. figure:: 1-Wire_bus_topology.drawio.svg
25 :alt: 1-Wire bus topology
27 A typical 1-Wire bus topology
[all …]
Di2c.rst3 Inter-Integrated Circuit (I2C) Bus
12 `NXP I2C Bus Specification Rev 7.0 <i2c-specification_>`_. These changed
15 `I2C`_ (Inter-Integrated Circuit, pronounced "eye
16 squared see") is a commonly-used two-signal shared peripheral interface
17 bus. Many system-on-chip solutions provide controllers that communicate
18 on an I2C bus. Devices on the bus can operate in two roles: as a
20 "target" that responds to transaction commands. A I2C controller on a
24 .. _i2c-controller-api:
29 Zephyr's I2C controller API is used when an I2C peripheral controls the bus,
34 This API is supported in all in-tree I2C peripheral drivers and is
[all …]
/Zephyr-latest/drivers/clock_control/
DKconfig.npcx4 # SPDX-License-Identifier: Apache-2.0
9 depends on DT_HAS_NUVOTON_NPCX_PCC_ENABLED
16 bool "Generate LFCLK by on-chip Crystal Oscillator"
19 is generated by the on-chip Crystal Oscillator (XTOSC).
20 This includes an on-chip oscillator, to which an external crystal
24 bool "Indicates that the clock controller supports APB4 bus"
27 Selected if NPCX series supports APB4 bus.
30 bool "Indicates that the clock controller supports FIU1 bus"
33 Selected if NPCX series supports FIU1 bus.
/Zephyr-latest/tests/drivers/i2c/i2c_target_api/
DREADME.txt9 controllers on a common bus. The test is supported by a test-specific
10 driver that simulates an EEPROM with an I2C bus target interface. Data
11 is pre-loaded into the simulated devices outside the I2C API, and the
17 I2C controllers, so this behavior is now opt-in using
19 second EEPROM just to identify the bus.
23 * Use API specific to the simulated EEPROM to pre-populate the simulated
24 devices with device-specific content.
25 * Register a simulated EEPROM as a I2C target device on a bus. If
28 * Issue commands on one bus controller (operating as the bus controller) and
30 the expected values given the content known to be present on the
[all …]
/Zephyr-latest/samples/drivers/w1/scanner/
Dsample.yaml2 name: 1-Wire scanner sample
8 sample.drivers.w1.scanner.ds2482-800:
10 extra_args: DTC_OVERLAY_FILE=ds2482-800.overlay
15 - "Number of devices found on bus: .*"
21 - nrf52840dk/nrf52840
22 - nucleo_g0b1re
26 - "Number of devices found on bus: .*"
32 - nrf52840dk/nrf52840
33 - nucleo_g0b1re
37 - "Number of devices found on bus: .*"
[all …]
/Zephyr-latest/drivers/sensor/tdk/icm42688/
Dicm42688_spi.h4 * SPDX-License-Identifier: Apache-2.0
19 * @param bus SPI bus pointer
22 * @return int 0 on success, negative error code otherwise
24 int icm42688_spi_single_write(const struct spi_dt_spec *bus, uint16_t reg, uint8_t data);
32 * @param bus SPI bus pointer
36 * @return int 0 on success, negative error code otherwise
38 int icm42688_spi_update_register(const struct spi_dt_spec *bus, uint16_t reg, uint8_t mask,
47 * @param bus SPI bus pointer
51 * @return int 0 on success, negative error code otherwise
53 int icm42688_spi_read(const struct spi_dt_spec *bus, uint16_t reg, uint8_t *data, size_t len);
/Zephyr-latest/doc/build/dts/
Dbindings-syntax.rst1 .. _dt-bindings-file-syntax:
7 files are YAML files. A :ref:`simple example <dt-bindings-simple-example>` was
17 The top level of a bindings file maps keys to values. The top-level keys look
20 .. code-block:: yaml
24 This is the Vendomatic company's foo-device.
29 See https://yaml-multiline.info/ for formatting help.
35 compatible: "manufacturer,foo-device"
41 child-binding:
45 # If the node describes bus hardware, like an SPI bus controller
46 # on an SoC, use 'bus:' to say which one, like this:
[all …]
/Zephyr-latest/include/zephyr/drivers/
Dmdio.h8 * Copyright (c) 2021 IP-Logix Inc.
11 * SPDX-License-Identifier: Apache-2.0
37 /** Enable the MDIO bus device */
40 /** Disable the MDIO bus device */
43 /** Read data from MDIO bus */
47 /** Write data to MDIO bus */
51 /** Read data from MDIO bus using Clause 45 access */
55 /** Write data to MDIO bus using Clause 45 access */
64 * @brief Enable MDIO bus
74 (const struct mdio_driver_api *)dev->api; in z_impl_mdio_bus_enable()
[all …]
Dw1.h5 * SPDX-License-Identifier: Apache-2.0
10 * @brief Public 1-Wire Driver APIs
27 * @brief 1-Wire Interface
28 * @defgroup w1_interface 1-Wire Interface
38 * Count the number of slaves expected on the bus.
39 * This can be used to decide if the bus has a multidrop topology or
46 (FOR_EACH(F1, (+), DT_SUPPORTS_DEP_ORDS(node_id)) - 1)
53 * @brief Defines the 1-Wire master settings types, which are runtime configurable.
74 /** Configuration common to all 1-Wire master implementations. */
80 /** Data common to all 1-Wire master implementations. */
[all …]
/Zephyr-latest/drivers/flash/
Dflash_npcx_fiu_qspi.h4 * SPDX-License-Identifier: Apache-2.0
41 /* QSPI bus configuration for a SPI device */
45 /* Pinctrl for QSPI bus */
51 /* Configurations for the Quad-SPI peripherals */
56 * @brief Execute UMA transactions on qspi bus
58 * @param dev Pointer to the device structure for qspi bus controller instance.
61 * @retval 0 on success, -EPERM if an UMA transaction is not permitted.
67 * @brief Lock the mutex of npcx qspi bus controller and apply its configuration
69 * @param dev Pointer to the device structure for qspi bus controller instance.
70 * @param cfg Pointer to the configuration for the device on qspi bus.
[all …]
DKconfig.npcx_fiu4 # SPDX-License-Identifier: Apache-2.0
7 bool "Nuvoton NPCX QSPI Bus Flash driver"
9 depends on DT_HAS_NUVOTON_NPCX_FIU_QSPI_ENABLED
12 This option enables the QSPI Bus Flash driver for NPCX family of
18 depends on DT_HAS_NUVOTON_NPCX_FIU_NOR_ENABLED
19 depends on FLASH_NPCX_FIU_QSPI
34 depends on FLASH_NPCX_FIU_NOR
36 This option enables the QSPI NOR Flash features such as Quad-Enable,
37 4-byte address support and so on during driver initialization. Disable
66 Read Access (DRA) on QSPI bus.
/Zephyr-latest/dts/bindings/flash_controller/
Dst,stm32-xspi-nor.yaml1 # Copyright (c) 2021 - 2024 STMicroelectronics
2 # SPDX-License-Identifier: Apache-2.0
7 Representation of a serial flash on a xspi bus:
9 mx25lm51245: xspi-nor-flash@70000000 {
10 compatible = "st,stm32-xspi-nor";
12 data-mode = <XSPI_OCTO_MODE>; /* access on 8 data lines */
13 data-rate = <XSPI_DTR_TRANSFER>; /* access in DTR */
14 ospi-max-frequency = <DT_FREQ_M(50)>;
18 compatible: "st,stm32-xspi-nor"
21 - name: st,stm32-ospi-nor.yaml
[all …]
/Zephyr-latest/doc/hardware/emulator/
Dindex.rst35 * A fake driver which pretends to be actual ADC, and can be used for testing higher-level API
38 * DT binding: :dtcompatible:`zephyr,adc-emul`
43 * DT binding: :dtcompatible:`zephyr,dma-emul`
46 * Emulate an EEPROM on a flash partition
48 * DT binding: :dtcompatible:`zephyr,emu-eeprom`
53 * Emulate an EEPROM on RAM
55 * DT binding: :dtcompatible:`zephyr,sim-eeprom`
57 as a file on the host filesystem.
59 **External bus and bus connected peripheral emulators**
66 * Emulate a flash on RAM
[all …]
/Zephyr-latest/drivers/sensor/bosch/bmg160/
DKconfig4 # SPDX-License-Identifier: Apache-2.0
9 depends on DT_HAS_BOSCH_BMG160_ENABLED
17 prompt "BMG160 I2C bus speed"
23 Standard bus speed of up to 100kHz.
28 Fast bus speed of up to 400KHz.
42 depends on GPIO
43 depends on $(dt_compat_any_has_prop,$(DT_COMPAT_BOSCH_BMG160),int-gpios)
48 depends on GPIO
49 depends on $(dt_compat_any_has_prop,$(DT_COMPAT_BOSCH_BMG160),int-gpios)
58 depends on BMG160_TRIGGER_OWN_THREAD
[all …]
/Zephyr-latest/drivers/mfd/
DKconfig.ad559x2 # SPDX-License-Identifier: Apache-2.0
7 depends on DT_HAS_ADI_AD559X_ENABLED
14 bool "Analog AD559x I2C bus support"
16 depends on $(dt_compat_on_bus,$(DT_COMPAT_ADI_AD559X),i2c)
17 depends on I2C
20 bool "Analog AD559x SPI bus support"
22 depends on $(dt_compat_on_bus,$(DT_COMPAT_ADI_AD559X),spi)
23 depends on SPI
/Zephyr-latest/drivers/i2s/
DKconfig.sam_ssc1 # Atmel SAM I2S bus driver configuration options
4 # SPDX-License-Identifier: Apache-2.0
7 bool "Atmel SAM MCU family I2S (SSC) Bus Driver"
9 depends on DT_HAS_ATMEL_SAM_SSC_ENABLED
13 Enable Inter Sound (I2S) bus driver for Atmel SAM MCU family based on
31 an output or an input depending on whether the receiver is working
42 an output or an input depending on whether the receiver is working

12345678910>>...41