Searched refs:values (Results 176 – 200 of 446) sorted by relevance
12345678910>>...18
| /Zephyr-latest/cmake/compiler/xcc/ |
| D | target.cmake | 69 # Appending onto any existing values lets users specify
|
| /Zephyr-latest/boards/mediatek/mt8196/ |
| D | mt8196_adsp.dts | 47 * values here appear to be hardware defaults). We represent
|
| /Zephyr-latest/samples/sensor/lsm6dso_i2c_on_i3c/ |
| D | README.rst | 12 the values for accelerometer and gyroscope.
|
| /Zephyr-latest/samples/drivers/jesd216/ |
| D | README.rst | 12 generate ``jedec,spi-nor`` devicetree property values for the device.
|
| /Zephyr-latest/tests/drivers/i2c/i2c_target_api/ |
| D | README.txt | 30 the expected values given the content known to be present on the
|
| /Zephyr-latest/scripts/coccinelle/ |
| D | int_ms_to_timeout.cocci | 7 // integer milliseconds, when they were intended to be timeout values
11 // A few expressions that are clearly integer values are also
|
| /Zephyr-latest/doc/build/version/ |
| D | index.rst | 37 Each field and the values it supports is described below. Zephyr limits the value of each numeric
40 maximum values of fields):
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | rtc.rst | 77 The calibration test tests a range of values which are printed to the
79 gotten values to ensure they are valid.
|
| /Zephyr-latest/subsys/random/ |
| D | Kconfig | 13 values that are not truly random.
85 CS random values. For this to be enabled, there must be the "zephyr,entropy"
|
| /Zephyr-latest/scripts/ci/ |
| D | test_plan.py | 251 known_boards = list_boards.find_v2_boards(lb_args).values()
352 for t in tags.values():
357 for t in tags.values():
|
| /Zephyr-latest/boards/nxp/s32z2xxdc2/support/ |
| D | startup.cmm | 9 ; valid values: flash, debug *
13 ; valid values: 0, 1 *
16 ; valid values: 0 to 3 *
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr_handlers.rst | 12 corresponding group ID values. The group ID is included in SMP headers to identify which
56 that group IDs need to be unique so other custom groups should use different values, a central index
74 note that event IDs need to be unique so other custom groups should use different values, a
|
| /Zephyr-latest/subsys/testsuite/ztest/ |
| D | Kconfig | 228 return values and expected parameters to functions.
231 int "Count of parameters or return values reserved"
235 Maximum amount of concurrent return values / expected parameters.
|
| /Zephyr-latest/doc/develop/west/ |
| D | config.rst | 63 values. You can pass ``west config`` the options ``--system``, ``--global``, or
214 trailing whitespace are ignored. That means these example values
222 Any empty elements are ignored. That means these example values are
256 - String, one the values ``"env"`` and ``"configfile"``. If set to
|
| /Zephyr-latest/soc/microchip/mec/mec15xx/ |
| D | Kconfig | 30 Allowed divider values: 1, 3, 4, 16, and 48.
|
| /Zephyr-latest/boards/m5stack/m5stack_atoms3/doc/ |
| D | index.rst | 67 try using different values by using ``--esp-baud-rate <BAUD>`` option during
|
| /Zephyr-latest/boards/m5stack/m5stack_atoms3_lite/doc/ |
| D | index.rst | 65 try using different values by using ``--esp-baud-rate <BAUD>`` option during
|
| /Zephyr-latest/boards/m5stack/m5stack_atom_lite/doc/ |
| D | index.rst | 65 try using different values by using ``--esp-baud-rate <BAUD>`` option during
|
| /Zephyr-latest/subsys/secure_storage/ |
| D | Kconfig.its_store | 25 their values to the first 30 bits.
|
| /Zephyr-latest/samples/boards/st/sensortile_box/ |
| D | README.rst | 83 sensor, you will see the accelerometer, gyro, and temperature values change.
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | clocks.rst | 16 Real time values, typically specified in milliseconds or microseconds,
101 All these values are specified using a :c:type:`k_timeout_t` value. This is
123 :c:macro:`K_CYC()` specify timeout values that will expire after specified
126 Precision of :c:type:`k_timeout_t` values is configurable, with the default
272 Millisecond values from the user may be treated any way the subsystem
353 Note that :c:func:`sys_timepoint_calc` accepts special values :c:macro:`K_FOREVER`
|
| /Zephyr-latest/drivers/pwm/ |
| D | pwm_nrfx.c | 108 return (uint16_t *)config->seq.values.p_raw; in seq_values_ptr_get()
520 .seq.values.p_raw = pwm_##idx##_seq_values, \
|
| /Zephyr-latest/include/zephyr/arch/nios2/ |
| D | linker.ld | 24 * SOC-specific linker script. All of these values can be found defined
219 * register, then we can access those values in a single instruction,
|
| /Zephyr-latest/drivers/hwinfo/ |
| D | Kconfig | 42 Always return factory pre-programmed values, stored in FCFG and ignore
43 values provided in CCFG (Customer Configuration).
|
| /Zephyr-latest/scripts/dts/python-devicetree/src/devicetree/ |
| D | dtlib.py | 178 for node in self.nodes.values():
210 for prop in self.props.values():
213 for child in self.nodes.values():
979 for prop in node.props.values()
1844 for prop in tuple(node.props.values()):
1904 for prop in aliases.props.values():
1943 for prop in node.props.values():
|
12345678910>>...18
