Home
last modified time | relevance | path

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

/Zephyr-Core-2.7.6/samples/sensor/mcux_acmp/
DREADME.rst16 The output value of the analog comparator is reported on the console.
/Zephyr-Core-2.7.6/samples/boards/stm32/backup_sram/
DREADME.rst40 Next reported value should be: 12
/Zephyr-Core-2.7.6/subsys/usb/class/hid/
Dcore.c317 bool reported = false; in hid_sof_handler() local
333 if (diff < 2 && reported == false) { in hid_sof_handler()
340 reported = true; in hid_sof_handler()
342 } else if (diff == 0 && reported == true) { in hid_sof_handler()
/Zephyr-Core-2.7.6/doc/development_process/
Dissues.rst19 It could happen that the issue being reported is identified as a regression,
/Zephyr-Core-2.7.6/doc/security/
Dreporting.rst9 Vulnerabilities to the Zephyr project may be reported via email to the
14 view the issues that they have reported.
73 The Zephyr Security Subcommittee shall review the reported
Dsecurity-overview.rst456 modules in all of its stages and the management of reported security
/Zephyr-Core-2.7.6/samples/sensor/ccs811/
DREADME.rst38 reported measurements of about 400 ppm eC02 and 0 ppb eTVOC.
/Zephyr-Core-2.7.6/doc/reference/bluetooth/mesh/
Dhealth_srv.rst25 vendor specific. The list of faults are always reported with a company ID to
/Zephyr-Core-2.7.6/samples/net/zperf/
DREADME.rst16 an error message like this is printed and the server reported statistics
/Zephyr-Core-2.7.6/subsys/debug/
DKconfig120 check, "<unknown module>" is reported in the stack traces during the leak
309 debugging information to be reported at runtime.
320 exception is reported.
/Zephyr-Core-2.7.6/
DCODE_OF_CONDUCT.md58 reported by contacting the project team at conduct@zephyrproject.org.
/Zephyr-Core-2.7.6/doc/guides/networking/
Dqemu_user_setup.rst66 this command line will be reported by QEMU only. Here's what this particular
/Zephyr-Core-2.7.6/doc/reference/bluetooth/
Dhci.txt82 the controller. By default no vendor events are reported.
425 executed. Until then the current BD_ADDR is still active and reported by
1114 The event is reported by default unless masked away by Set_Event_Mask command.
1161 The event is only reported when unmasked by Set_Event_Mask command.
1226 The event is only reported when unmasked by Set_Event_Mask command.
/Zephyr-Core-2.7.6/subsys/mgmt/osdp/
DKconfig.pd106 open/closed circuit status to the reported active/inactive status. (User
/Zephyr-Core-2.7.6/doc/reference/api/
Dterminology.rst173 generally provide a mechanism by which operation completion is reported,
/Zephyr-Core-2.7.6/doc/guides/west/
Dtroubleshooting.rst102 Neither macOS nor Windows users have reported this issue. There have been no
/Zephyr-Core-2.7.6/subsys/net/lib/lwm2m/
Dlwm2m_engine.c3218 bool reported = false; in lwm2m_discover_handler() local
3277 reported = true; in lwm2m_discover_handler()
3311 reported = true; in lwm2m_discover_handler()
3338 reported = true; in lwm2m_discover_handler()
3343 return reported ? 0 : -ENOENT; in lwm2m_discover_handler()
/Zephyr-Core-2.7.6/doc/guides/docs/
Dindex.rst237 The most common warning reported by Sphinx/Breathe is related to duplicate C
/Zephyr-Core-2.7.6/doc/contribute/
Dindex.rst211 system to see what's been reported on the issue you'd like to address. Have a
376 If you want to override checkpatch verdict and push you branch despite reported
/Zephyr-Core-2.7.6/doc/guides/test/
Dtwister.rst670 some more details can be given (e.g. link to a reported issue). These comments will also
/Zephyr-Core-2.7.6/doc/reference/usermode/
Dsyscalls.rst460 reported, to a caller, with returning the ``-ENOMEM`` . The ``Z_OOPS()``
/Zephyr-Core-2.7.6/doc/releases/
Drelease-notes-1.11.rst440 * :github:`5938` - Incorrectly reported coverage changes
Drelease-notes-2.7.rst139 exponentiation was 3 or smaller. Found and reported by Zili KOU,
1136 * Fixed a bug, where Register failures were reported as success to the
1872 …37652` - bluetooth: tests/bluetooth/bsim_bt/bsim_test_advx reported success but still reported fai…
Drelease-notes-2.3.rst955 * :github:`24634` - Invalid pin reported in gpio callback
/Zephyr-Core-2.7.6/cmake/
Dextensions.cmake857 # 0.1.0 and 0.3.0, and user provides 0.2.0, then an error is reported