Home
last modified time | relevance | path

Searched refs:properties (Results 1 – 25 of 194) sorted by relevance

12345678

/Zephyr-latest/samples/bluetooth/hap_ha/src/
Dhas_server.c44 .properties = BT_HAS_PROP_AVAILABLE | BT_HAS_PROP_WRITABLE, in has_server_preset_init()
50 .properties = BT_HAS_PROP_AVAILABLE | BT_HAS_PROP_WRITABLE, in has_server_preset_init()
56 .properties = BT_HAS_PROP_AVAILABLE | BT_HAS_PROP_WRITABLE, in has_server_preset_init()
62 .properties = BT_HAS_PROP_AVAILABLE | BT_HAS_PROP_WRITABLE, in has_server_preset_init()
/Zephyr-latest/cmake/linker/
Dlinker_flags_template.cmake5 # Base properties.
6 # Basic linker properties which should always be applied for a Zephyr build.
9 # Base properties when C++ support is enabled.
10 # Basic linker properties which should always be applied for a Zephyr build
14 # Base properties when building Zephyr for an embedded target (baremetal).
Dlinker_libraries_native.cmake6 # No reason for loading linker libraries properties in this case, however we do
15 # Although library properties are empty per default, then we still define link
/Zephyr-latest/doc/build/dts/
Dphandles.rst40 :ref:`dt-bindings-properties` in the devicetree bindings documentation.
68 These properties have type ``phandle``.
76 properties like ``pinctrl-0``, ``pinctrl-1`` etc. may contain multiple
87 These properties have type ``phandles``.
98 These properties have type ``phandle-array``.
102 phandle-array properties
105 These properties are commonly used to specify a resource that is owned by
111 Usually, properties with this type are written like ``phandle-array-prop`` in
135 document more rules about how to use phandle-array properties in practice.
140 Perhaps the most common use case for phandle-array properties is specifying one argument
[all …]
Dapi-usage.rst63 properties.
128 - :ref:`simple-properties`
129 - :ref:`reg-properties`
130 - :ref:`interrupts-properties`
131 - :ref:`phandle-properties`
135 Checking properties and values
146 .. _simple-properties:
148 Simple properties
152 numeric array, and string array properties.
166 That is, properties also need special characters converted to underscores.
[all …]
Dbindings-syntax.rst37 properties:
38 # Requirements for and descriptions of the properties that this
67 datasheets or example nodes or properties as well.
114 .. _dt-bindings-properties:
119 The ``properties:`` key describes properties that nodes which match the binding
127 properties:
141 The build system uses bindings to generate C macros for devicetree properties
144 build system only generates macros for properties listed in the ``properties:``
149 standard properties, like :ref:`reg <dt-important-props>`, whose meaning is
156 Property entries in ``properties:`` are written in this syntax:
[all …]
Dzephyr-user-node.rst8 you can put essentially arbitrary properties inside it and retrieve their
10 when only a few simple properties are needed.
69 You can convert the phandles in the ``handle`` and ``handles`` properties to
Dbindings-upstream.rst23 try to replicate its properties when writing a Zephyr binding, and you must
108 <dt-important-props>` properties.
119 properties, and compatibles should not include them unless they refer to an
150 create a consistent configuration, then those properties should be made
159 is likely to be incorrect. For such properties it's better to make the
170 (as long as they are independent from other properties)
176 properties:
196 properties:
240 but not required to add the ``zephyr,`` prefix to properties defined in the
/Zephyr-latest/tests/drivers/charger/sbs_charger/boards/
Dqemu_cortex_a53.overlay17 * qemu_cortex_a53 SoC requires a 64 bit child addresses (reg properties)
18 * See its /soc #address-cells & #size-cells properties.
/Zephyr-latest/tests/drivers/fuel_gauge/sbs_gauge/boards/
Dqemu_cortex_a53.overlay17 * qemu_cortex_a53 SoC requires a 64 bit child addresses (reg properties)
18 * See its /soc #address-cells & #size-cells properties.
/Zephyr-latest/include/zephyr/bluetooth/audio/
Dhas.h127 enum bt_has_properties properties; member
354 enum bt_has_properties properties; member
446 typedef uint8_t (*bt_has_preset_func_t)(uint8_t index, enum bt_has_properties properties,
/Zephyr-latest/tests/bsim/bluetooth/audio/src/
Dhas_test.c91 preset_param.properties = test_preset_properties; in test_common()
102 preset_param.properties = test_preset_properties; in test_common()
136 preset_param.properties = test_preset_properties; in test_offline_behavior()
/Zephyr-latest/doc/hardware/peripherals/
Dbbram.rst6 The BBRAM APIs allow interfacing with the unique properties of this memory region. The following
7 common types of BBRAM properties are easily accessed via this API:
Dregulators.rst11 The ``*-supply`` devicetree properties are used to identify the regulator(s)
18 infrastructure is not justified, and ``*-gpios`` devicetree properties should be
Dcharger.rst17 host controller by setting the relevant properties, and can be adjusted at runtime to respond to
34 Chargers typically support multiple properties, such as temperature readings of the battery-pack
/Zephyr-latest/subsys/bluetooth/audio/
Dhas_internal.h82 uint8_t properties; member
95 uint8_t properties; member
Dhas.c555 enum bt_has_properties properties; member
619 static struct has_preset *preset_alloc(uint8_t index, enum bt_has_properties properties, in preset_alloc() argument
632 preset->properties = properties; in preset_alloc()
835 preset->index, preset->properties, preset->name, is_last); in bt_has_cp_read_preset_rsp()
842 rsp->properties = preset->properties; in bt_has_cp_read_preset_rsp()
861 uint8_t properties, const char *name, uint8_t is_last) in bt_has_cp_generic_update() argument
870 client, prev_index, index, properties, name, is_last); in bt_has_cp_generic_update()
877 generic_update->properties = properties; in bt_has_cp_generic_update()
1053 .properties = BT_HAS_PROP_NONE, in preset_list_changed_generic_update_tail()
1066 last.index, last.properties, last.name, false); in preset_list_changed_generic_update_tail()
[all …]
/Zephyr-latest/cmake/modules/
DFindDeprecated.cmake110 "linker flags as properties instead. "
112 "known linker properties."
126 "linker flags as properties instead. "
128 "known linker properties."
142 "linker flags as properties instead. "
144 "known linker properties."
/Zephyr-latest/share/sysbuild/image_configurations/
DALL_image_default.cmake5 # This sysbuild CMake file sets the sysbuild controlled settings as properties
/Zephyr-latest/doc/hardware/peripherals/sensor/
Dattributes.rst7 mutable properties of a sensor and its channels.
13 inspecting and manipulating such device properties.
/Zephyr-latest/cmake/bintools/host-gnu/
Dtarget.cmake15 # Include bin tool properties
/Zephyr-latest/doc/build/dts/api/
Dapi.rst52 The following general-purpose macros can be used to access node properties.
125 properties, etc. Some macros used for special purposes (such as
143 - a node directly depends on any nodes its properties refer to by phandle
242 controllers/transceivers, and properties related to them.
250 properties related to them.
258 controllers or channels, and properties related to them.
279 and properties related to them.
297 and properties related to them.
306 These are used to access pin control properties by name or index.
308 Devicetree nodes may have properties which specify pin control (sometimes known
[all …]
/Zephyr-latest/scripts/ci/es_upload/
DREADME.md49 * `--exclude` removes excess testsuite properties not needed to store them
52 * `--transform` applies regexp group parsing rules to string properties extracting
53 derived object properties.
57 inheriting all other testsuite properties, whereas the children object's properties
125 with 3 additional data properties extracted by regular expressions.
/Zephyr-latest/cmake/compiler/armclang/
Dcompiler_flags.cmake1 # First step is to inherit all properties from gcc, as clang is compatible with most flags.
/Zephyr-latest/subsys/bluetooth/audio/shell/
Dhas.c45 .properties = shell_strtoul(argv[2], 16, &err), in cmd_preset_reg()
162 static uint8_t print_list_entry(uint8_t index, enum bt_has_properties properties, in print_list_entry() argument
168 properties, name); in print_list_entry()

12345678