Lines Matching full:like
40 CMake prints the input and output file locations like this:
125 on user input like in a shell application. In this case you can get the
134 You can then use ``uart_dev`` with :ref:`uart_api` API functions like
139 that the node has ``status = "okay"``, like this:
162 successfully, the last thing to check is if the device is ready, like this:
203 Make note of the path to the node you want to find, like ``/flash@0``. Search
204 for the node's output in the file, which starts with something like this if the
230 like ``\${ZEPHYR_<module>_MODULE_DIR}/<path-to>/dts.overlay``
273 finds in the configuration phase, like this:
350 child device on an existing bus node, do something like this:
432 device-specific configuration and data structures and API functions, like this:
513 Notice the use of APIs like :c:macro:`DT_INST_PROP` and
536 blocks to implement Zephyr driver callbacks. Cases like this should use
542 labels like ``mydevice0``, ``mydevice1``, etc. appropriately for the IP blocks
543 your driver supports. The resulting devicetree usually looks something like
572 * Define your instantiation macro; "idx" is a number like 0 for mydevice0
590 Notice the use of APIs like :c:macro:`DT_PROP` and
622 file like :zephyr_file:`dts/bindings/spi/spi-device.yaml` which provides
624 use of APIs like :c:macro:`DT_BUS` to obtain a node identifier for the bus