Home
last modified time | relevance | path

Searched refs:above (Results 51 – 75 of 381) sorted by relevance

12345678910>>...16

/Zephyr-latest/samples/drivers/display/
DREADME.rst15 at any point or the order of the corners is not as described above then the LCD
/Zephyr-latest/doc/_doxygen/
Ddoxygen-awesome-sidebar-only-darkmode-toggle.css18 The above copyright notice and this permission notice shall be included in all
/Zephyr-latest/samples/drivers/led/is31fl3733/
DREADME.rst18 API, and repeat the above tests
/Zephyr-latest/samples/drivers/led/pwm/boards/
Dmec15xxevb_assy6853.overlay18 * Due to all the above we use 50 ms for DT PWM period.
/Zephyr-latest/doc/kernel/object_cores/
Dindex.rst123 code builds on the example above and initializes the object core.
142 above and prints the addresses of all the objects of that new object type.
174 The following code builds on the examples above and shows how an object
/Zephyr-latest/doc/kernel/services/data_passing/
Dfifos.rst85 The following code has the same effect as the code segment above.
96 The following code builds on the example above, and uses the FIFO
134 The following code builds on the example above, and uses the FIFO
/Zephyr-latest/doc/services/device_mgmt/
Dsmp_protocol.rst150 The payload for above groups, except for user groups (``64`` and above) is
151 always CBOR encoded. The group ``64``, and above can define their own scheme
/Zephyr-latest/cmake/modules/
Dconfiguration_files.cmake20 # If any of the above variables are already set when this CMake module is
23 # Variables set by this module and not mentioned above are considered internal
Darch_v2.cmake23 # Variables set by this module and not mentioned above are considered internal
Darch_v1.cmake27 # Variables set by this module and not mentioned above are considered internal
/Zephyr-latest/doc/safety/
Dsafety_requirements.rst67 the steps above.
120 * Other formats are accepted as long as the characteristics of a requirement from above are met.
/Zephyr-latest/subsys/mgmt/osdp/
DKconfig.cp20 string should exactly match the number of connected PDs specified above
/Zephyr-latest/samples/drivers/espi/
DREADME.rst51 note:: The values shown above might differ.
/Zephyr-latest/samples/sensor/qdec/
DREADME.rst72 in the above example. This depends on the mechanical encoder being used and
/Zephyr-latest/samples/subsys/fs/fs_sample/boards/
Dnrf52840dk_nrf52840_ram_disk_region.overlay52 * region by label we have defined it above.
/Zephyr-latest/boards/shields/nxp_btb44_ov5640/doc/
Dindex.rst115 as above, such as i.MX RT1160 and RT1170 EVK boards.
/Zephyr-latest/samples/drivers/can/counter/
DREADME.rst64 .. note:: The values shown above might differ.
/Zephyr-latest/doc/build/kconfig/
Dextensions.rst24 The statement above is equivalent to:
71 above is equivalent to the following two ``source`` statements:
/Zephyr-latest/samples/net/telnet/
DREADME.rst89 board documentation noted above.
117 The above result depends on your local network.
/Zephyr-latest/doc/kernel/services/synchronization/
Dmutexes.rst111 The following code has the same effect as the code segment above.
122 The following code builds on the example above, and waits indefinitely
145 The following code builds on the example above,
/Zephyr-latest/doc/build/snippets/
Dwriting.rst130 ``CONFIG_FOO=2`` in the above example, the resulting final configuration will
221 The above example uses :file:`bar.overlay` when building for board ``bar``, and
244 The above example uses devicetree overlay :file:`my_vendor.overlay` when
/Zephyr-latest/samples/boards/nordic/nrfx_prs/boards/
Dnrf9160dk_nrf9160.overlay83 * board configuration it uses the same pin numbers that are above assigned
/Zephyr-latest/doc/kernel/iterable_sections/
Dindex.rst63 above would visit ``d1``, ``d2`` and ``d3`` in that order, regardless of how
/Zephyr-latest/boards/intel/common/
Dnet_boot.rst31 ``zephyr.efi`` is a Zephyr EFI binary created above.
/Zephyr-latest/boards/kincony/kincony_kc868_a32/doc/
Dindex.rst38 It is recommended running the command above after :file:`west update`.

12345678910>>...16