| /Zephyr-Core-3.5.0/tests/lib/cpp/cxx/src/ |
| D | main.cpp | 90 foo_class(int foo) : foo(foo) {} in foo_class() argument
91 int get_foo() const { return foo;} in get_foo()
93 int foo; member in foo_class
96 struct foo { struct
100 BUILD_ASSERT(sizeof(foo) == sizeof(int)); argument
102 static struct foo foos[5];
|
| /Zephyr-Core-3.5.0/doc/build/snippets/ |
| D | writing.rst | 29 name: foo
31 EXTRA_DTC_OVERLAY_FILE: foo.overlay
32 EXTRA_CONF_FILE: foo.conf
41 For example, if your snippet is named ``foo-bar``, write your devicetree
73 For example, if :makevar:`SNIPPET_ROOT` is set to ``/foo;/bar``, the build
77 - :file:`/foo/snippets/`
104 To apply ``bar`` after ``foo``:
108 cmake -Sapp -Bbuild -DSNIPPET="foo;bar" [...]
115 west build -S foo -S bar [...] app
120 For instance, if ``foo`` sets ``CONFIG_FOO=1`` and ``bar`` sets
[all …]
|
| D | using.rst | 17 To use a snippet named ``foo`` when building an application ``app``:
21 west build -S foo app
|
| D | design.rst | 36 to boards ``foo`` and ``bar`` by specifying ``/(foo|bar)/`` as a regular
|
| /Zephyr-Core-3.5.0/tests/kernel/device/src/ |
| D | abstract_driver.c | 15 static int my_driver_A_do_this(const struct device *device, int foo, int bar) in my_driver_A_do_this() argument
17 return foo + bar; in my_driver_A_do_this()
37 static int my_driver_B_do_this(const struct device *device, int foo, int bar) in my_driver_B_do_this() argument
39 return foo - bar; in my_driver_B_do_this()
|
| D | abstract_driver.h | 11 typedef int (*subsystem_do_this_t)(const struct device *device, int foo,
21 static inline int subsystem_do_this(const struct device *device, int foo, in subsystem_do_this() argument
27 return api->do_this(device, foo, bar); in subsystem_do_this()
|
| D | main.c | 365 int foo = 2; in ZTEST() local
373 ret = subsystem_do_this(dev, foo, bar); in ZTEST()
374 zassert_true(ret == (foo + bar), "common API do_this fail"); in ZTEST()
383 ret = subsystem_do_this(dev, foo, bar); in ZTEST()
384 zassert_true(ret == (foo - bar), "common API do_this fail"); in ZTEST()
|
| /Zephyr-Core-3.5.0/tests/cmake/snippets/ |
| D | Kconfig | 23 Test the `foo` snippet from the default application snippet root.
33 Test the snippet processing order (1. foo, 2. bar)
38 Test the snippet processing order (1. bar, 2. foo)
44 int "Test value set by the 'foo' snippet config overlay"
46 This option's value should be overridden by the 'foo' snippet config
50 int "Test value set by the 'foo' snippet config overlay"
52 This option's value should be overridden by the 'foo' snippet config
|
| D | app.overlay | 2 /* This node will be deleted by the `foo` snippet. */
3 deleted-by-foo {};
|
| /Zephyr-Core-3.5.0/scripts/dts/python-devicetree/tests/ |
| D | test.dts | 24 interrupt-names = "foo", "bar";
240 reg-names = "foo", "bar";
332 foo = <0>;
338 foo = <0>;
355 string = "foo";
356 string-array = "foo", "bar", "baz";
360 foo-gpios = < &{/ctrl-1} 1 >;
366 #phandle-array-foo-cells = <1>;
372 #phandle-array-foo-cells = <2>;
378 phandle-array-foo-names = "a", "missing", "b";
[all …]
|
| /Zephyr-Core-3.5.0/doc/build/kconfig/ |
| D | extensions.rst | 31 source "foo/bar/*/Kconfig"
33 If the pattern ``foo/bar/*/Kconfig`` matches the files
34 :file:`foo/bar/baz/Kconfig` and :file:`foo/bar/qaz/Kconfig`, the statement
39 source "foo/bar/baz/Kconfig"
40 source "foo/bar/qaz/Kconfig"
60 As an example, assume that :file:`foo/Kconfig` is the top-level
61 :file:`Kconfig` file, and that :file:`foo/bar/Kconfig` has the following
69 This will include the two files :file:`foo/qaz/Kconfig1` and
70 :file:`foo/bar/qaz/Kconfig2`.
|
| /Zephyr-Core-3.5.0/tests/cmake/snippets/extra_snippet_root/snippets/bar/ |
| D | bar.overlay | 3 /delete-node/ added-by-foo;
5 /* This node will be deleted by the `foo` snippet if applied. */
|
| /Zephyr-Core-3.5.0/tests/cmake/snippets/snippets/foo/ |
| D | foo.overlay | 2 /delete-node/ deleted-by-foo;
6 added-by-foo {};
|
| /Zephyr-Core-3.5.0/doc/develop/sca/ |
| D | index.rst | 36 To add ``foo`` under ``/path/to/my_tools/cmake/sca`` create the following structure:
43 └── foo/
46 To use ``foo`` as SCA tool you must then specify ``-DZEPHYR_SCA_VARIANT=foo``.
|
| /Zephyr-Core-3.5.0/doc/build/dts/ |
| D | bindings-syntax.rst | 24 This is the Vendomatic company's foo-device.
35 compatible: "manufacturer,foo-device"
55 foo-cells:
56 # "Specifier" cell names for the 'foo' domain go here; example 'foo'
192 # Describes an optional property like 'keys = "foo", "bar";'
236 default: "foo"
240 default: ["foo", "bar"] # Same as 'string-array-with-default = "foo", "bar"'
311 ``foo = "/path/to/some/node";``
315 - ``foo = <&label>, [01 02];``
343 foo:
[all …]
|
| D | bindings-intro.rst | 29 compatible = "foo-company,bar-device";
39 compatible: "foo-company,bar-device"
72 compatible = "foo-company,bar-device";
87 compatible = "foo-company,baz-device", "generic-baz-device";
92 ``compatible: "foo-company,baz-device"`` line.
109 above example binding would be named :file:`foo-company,bar-device.yaml` by
|
| D | intro-syntax-structure.rst | 31 foo = <3>;
70 Node ``a-sub-node`` has a property named ``foo``, whose value is a cell with
71 value 3. The size and type of ``foo``\ 's value are implied by the enclosing
348 - ``foo = <0xdeadbeef 1234 0>;``
378 - The ``foo`` property value above has three *cells* with values 0xdeadbeef, 1234,
399 You can write a phandle using ``&foo``, where ``foo`` is a :ref:`node label
404 foo: device@0 { };
406 sibling = <&foo 1 2>;
411 #. The ``device@0`` node's phandle, which is written here as ``&foo`` since
412 the ``device@0`` node has a node label ``foo``
[all …]
|
| D | phandles.rst | 117 phandle-array-prop = <&foo 1 2>, <&bar 3>, <&baz 4 5>;
122 Each "group" starts with a phandle (``&foo``, ``&bar``, ``&baz``). The values
218 phandle-array-prop = <&foo 1 2>, <&bar 3>;
236 the ``foo`` and ``bar`` nodes to have the following ``#baz-cells`` properties:
240 foo: node@1000 {
260 foo: node@1000 {
272 phandle-array-prop = <&foo 1 2>, <&bar 3>;
273 phandle-array-prop-2 = <&foo 4>;
317 specifier space ``foo``. For example:
333 ``*-gpios`` properties are special-cased so that e.g. ``foo-gpios`` resolves to
[all …]
|
| /Zephyr-Core-3.5.0/cmake/ |
| D | package_helper.cmake | 32 # $ cmake -DBOARD=<board> -B build -S samples/hello_world -DEXTRA_CONF_FILE=foo.conf
35 # $ cmake -DBOARD=<board> -B build -S samples/hello_world -DEXTRA_CONF_FILE=foo.conf \
41 # set(EXTRA_CONF_FILE foo.conf)
43 # the 'foo.conf' must be specified using '-DEXTRA_CONF_FILE=foo.conf'
|
| /Zephyr-Core-3.5.0/doc/develop/ |
| D | env_vars.rst | 15 To set the environment variable ``MY_VARIABLE`` to ``foo`` for the
24 export MY_VARIABLE=foo
30 set MY_VARIABLE=foo
47 Add the ``export MY_VARIABLE=foo`` line to your shell's startup script in
59 new ``cmd.exe`` windows will have ``MY_VARIABLE`` set to ``foo``.
63 setx MY_VARIABLE foo
96 export MY_VARIABLE=foo
107 Add the line ``set MY_VARIABLE=foo`` to the file
|
| /Zephyr-Core-3.5.0/doc/kernel/services/other/ |
| D | fatal.rst | 59 __ASSERT(foo == 0xF0CACC1A, "Invalid value of foo, got 0x%x", foo);
61 If at runtime ``foo`` had some unexpected value, the error produced may
66 ASSERTION FAIL [foo == 0xF0CACC1A] @ ZEPHYR_BASE/tests/kernel/fatal/src/main.c:367
67 Invalid value of foo, got 0xdeadbeef
94 x = foo();
95 __ASSERT(x != 0, "foo() returned zero!");
102 __ASSERT_EVAL ((void) foo(),
103 int x = foo(),
105 "foo() returned zero!");
|
| /Zephyr-Core-3.5.0/samples/subsys/shell/shell_module/src/ |
| D | test_module.c | 11 void foo(void) in foo() function
|
| /Zephyr-Core-3.5.0/doc/develop/west/ |
| D | manifest.rst | 601 contain these characters elsewhere in their names. For example, ``foo-bar`` and
602 ``foo+bar`` are valid groups, but ``-foobar`` and ``+foobar`` are not.
694 - name: foo
713 all three projects (``foo``, ``bar``, and ``baz``) are active. Note that there
725 - name: foo
744 Since ``groupA`` is disabled, project ``foo`` is inactive. Project ``bar`` is
756 - name: foo
775 Both ``foo`` and ``bar`` are inactive, because all of their groups are
787 - name: foo
806 Project ``foo`` is inactive because ``groupA`` has been disabled by the
[all …]
|
| /Zephyr-Core-3.5.0/cmake/modules/ |
| D | soc.cmake | 55 …- if your SoC family directory is '/foo/bar/soc/<ARCH>/my_soc_family', then add '/foo/bar' to SOC_…
|
| D | boards.cmake | 36 # - BOARD: Board name, including any optional revision field, for example: `foo` or `foo@1.0.0`
95 …- if your board directory is '/foo/bar/boards/<ARCH>/my_board' then add '/foo/bar' to BOARD_ROOT, …
|
