Searched full:relation (Results 1 – 25 of 30) sorted by relevance
12
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | flash.rst | 11 Offsets used by the user API are expressed in relation to
|
| /Zephyr-latest/include/zephyr/drivers/sensor/ |
| D | tmag5273.h | 39 * Define axis relation measurements.
|
| /Zephyr-latest/subsys/mgmt/mcumgr/transport/ |
| D | Kconfig.shell | 28 must satisfy the following relation:
|
| D | Kconfig.uart | 60 This value must satisfy the following relation:
|
| D | Kconfig.udp | 61 This value must satisfy the following relation:
|
| D | Kconfig | 46 the following relation:
|
| /Zephyr-latest/doc/project/ |
| D | issues.rst | 6 To maintain traceability and relation between proposals, changes, features, and
|
| /Zephyr-latest/dts/bindings/charger/ |
| D | maxim,max20335-charger.yaml | 65 Recharge threshold in relation to BatReg.
|
| /Zephyr-latest/dts/bindings/display/ |
| D | istech,ist3931.yaml | 77 description: Reverse the lit and unlit display relation between RAM bit data and LCD cell
|
| /Zephyr-latest/include/zephyr/drivers/adc/ |
| D | adc_npcx_threshold.h | 20 /* Sets relation between measured value and assetion threshold value.*/
|
| /Zephyr-latest/include/zephyr/sensing/ |
| D | sensing_datatypes.h | 28 * The 'base_timestamp' is for readings[0], the 'timestamp_delta' is relation
|
| /Zephyr-latest/doc/services/storage/flash_map/ |
| D | flash_map.rst | 64 Partition offset shall be expressed in relation to the flash memory beginning
|
| /Zephyr-latest/tests/kernel/spinlock/src/ |
| D | spinlock_fairness.c | 108 * @details This test verifies a spinlock acquisition fairness in relation
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 101 :alt: IEC 61508 relation to other standards
104 IEC 61508 relation to other standards
|
| /Zephyr-latest/drivers/console/ |
| D | Kconfig | 231 setting's value must satisfy the following relation:
|
| /Zephyr-latest/doc/build/dts/api/ |
| D | api.rst | 137 nodes. Dependency tracking relies on a binary "depends on" relation between
140 depends on" relation:
|
| /Zephyr-latest/include/zephyr/net/ |
| D | ptp_time.h | 75 * ranging applications and ibid., section 6.7.6 for the relation between guard
|
| /Zephyr-latest/drivers/dma/ |
| D | dma_dw_common.h | 240 * the relation between msize and burst_elems should be
|
| /Zephyr-latest/doc/services/sensing/ |
| D | index.rst | 200 The **timestamp_delta** is in relation to the previous **readings** (or the **base_timestamp**)
|
| /Zephyr-latest/include/zephyr/fs/ |
| D | fcb.h | 231 * Function to obtain fcb entry location in relation to entry pointed by
|
| /Zephyr-latest/tests/kernel/threads/thread_stack/src/ |
| D | main.c | 244 /* These should be exactly the same. We have an equivalence relation: in stack_buffer_scenarios()
|
| /Zephyr-latest/drivers/regulator/ |
| D | regulator_cp9314.c | 494 * burned on the CP9314 device. The PTE_2 values in relation to the OTP table names in regulator_cp9314_otp_init()
|
| /Zephyr-latest/include/zephyr/drivers/ |
| D | counter.h | 84 * Ticks relation to counter value. If set ticks are treated as absolute value,
|
| /Zephyr-latest/subsys/bluetooth/mesh/ |
| D | access.c | 75 /** Type of relation; value in range 0x00-0xFE marks correspondence
1090 LOG_WRN("Unused space in relation list: %d", in bt_mesh_comp_register()
1727 /* For vendor models, determine the offset within the model relation list
|
| /Zephyr-latest/drivers/adc/ |
| D | adc_npcx.c | 66 * Sets relation between measured value and assetion threshold value.
|
12
