Home
last modified time | relevance | path

Searched full:reported (Results 1 – 25 of 207) sorted by relevance

123456789

/Zephyr-latest/tests/benchmarks/thread_metric/
DKconfig21 is reported every 30 seconds.
28 on each context switch. The sum total of the counters is reported
40 takes that semaphore. The sum total of the counters is reported
51 of a thread. The total number of context switches is reported every
59 is reported every 30 seconds.
66 This number is reported every 30 seconds.
73 cyclical pattern. The total number of context switches is reported
81 is reported every 30 seconds.
/Zephyr-latest/dts/bindings/input/
Dcirque,pinnacle-common.yaml29 Data output mode in which position is reported. In the relative mode
30 each position is reported as relative to the last position. In the
31 absolute mode absolute coordinates are reported.
50 In the absolute mode enable clipping of reported coordinates which are
57 The minimum X value which can be reported.
63 The maximum X value which can be reported.
69 The minimum Y value which can be reported.
75 The maximum Y value which can be reported.
Dxptek,xpt2046.yaml28 description: minimum raw X value reported.
33 description: minimum raw Y value reported.
38 description: maximum raw X value reported.
43 description: maximum raw Y value reported.
Dst,stmpe811.yaml20 Signed raw X axis start for scaling the reported coordinates.
26 Signed raw Y axis start for scaling the reported coordinates.
32 Raw X axis end for scaling the reported coordinates.
38 Raw Y axis end for scaling the reported coordinates.
Dtouchscreen-common.yaml13 Horizontal resolution of touchscreen (maximum x coordinate reported + 1). The default
21 Vertical resolution of touchscreen (maximum y coordinate reported + 1). The default
/Zephyr-latest/samples/boards/microchip/mec15xxevb_assy6853/power_management/src/
Dpower_mgmt.h19 * @param use_logging test progress will be reported using logging,
31 * @param use_logging test progress will be reported using logging,
/Zephyr-latest/tests/net/lib/lwm2m/content_json/src/
Dmain.c176 zassert_true(ret >= 0, "Error reported"); in ZTEST()
218 zassert_true(ret >= 0, "Error reported"); in ZTEST()
260 zassert_true(ret >= 0, "Error reported"); in ZTEST()
302 zassert_true(ret >= 0, "Error reported"); in ZTEST()
336 zassert_true(ret >= 0, "Error reported"); in ZTEST()
378 zassert_true(ret >= 0, "Error reported"); in ZTEST()
419 zassert_true(ret >= 0, "Error reported"); in ZTEST()
463 zassert_true(ret >= 0, "Error reported"); in ZTEST()
504 zassert_true(ret >= 0, "Error reported"); in ZTEST()
536 zassert_true(ret >= 0, "Error reported"); in ZTEST()
[all …]
/Zephyr-latest/tests/drivers/gnss/gnss_api/src/
Dtest_enabled_systems.c22 static bool test_reported_are_expected(gnss_systems_t reported, gnss_systems_t expected) in test_reported_are_expected() argument
24 return ((~expected) & reported) == 0; in test_reported_are_expected()
82 zassert_true(expected, "unexpected systems reported (%u != %u)", in test_validate_satellites()
/Zephyr-latest/include/zephyr/bluetooth/mesh/
Dhealth_srv.h34 * reported for any Company ID, and the same fault may be presented
44 * ID is reported for each call.
64 * Company ID should be reported.
69 * reported for any Company ID, and the same fault may be presented
109 * be reported back to the client if the test execution didn't start.
/Zephyr-latest/include/zephyr/ipc/
Drpmsg_service.h39 * @retval <0 an other negative errno code, reported by rpmsg.
52 * @retval <0 an error code, reported by rpmsg.
/Zephyr-latest/include/zephyr/input/
Dinput_touch.h80 * @param x X coordinate as reported by the controller
81 * @param y Y coordinate as reported by the controller
/Zephyr-latest/drivers/gnss/
DKconfig.generic28 device is actually tracking, just how many of those can be reported
DKconfig.luatos_air530z27 be reported in the satellites callback.
DKconfig.u_blox_m829 device is actually tracking, just how many of those can be reported
/Zephyr-latest/tests/drivers/build_all/sensor/
DKconfig18 test, interpolated from the sensor's reported lower and upper sample
/Zephyr-latest/doc/project/
Dcommunication.rst16 In general, bug reports and other issues should be reported as `GitHub Issues
/Zephyr-latest/dts/bindings/dai/
Dnxp,dai-esai.yaml40 Use this property to set the FIFO depth that will be reported
50 not use this property at all, in which case the reported value will be
/Zephyr-latest/samples/drivers/charger/
DREADME.rst22 the battery pack. Additionally, the sample intentionally does not respond to the reported charger
/Zephyr-latest/subsys/ipc/rpmsg_service/
Drpmsg_backend.h36 * @retval <0 Initialization error reported by OpenAMP
/Zephyr-latest/subsys/fs/fcb/
Dfcb_walk.c13 * only elements with that flash_sector are reported.
/Zephyr-latest/samples/drivers/gnss/
DREADME.rst29 gnss reported 2 satellites!
/Zephyr-latest/tests/net/lib/lwm2m/content_senml_cbor/src/
Dmain.c237 zassert_true(ret >= 0, "Error reported"); in ZTEST()
325 zassert_true(ret >= 0, "Error reported"); in ZTEST()
413 zassert_true(ret >= 0, "Error reported"); in ZTEST()
501 zassert_true(ret >= 0, "Error reported"); in ZTEST()
550 zassert_true(ret >= 0, "Error reported"); in ZTEST()
681 zassert_true(ret >= 0, "Error reported"); in ZTEST()
750 zassert_true(ret >= 0, "Error reported"); in ZTEST()
843 zassert_true(ret >= 0, "Error reported"); in ZTEST()
892 zassert_true(ret >= 0, "Error reported"); in test_put_opaque()
938 zassert_true(ret >= 0, "Error reported"); in ZTEST()
[all …]
/Zephyr-latest/subsys/debug/
Dasan_hacks.c31 * leak check; "<unknown module>" is reported in the stack traces during the
/Zephyr-latest/samples/boards/st/backup_sram/src/
Dmain.c47 printk("Next reported value should be: %d\n", backup.value); in main()
/Zephyr-latest/samples/boards/st/backup_sram/
DREADME.rst40 Next reported value should be: 12

123456789