Searched refs:readable (Results 1 – 22 of 22) sorted by relevance
| /Zephyr-Core-3.5.0/subsys/net/lib/sockets/ |
| D | socketpair.c | 52 struct k_poll_signal readable; member
180 res = k_poll_signal_raise(&remote->readable, in spair_delete()
254 k_poll_signal_init(&spair->readable); in spair_new()
555 res = k_poll_signal_raise(&remote->readable, SPAIR_SIG_DATA); in spair_write()
676 &spair->readable in spair_read()
691 k_poll_signal_check(&spair->readable, &signaled, in spair_read()
726 k_poll_signal_reset(&spair->readable); in spair_read()
769 (*pev)->obj = &spair->readable; in zsock_poll_prepare_ctx()
882 k_poll_signal_check(&spair->readable, &signaled, &result); in zsock_poll_update_ctx()
|
| /Zephyr-Core-3.5.0/subsys/logging/ |
| D | Kconfig | 57 Module which provides formatting of log messages to a human-readable
|
| /Zephyr-Core-3.5.0/arch/nios2/ |
| D | Kconfig | 58 human-readable form, at the expense of code size. For example,
|
| /Zephyr-Core-3.5.0/arch/arm64/core/ |
| D | Kconfig | 261 Print human-readable information about exception vectors, cause codes,
262 and parameters, at a cost of code/data size for the human-readable
|
| /Zephyr-Core-3.5.0/boards/arm/rcar_h3_salvatorx/doc/ |
| D | rcar_h3_salvatorx.rst | 76 By running Zephyr on H3 Salvator-X, the software readable push buttons 'SW20',
|
| /Zephyr-Core-3.5.0/arch/arc/ |
| D | Kconfig | 384 Print human-readable information about exception vectors, cause codes,
385 and parameters, at a cost of code/data size for the human-readable
|
| /Zephyr-Core-3.5.0/doc/develop/test/ |
| D | pytest.rst | 13 Pytest is a python framework that *“makes it easy to write small, readable tests, and can scale to
|
| D | twister.rst | 1279 Robot files allow you to express interactive test scenarios in human-readable text format and execu…
|
| /Zephyr-Core-3.5.0/boards/arm/rcar_h3ulcb/doc/ |
| D | rcar_h3ulcb.rst | 94 By running Zephyr on H3ULCB, the software readable push button 'SW3' can be used as input, and the …
|
| /Zephyr-Core-3.5.0/scripts/pylib/twister/twisterlib/ |
| D | harness.py | 391 while proc.stdout.readable() and proc.poll() is None:
|
| /Zephyr-Core-3.5.0/ |
| D | LICENSE | 108 include a readable copy of the attribution notices contained
|
| /Zephyr-Core-3.5.0/doc/build/dts/ |
| D | intro-syntax-structure.rst | 6 As the name indicates, a devicetree is a tree. The human-readable text format
|
| D | howtos.rst | 410 description: <Human-readable description of your binding>
|
| /Zephyr-Core-3.5.0/doc/contribute/coding_guidelines/ |
| D | index.rst | 102 …ki.sei.cmu.edu/confluence/display/c/MSC04-C.+Use+comments+consistently+and+in+a+readable+fashion>`_
181 …ki.sei.cmu.edu/confluence/display/c/MSC04-C.+Use+comments+consistently+and+in+a+readable+fashion>`_
231 …ki.sei.cmu.edu/confluence/display/c/MSC04-C.+Use+comments+consistently+and+in+a+readable+fashion>`_
|
| /Zephyr-Core-3.5.0/doc/hardware/porting/ |
| D | board_porting.rst | 198 model = "A human readable name";
|
| /Zephyr-Core-3.5.0/doc/services/logging/ |
| D | index.rst | 678 Dictionary-based logging, instead of human readable texts, outputs the log
|
| /Zephyr-Core-3.5.0/doc/develop/ |
| D | modules.rst | 972 - ``description``: Human-readable description of the binary blob
|
| /Zephyr-Core-3.5.0/doc/ |
| D | zephyr.doxyfile.in | 189 # less readable) file names. This can be useful is your file systems doesn't
351 # according to the Markdown format, which allows for more readable
|
| /Zephyr-Core-3.5.0/doc/releases/ |
| D | release-notes-2.7.rst | 647 * Fixed a bug, where notifications were generated on changes to non-readable
|
| D | release-notes-3.2.rst | 1880 * :github:`50214` - Missing human readable names in names file od deive structure
|
| D | release-notes-3.3.rst | 1478 which is a human-readable string describing the sensor.
|
| /Zephyr-Core-3.5.0/samples/modules/tflite-micro/hello_world/train/ |
| D | train_hello_world_model.ipynb | 1527 "To make the flatter part of the graph more readable, let's skip the first 50 epochs:"
|
