Home
last modified time | relevance | path

Searched refs:baz (Results 1 – 21 of 21) sorted by relevance

/Zephyr-Core-3.5.0/tests/kernel/device/src/
Dabstract_driver.c21 unsigned int *baz) in my_driver_A_do_that() argument
23 *baz = 1; in my_driver_A_do_that()
43 unsigned int *baz) in my_driver_B_do_that() argument
45 *baz = 2; in my_driver_B_do_that()
Dabstract_driver.h14 unsigned int *baz);
31 unsigned int *baz) in subsystem_do_that() argument
36 api->do_that(device, baz); in subsystem_do_that()
Dmain.c367 unsigned int baz = 0; in ZTEST() local
376 subsystem_do_that(dev, &baz); in ZTEST()
377 zassert_true(baz == 1, "common API do_that fail"); in ZTEST()
386 subsystem_do_that(dev, &baz); in ZTEST()
387 zassert_true(baz == 2, "common API do_that fail"); in ZTEST()
Dmmio.c18 int baz; member
104 int baz; member
Dmmio_multireg.c18 int baz; member
/Zephyr-Core-3.5.0/doc/build/snippets/
Dwriting.rst47 zephyr,baz = &snippet_foo_bar_dev;
86 For example, in a zephyr module named ``baz``, you can add this to your
94 And then any :file:`snippet.yml` files in ``baz/snippets`` will
96 the path to ``baz`` had appeared in :makevar:`SNIPPET_ROOT`.
194 baz: # settings for board "baz" go here
196 EXTRA_DTC_OVERLAY_FILE: baz.overlay
199 :file:`baz.overlay` when building for ``baz``.
/Zephyr-Core-3.5.0/doc/build/dts/
Dbindings-intro.rst86 baz-device {
87 compatible = "foo-company,baz-device", "generic-baz-device";
90 The ``baz-device`` node would get matched to a binding with a ``compatible:
91 "generic-baz-device"`` line if the build system can't find a binding with a
92 ``compatible: "foo-company,baz-device"`` line.
Dphandles.rst117 phandle-array-prop = <&foo 1 2>, <&bar 3>, <&baz 4 5>;
122 Each "group" starts with a phandle (``&foo``, ``&bar``, ``&baz``). The values
235 ``phandle-array-prop``\ 's specifier space is named ``baz``. Then we would need
236 the ``foo`` and ``bar`` nodes to have the following ``#baz-cells`` properties:
241 #baz-cells = <2>;
245 #baz-cells = <1>;
248 Without the ``#baz-cells`` property, the devicetree tooling would not be able
261 #baz-cells = <2>;
Dbindings-upstream.rst206 baz:
210 description: baz time in milliseconds
Dapi-usage.rst192 c = "bar", "baz"; /* string-array */
Dmacros.bnf114 ; pinctrl-1 = <&baz>;
/Zephyr-Core-3.5.0/scripts/dts/python-devicetree/tests/
Dtest.dts334 baz = <2>;
340 baz = <2>;
356 string-array = "foo", "bar", "baz";
435 no-enum = "baz";
/Zephyr-Core-3.5.0/doc/build/kconfig/
Dextensions.rst34 :file:`foo/bar/baz/Kconfig` and :file:`foo/bar/qaz/Kconfig`, the statement
39 source "foo/bar/baz/Kconfig"
/Zephyr-Core-3.5.0/tests/lib/devicetree/api/
Dapp.overlay48 c = "bar", "baz";
67 baz-names = "john", "doe";
156 #baz-cells = < 0x1 >;
181 #baz-cells = < 0x1 >;
583 baz = <1>;
/Zephyr-Core-3.5.0/doc/develop/west/
Dmanifest.rst701 - name: baz
713 all three projects (``foo``, ``bar``, and ``baz``) are active. Note that there
714 is no way to make project ``baz`` inactive, since it has no groups.
823 - name: baz
858 - name: baz
893 - name: baz
1189 - name: baz
1201 foo, bar, baz = manifest.get_projects(['foo', 'bar', 'baz'])
1205 baz.userdata # {'key': 'value'}
1823 path: modules/hals/baz # excluded
[all …]
/Zephyr-Core-3.5.0/doc/kernel/drivers/
Dindex.rst130 typedef void (*subsystem_do_that_t)(const struct device *dev, void *baz);
145 static inline void subsystem_do_that(const struct device *dev, void *baz)
150 api->do_that(dev, baz);
163 static void my_driver_do_that(const struct device *dev, void *baz)
/Zephyr-Core-3.5.0/tests/kernel/threads/thread_stack/src/
Dmain.c29 int baz; member
/Zephyr-Core-3.5.0/doc/services/tfm/
Dbuild.rst134 -DFOO="bar\\\;baz"
/Zephyr-Core-3.5.0/doc/build/dts/api/
Dapi.rst316 pinctrl-1 = <&baz ...>;
/Zephyr-Core-3.5.0/cmake/modules/
Dextensions.cmake3620 # dt_has_chosen(result PROPERTY "baz")
3697 # baz {};
3709 # dt_path_internal(ret "my-alias/baz") # sets ret to "/foo/bar/baz"
/Zephyr-Core-3.5.0/tests/lib/devicetree/api/src/
Dmain.c205 zassert_equal(DT_ANY_INST_HAS_PROP_STATUS_OKAY(baz), 0, ""); in ZTEST()