Searched refs:look (Results 76 – 100 of 108) sorted by relevance
12345
| /Zephyr-latest/doc/kernel/services/ |
| D | polling.rst | 55 nature of the kernel. The caller must look at the state of all the poll events
|
| D | interrupts.rst | 573 This is used by the common software IRQ handler to look up the ISR and its
688 configures an interrupt it will look for a free vector in the appropriate range
|
| /Zephyr-latest/doc/services/storage/zms/ |
| D | zms.rst | 130 It must look for a closed sector followed by an open one, then within the open sector, it finds
137 To avoid rewriting the same data with the same ID again, ZMS must look in all the sectors if the
|
| /Zephyr-latest/boards/snps/em_starterkit/doc/ |
| D | index.rst | 149 * If you want to know more about how to use this board, you can take a look
|
| /Zephyr-latest/doc/connectivity/usb/device_next/ |
| D | usb_device.rst | 252 Simplified, the interrupt handler should look something like:
|
| /Zephyr-latest/doc/services/storage/settings/ |
| D | index.rst | 134 The FCB, non-volatile storage (NVS) and ZMS backends look for a fixed
|
| /Zephyr-latest/boards/acrn/acrn/doc/ |
| D | index.rst | 88 Find the "<vm id="0">...<os_config>" tag that will look something like this:
|
| /Zephyr-latest/boards/microchip/mec15xxevb_assy6853/doc/ |
| D | index.rst | 309 #. Final wiring for the board should look like this:
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-le-host.rst | 315 configuration options needed will look something like the following:
|
| /Zephyr-latest/doc/build/dts/ |
| D | phandles.rst | 290 Therefore, almost all GPIO controller nodes you will see in practice will look
|
| D | intro-syntax-structure.rst | 93 The DTS would look something like this:
|
| D | howtos.rst | 476 * the zephyr Git repository to look for example drivers using this style).
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | i3c.rst | 311 any calls to I2C API will need to look up the corresponding device
|
| /Zephyr-latest/doc/develop/west/ |
| D | built-in.rst | 132 Some branch names might look like short SHAs, like ``deadbeef``. West treats
|
| /Zephyr-latest/doc/services/shell/ |
| D | index.rst | 294 Abstract code for this task would look like this:
322 This is how it would look like in the shell:
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 567 For an application, this would look like this:
656 A Kconfig fragment could look as:
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | syscalls.rst | 117 user mode, or exclusively in supervisor mode. The system will look for
254 provided by the user to look up the appropriate unmarshalling function for that
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | setting.rst | 118 :kbd:`/`), or look up the symbol in the :ref:`Kconfig search page
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | clocks.rst | 330 an uptime tick at which it will expire. So such a loop might look like:
|
| /Zephyr-latest/doc/ |
| D | zephyr.doxyfile.in | 310 # qualified scopes will look different, etc.
1369 # sheet that is used by each HTML page. It can be used to fine-tune the look of
1743 # further fine tune the look of the index (see "Fine-tuning the output"). As an
1805 # the HTML output. These images will generally look nicer at scaled resolutions.
1831 # installed or if you want to formulas look prettier in the HTML output. When
2178 # RTF output is optimized for Word 97 and may not look too pretty with other RTF
2727 # class diagrams will look similar to the default class diagrams but using UML
|
| /Zephyr-latest/doc/hardware/pinctrl/ |
| D | index.rst | 230 best place to look for details.
|
| /Zephyr-latest/doc/develop/test/ |
| D | ztest.rst | 517 The output will look something like:
|
| /Zephyr-latest/cmake/modules/ |
| D | extensions.cmake | 317 # look like this:
1188 # large number of JOBS. Once it's done look at the log.txt file
2682 # NAMES <name1> [name2] ... List of file names to look for and instead of
2692 # SUFFIX fish, will look for <file>_fish.conf and use
3180 # name, or to look for values from multiple variables.
3350 # <scope> : Scope for the variable look up
3351 # <var> : Name to look up in the specific scope
|
| /Zephyr-latest/scripts/west_commands/completion/ |
| D | west-completion.fish | 427 … boards" -l board-dir -xa "(__zephyr_west_complete_directories)" -d "only look for boards in this …
|
| /Zephyr-latest/doc/services/tracing/ |
| D | index.rst | 60 CTF should look familiar to C programmers but adds stronger typing.
|
12345
