Home
last modified time | relevance | path

Searched refs:measure (Results 1 – 25 of 41) sorted by relevance

12

/Zephyr-latest/drivers/usb_c/vbus/
Dusbc_vbus_tcpci.c28 uint16_t measure; in tcpci_measure() local
33 ret = tcpci_read_reg16(&cfg->i2c, TCPC_REG_VBUS_VOLTAGE, &measure); in tcpci_measure()
38 *vbus_meas = TCPC_REG_VBUS_VOLTAGE_VBUS(measure); in tcpci_measure()
45 int measure; in tcpci_check_level() local
48 ret = tcpci_measure(dev, &measure); in tcpci_check_level()
55 return (measure < PD_V_SAFE_0V_MAX_MV); in tcpci_check_level()
57 return (measure >= PD_V_SAFE_5V_MIN_MV); in tcpci_check_level()
59 return (measure < TC_V_SINK_DISCONNECT_MAX_MV); in tcpci_check_level()
84 .measure = tcpci_measure,
Dusbc_vbus_numaker.c115 .measure = numaker_vbus_measure,
Dusbc_vbus_adc.c195 .measure = adc_vbus_measure,
/Zephyr-latest/include/zephyr/drivers/usb_c/
Dusbc_vbus.h37 int (*measure)(const struct device *dev, int *vbus_meas); member
71 return api->measure(dev, meas); in usbc_vbus_measure()
/Zephyr-latest/doc/hardware/peripherals/sensor/
Dchannels.rst7 a sensor device can measure.
10 the same physical property (e.g. acceleration); or because they can measure
/Zephyr-latest/drivers/clock_control/
DKconfig.stm3263 This property controls how much LSI periods are required for each measure.
64 Bigger window sizes increase accuracy of the measure, but increase the time
66 size makes each measure roughly 42µs slower in the worst case.
83 the amount of time specified in this property between each measure. This
90 measurements - the result of a single measure performed at boot will be
/Zephyr-latest/doc/hardware/peripherals/
Dusbc_vbus.rst17 The USB-C VBUS device driver presents an API that's used to control and measure
Dfuel_gauge.rst18 Fundamentally, a property is a quantity that a fuel gauge device can measure.
Dcharger.rst32 measure.
/Zephyr-latest/tests/benchmarks/sched_userspace/
DREADME.rst4 This is a scheduler microbenchmark, designed to measure minimum
/Zephyr-latest/tests/kernel/timer/timer_behavior/
DKconfig61 connected to a GPIO pin is used to measure time behaviour.
68 connected to a GPIO pin is used to measure time behaviour.
/Zephyr-latest/samples/sensor/max30101/
DREADME.rst17 enable the green LED and measure the reflected light with a photodiode. The raw
/Zephyr-latest/tests/benchmarks/sched/
DREADME.rst4 This is a scheduler microbenchmark, designed to measure minimum
/Zephyr-latest/samples/userspace/syscall_perf/
DREADME.rst9 The goal of this sample application is to measure the performance loss when a
/Zephyr-latest/tests/drivers/regulator/voltage/boards/
Drpi_pico.overlay13 * Scraping the resist on there and soldering wire to make it able to measure by ADC.
/Zephyr-latest/samples/sensor/ams_iAQcore/
DREADME.rst11 measure CO2 equivalent and VOC. The CO2 value is a predicted value derived from
/Zephyr-latest/samples/subsys/usb/uac2_implicit_feedback/
DREADME.rst18 Target must be able to measure I2S block start (i.e. first sample from output
/Zephyr-latest/samples/sensor/bmi270/
DREADME.rst11 measure data at 100Hz. The result is written to the console.
/Zephyr-latest/boards/shields/mikroe_weather_click/doc/
Dindex.rst11 measure relative humidity, barometric pressure, and ambient temperature.
/Zephyr-latest/boards/espressif/esp32c3_rust/
Desp32c3_rust.dts107 measure-mode = "normal";
/Zephyr-latest/samples/basic/minimal/
DREADME.rst10 can be used to measure Zephyr's minimal ROM footprint in different
/Zephyr-latest/samples/subsys/zbus/benchmark/
DREADME.rst7 This sample implements an application to measure the time for sending 256KB from the producer to the
/Zephyr-latest/samples/boards/nordic/clock_skew/
DREADME.rst9 This sample uses the API for correlating time sources to measure the
/Zephyr-latest/samples/boards/nordic/battery/
DREADME.rst10 infrastructure to measure the voltage of the device power supply. Two
/Zephyr-latest/boards/st/stm32g071b_disco/
Dstm32g071b_disco.dts141 * Use U10, INA230 to measure VBUS. I2C Address: 0x40

12