Home
last modified time | relevance | path

Searched full:foo (Results 1 – 25 of 198) sorted by relevance

12345678

/Zephyr-latest/doc/build/kconfig/
Dextensions.rst17 config FOO
18 bool "FOO"
21 configdefault FOO
28 config FOO
29 bool "Foo"
39 configdefault FOO
43 configdefault FOO
54 The recommended syntax for referencing environment variables is ``$(FOO)``
55 rather than ``$FOO``. This uses the new `Kconfig preprocessor
57 The ``$FOO`` syntax for expanding environment variables is only supported for
[all …]
Dtips.rst27 If a symbol has a prompt (e.g. ``bool "Enable foo"``), then the user can change
251 bool "FOO SoC"
326 bool "external SPI ADC foo driver"
357 config FOO
358 bool "Support foo"
360 In this case, ``FOO`` will end up with this definition:
364 config FOO
365 bool "Support foo"
369 ``FOO`` in :file:`Kconfig.other`, because the ``DEP`` dependency has already
386 config FOO
[all …]
/Zephyr-latest/tests/cmake/snippets/
DKconfig21 bool "Test Type: Foo"
23 Test the `foo` snippet from the default application snippet root.
31 bool "Test Type: Foo-Bar"
33 Test the snippet processing order (1. foo, 2. bar)
36 bool "Test Type: Bar-Foo"
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
Dtestcase.yaml17 # Test the `foo` snippet from the default application snippet root
18 buildsystem.snippets.foo:
19 extra_args: SNIPPET="foo"
27 # Test the snippet processing order (1. foo, 2. bar)
29 extra_args: SNIPPET="foo;bar"
32 # Test the snippet processing order (1. bar, 2. foo)
34 extra_args: SNIPPET="bar;foo"
Dapp.overlay2 /* This node will be deleted by the `foo` snippet. */
3 deleted-by-foo {};
/Zephyr-latest/tests/cmake/snippets/src/
Dmain.c14 /* Test config values set by the `foo` snippet */
36 * When `foo` snippet is applied, test that the foo and common in ZTEST()
37 * config values correspond to the values set by the `foo` in ZTEST()
54 * When `foo` and `bar` snippets are applied, with `bar` in ZTEST()
55 * specified after `foo`, test that the common config value in ZTEST()
63 * When `foo` and `bar` snippets are applied, with `foo` in ZTEST()
65 * corresponds to the value set by the `foo` snippet. in ZTEST()
79 * When no snippet is applied, test that both `deleted-by-foo` in ZTEST()
81 * added by the `foo` and `bar` snippets exist. in ZTEST()
89 * When `foo` snippet is applied, test that `deleted-by-foo` is in ZTEST()
[all …]
/Zephyr-latest/doc/build/snippets/
Dwriting.rst29 name: foo
31 EXTRA_DTC_OVERLAY_FILE: foo.overlay
32 EXTRA_CONF_FILE: foo.conf
38 name: foo
50 For example, if your snippet is named ``foo-bar``, write your devicetree
82 For example, if :makevar:`SNIPPET_ROOT` is set to ``/foo;/bar``, the build
86 - :file:`/foo/snippets/`
113 To apply ``bar`` after ``foo``:
117 cmake -Sapp -Bbuild -DSNIPPET="foo;bar" [...]
124 west build -S foo -S bar [...] app
[all …]
/Zephyr-latest/scripts/dts/python-devicetree/tests/test-bindings/
Dprops.yaml26 const: "foo"
30 const: ['foo', 'bar', 'baz']
41 phandle-array-foo-names:
44 # There's some slight special-casing for GPIOs in that 'foo-gpios = ...'
45 # gets resolved to #gpio-cells rather than #foo-gpio-cells, so test that
47 foo-gpios:
Dfoo-bus.yaml3 description: Foo bus controller
5 compatible: "foo-bus"
7 bus: "foo"
Ddevice-on-foo-bus.yaml3 description: Device on foo bus
7 on-bus: "foo"
Dorder-1.yaml7 include: ["foo-required.yaml", "foo-optional.yaml"]
Dorder-2.yaml7 include: ["foo-optional.yaml", "foo-required.yaml"]
/Zephyr-latest/scripts/tests/twister_blackbox/test_data/tests/params/dummy/src/
Dmain.c23 zassert_not_null("foo", "\"foo\" was NULL"); in ZTEST()
32 zassert_not_null("foo", "\"foo\" was NULL"); in ZTEST()
41 zassert_not_null("foo", "\"foo\" was NULL"); in ZTEST()
/Zephyr-latest/scripts/dts/python-devicetree/tests/
Dtest_dtlib.py373 l1: l2: l1: foo {
392 &{/foo} {
396 &{/foo/bar} {
413 l1: l2: l3: foo {
446 &{foo} {
449 ":6 (column 1): parse error: node path 'foo' does not start with '/'")
457 &{/foo} {
460 ":6 (column 1): parse error: component 'foo' in path '/foo' does not exist")
570 unit-addr-non-numeric@foo-bar {
582 unit-addr-non-numeric@foo-bar {
[all …]
Dtest.dts24 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-latest/soc/nordic/common/
Dsoc_nrf_common.h19 * @brief Get a PSEL value out of a foo-gpios or foo-pin devicetree property
21 * Many Nordic bindings have 'foo-pin' properties to specify a pin
22 * configuration as a PSEL value directly instead of using a 'foo-gpios'
25 * It would be better to use 'foo-gpios' properties instead. This type
28 * To allow for a smooth migration from 'foo-pin' to 'foo-gpios', this
30 * using whichever one of 'foo-gpios' or 'foo-pin' is in the DTS.
35 * - NRF_DT_GPIOS_TO_PSEL() if you only have a 'foo-gpios'
38 * @param psel_prop lowercase-and-underscores old-style 'foo-pin' property
39 * @param gpios_prop new-style 'foo-gpios' property
64 * @param gpios_prop lowercase-and-underscores foo-gpios style property
[all …]
/Zephyr-latest/tests/cmake/snippets/snippets/foo/
Dsnippet.yml1 name: foo
3 EXTRA_CONF_FILE: foo.conf
4 EXTRA_DTC_OVERLAY_FILE: foo.overlay
Dfoo.overlay2 /delete-node/ deleted-by-foo;
6 added-by-foo {};
/Zephyr-latest/scripts/tests/twister_blackbox/test_data/tests/dummy/agnostic/group2/src/
Dmain.c25 zassert_not_null("foo", "\"foo\" was NULL"); in ZTEST()
35 zassert_not_null("foo", "\"foo\" was NULL"); in ZTEST()
/Zephyr-latest/scripts/tests/twister_blackbox/test_data/tests/dummy/agnostic_cpp/group2/src/
Dmain.cpp28 zassert_not_null("foo", "\"foo\" was NULL"); in ZTEST()
38 zassert_not_null("foo", "\"foo\" was NULL"); in ZTEST()
/Zephyr-latest/tests/kernel/device/src/
Dabstract_driver.h15 typedef int (*abstract_do_this_t)(const struct device *dev, int foo, int bar);
23 __syscall int abstract_do_this(const struct device *dev, int foo, int bar);
25 static inline int z_impl_abstract_do_this(const struct device *dev, int foo, int bar) in z_impl_abstract_do_this() argument
29 return DEVICE_API_GET(abstract, dev)->do_this(dev, foo, bar); in z_impl_abstract_do_this()
Dabstract_driver.c15 static int my_driver_A_do_this(const struct device *dev, int foo, int bar) in my_driver_A_do_this() argument
17 return foo + bar; in my_driver_A_do_this()
36 static int my_driver_B_do_this(const struct device *dev, int foo, int bar) in my_driver_B_do_this() argument
38 return foo - bar; in my_driver_B_do_this()
/Zephyr-latest/doc/build/dts/
Dbindings-syntax.rst24 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 …]
/Zephyr-latest/doc/kernel/services/other/
Dfatal.rst59 __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!");
141 BUILD_ASSERT(FOO == 2000, "Invalid value of FOO");
[all …]
/Zephyr-latest/tests/cmake/snippets/extra_snippet_root/snippets/bar/
Dbar.overlay3 /delete-node/ added-by-foo;
5 /* This node will be deleted by the `foo` snippet if applied. */

12345678