Home
last modified time | relevance | path

Searched refs:reported (Results 1 – 25 of 66) sorted by relevance

123

/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/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()
/Zephyr-latest/drivers/gnss/
DKconfig.luatos_air530z27 be reported in the satellites callback.
DKconfig.generic28 device is actually tracking, just how many of those can be reported
DKconfig.u_blox_m829 device is actually tracking, just how many of those can be reported
/Zephyr-latest/samples/drivers/gnss/
DREADME.rst29 gnss reported 2 satellites!
/Zephyr-latest/doc/project/
Dcommunication.rst16 In general, bug reports and other issues should be reported as `GitHub Issues
Dissues.rst19 It could happen that the issue being reported is identified as a regression,
/Zephyr-latest/tests/drivers/build_all/sensor/
DKconfig18 test, interpolated from the sensor's reported lower and upper sample
/Zephyr-latest/samples/drivers/charger/
DREADME.rst22 the battery pack. Additionally, the sample intentionally does not respond to the reported charger
/Zephyr-latest/samples/boards/st/backup_sram/
DREADME.rst40 Next reported value should be: 12
/Zephyr-latest/samples/subsys/usb/uac2_implicit_feedback/
DREADME.rst19 buffer gets out) relative to USB SOF. The relative offset must be reported with
/Zephyr-latest/subsys/usb/device/class/hid/
Dcore.c316 bool reported = false; in hid_sof_handler() local
332 if (diff < 2 && reported == false) { in hid_sof_handler()
339 reported = true; in hid_sof_handler()
341 } else if (diff == 0 && reported == true) { in hid_sof_handler()
/Zephyr-latest/samples/sensor/qdec/
DREADME.rst71 The reported increment/decrement can be larger/smaller than the one shown
/Zephyr-latest/samples/net/zperf/
DREADME.rst17 an error message like this is printed and the server reported statistics
/Zephyr-latest/doc/services/input/
Dindex.rst19 multi-axis device have been reported.
32 used to indicate which device reported the event and can be used by subscribers
/Zephyr-latest/cmake/toolchain/cross-compile/
Dtarget.cmake13 set(SYSROOT_DIR "${reported_sysroot}" CACHE INTERNAL "Sysroot reported by ${CMAKE_C_COMPILER}")
/Zephyr-latest/doc/security/
Dreporting.rst9 Vulnerabilities to the Zephyr project may be reported via email to the
14 view the issues that they have reported.
94 The Zephyr Security Subcommittee shall review the reported
/Zephyr-latest/doc/connectivity/networking/api/
Dzperf.rst17 an error message like this is printed and the server reported statistics
/Zephyr-latest/samples/sensor/ccs811/
DREADME.rst39 reported measurements of about 400 ppm eC02 and 0 ppb eTVOC.
/Zephyr-latest/samples/sensor/mcux_lpcmp/
DREADME.rst23 The output value of the LPCMP is reported on the console.
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dhealth_srv.rst27 vendor specific. The list of faults are always reported with a company ID to
Dblob_cli.rst104 non-overlapping block size range, it will be dropped. Lost Target nodes will be reported through the
122 <bt_mesh_blob_cli_cb.end>` callback. Lost Target nodes will be reported through the
/Zephyr-latest/drivers/entropy/
DKconfig.stm3262 error is reported.
/Zephyr-latest/samples/sensor/mcux_acmp/
DREADME.rst22 The output value of the analog comparator is reported on the console.

123