| /Zephyr-latest/subsys/net/conn_mgr/ |
| D | conn_mgr_connectivity.c | 19 struct conn_mgr_conn_binding *binding; in conn_mgr_if_connect() local
25 binding = conn_mgr_if_get_binding(iface); in conn_mgr_if_connect()
26 if (!binding) { in conn_mgr_if_connect()
30 api = binding->impl->api; in conn_mgr_if_connect()
35 conn_mgr_binding_lock(binding); in conn_mgr_if_connect()
44 status = api->connect(binding); in conn_mgr_if_connect()
47 conn_mgr_binding_unlock(binding); in conn_mgr_if_connect()
56 struct conn_mgr_conn_binding *binding; in conn_mgr_if_disconnect() local
62 binding = conn_mgr_if_get_binding(iface); in conn_mgr_if_disconnect()
63 if (!binding) { in conn_mgr_if_disconnect()
[all …]
|
| /Zephyr-latest/tests/net/conn_mgr_conn/src/ |
| D | test_conn_impl.c | 91 static int test_connect(struct conn_mgr_conn_binding *const binding, bool a) in test_connect() argument
93 struct test_conn_data *data = binding->ctx; in test_connect()
104 simulate_fatal_error(binding->iface, data->fatal_error); in test_connect()
109 simulate_timeout(binding->iface); in test_connect()
118 net_if_dormant_off(binding->iface); in test_connect()
122 static int test_disconnect(struct conn_mgr_conn_binding *const binding, bool a) in test_disconnect() argument
124 struct test_conn_data *data = binding->ctx; in test_disconnect()
135 net_if_dormant_on(binding->iface); in test_disconnect()
150 int test_set_opt_a(struct conn_mgr_conn_binding *const binding, int optname, in test_set_opt_a() argument
153 struct test_conn_data *data = binding->ctx; in test_set_opt_a()
[all …]
|
| /Zephyr-latest/include/zephyr/net/ |
| D | conn_mgr_connectivity_impl.h | 53 int (*connect)(struct conn_mgr_conn_binding *const binding);
64 int (*disconnect)(struct conn_mgr_conn_binding *const binding);
76 void (*init)(struct conn_mgr_conn_binding *const binding);
96 int (*set_opt)(struct conn_mgr_conn_binding *const binding,
114 int (*get_opt)(struct conn_mgr_conn_binding *const binding,
157 * @brief Connectivity Manager network interface binding structure
201 /* Internal-use mutex for protecting access to the binding and API functions. */
235 * @brief Retrieves the conn_mgr binding struct for a provided iface if it exists.
241 * @param iface - bound network interface to obtain the binding struct for.
242 * @return struct conn_mgr_conn_binding* Pointer to the retrieved binding struct if it exists,
[all …]
|
| /Zephyr-latest/scripts/release/ |
| D | list_devicetree_bindings_changes.py | 26 from devicetree.edtlib import Binding, bindings_from_paths, load_vendor_prefixes_txt
42 binding between the start and end commits. See subclasses
46 Compat2Binding = Dict[Compat, Binding]
47 Binding2Changes = Dict[Binding, List[BindingChange]]
153 for compat, binding in compat2binding.items():
154 ret[get_vnd(binding.compatible)][compat] = binding
165 for binding, changes in binding2changes.items():
166 ret[get_vnd(binding.compatible)][binding] = changes
183 for compat, binding in compat2binding_end.items():
193 ret[binding] = binding_changes
[all …]
|
| /Zephyr-latest/dts/bindings/test/ |
| D | vnd,great-grandchild-bindings.yaml | 5 Test binding for 3 levels of "child-binding".
8 "child-binding:" in a YAML file. This file is used to test that the
15 child-binding:
18 child-binding:
21 child-binding:
|
| D | vnd,video-multi-port.yaml | 8 child-binding:
9 child-binding:
10 child-binding:
|
| /Zephyr-latest/dts/bindings/gpio/ |
| D | sparkfun,micromod-gpio.yaml | 13 by this binding.
14 * Reset, Boot pins and SWD pins not exposed by this binding.
16 RX and TX pins. Neither of them are exposed by this binding.
18 this binding.
19 * 2 SPI buses not exposed by this binding. Only SPI CS control pin
20 is exposed by this binding.
21 * Audio line not exposed by this binding.
26 This binding provides a nexus mapping for the analog, digital and
|
| /Zephyr-latest/scripts/dts/python-devicetree/tests/ |
| D | test_edtlib.py | 54 …f"compatible 'enums' in binding '{enums_hpath}' has non-tokenizable enum for property 'string-enum…
55 …f"compatible 'enums' in binding '{enums_hpath}' has enum for property 'tokenizable-lower-enum' tha…
234 "<Node /parent in 'test.dts', no binding>"
237 "<Node /parent/child-2 in 'test.dts', no binding>"
240 …: <Node /parent/child-1 in 'test.dts', no binding>, 'child-2': <Node /parent/child-2 in 'test.dts'…
263 binding_include = edt.get_node("/binding-include")
265 assert binding_include.description == "Parent binding"
272 verify_props(edt.get_node("/binding-include/child"),
285 edtlib.Binding("test-bindings-include/allow-and-blocklist.yaml", fname2path)
291 edtlib.Binding("test-bindings-include/allow-and-blocklist-child.yaml", fname2path)
[all …]
|
| /Zephyr-latest/scripts/dts/python-devicetree/tests/test-bindings-include/ |
| D | filter-child-bindings.yaml | 1 description: Test binding for filtering 'child-binding' properties
6 child-binding:
8 child-binding:
|
| D | allow-and-blocklist-child.yaml | 5 child binding. This binding should cause an error.
9 child-binding:
|
| D | simple_filter_allowlist.yaml | 4 # up to the grandchild-binding level.
9 child-binding:
11 child-binding:
|
| /Zephyr-latest/doc/_scripts/ |
| D | gen_devicetree_rest.py | 102 for binding in bindings:
103 vnd = compatible_vnd(binding.compatible)
105 generic_bindings.append(binding)
107 unsorted[vnd].append(binding)
109 unknown_vendor_bindings.append(binding)
115 def binding_key(binding): argument
116 return binding.compatible
184 help='additional DTS folders containing binding files')
202 # Get a list of edtlib.Binding objects from searching 'dts_roots'.
224 bindings = [binding for binding in bindings if
[all …]
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-intro.rst | 1 .. _dt-binding-compat:
14 each node in the devicetree to a binding file. When this succeeds, the build
15 system uses the information in the binding file both when validating the node's
33 Here is a minimal binding file which matches the node:
37 # A YAML binding matching the node
46 The build system matches the ``bar-device`` node to its YAML binding because
47 the node's ``compatible`` property matches the binding's ``compatible:`` line.
56 For example, the build system would use the above binding to check that the
67 binding:
90 The ``baz-device`` node would get matched to a binding with a ``compatible:
[all …]
|
| D | bindings-syntax.rst | 22 # A high level description of the device the binding applies to:
34 # Used to match nodes to this binding:
39 # binding's nodes need to satisfy go here.
41 child-binding:
42 # You can constrain the children of the nodes matching this binding
74 This key is used to match nodes to this binding as described in
75 :ref:`dt-binding-compat`. It should look like this in a binding file:
82 This devicetree node would match the above binding:
90 Assuming no binding has ``compatible: "manufacturer,device-v2"``, it would also
100 binding is used. The :ref:`on-bus: <dt-bindings-on-bus>` key can be used to
[all …]
|
| D | bindings-upstream.rst | 22 is an existing binding for your device in an authoritative location, you should
23 try to replicate its properties when writing a Zephyr binding, and you must
28 - There is an existing binding in the mainline Linux kernel. See
32 - Your hardware vendor provides an official binding outside of the Linux
55 - For example, a binding for compatible ``vnd,foo`` must be named ``vnd,foo.yaml``.
56 - If the binding is bus-specific, you can append the bus to the file name;
57 for example, if the binding YAML has ``on-bus: bar``, you may name the file
64 submitting the binding.
101 this rule is if you are replicating a well-established binding from somewhere
113 If your binding describes hardware with a well known vendor from the list in
[all …]
|
| /Zephyr-latest/scripts/dts/python-devicetree/tests/test-bindings/ |
| D | child-binding-with-compat.yaml | 3 description: child-binding with separate compatible than the parent
5 compatible: "top-binding-with-compat"
7 child-binding:
15 child-binding:
|
| D | child-binding.yaml | 3 description: child-binding test
5 compatible: "top-binding"
7 child-binding:
16 child-binding:
|
| D | parent.yaml | 3 description: Parent binding
5 compatible: "binding-include-test"
15 child-binding:
16 # child.yaml included at child-binding level
|
| /Zephyr-latest/doc/hardware/emulator/ |
| D | index.rst | 38 * DT binding: :dtcompatible:`zephyr,adc-emul`
43 * DT binding: :dtcompatible:`zephyr,dma-emul`
48 * DT binding: :dtcompatible:`zephyr,emu-eeprom`
55 * DT binding: :dtcompatible:`zephyr,sim-eeprom`
68 * DT binding: :dtcompatible:`zephyr,sim-flash`
75 * DT binding: :dtcompatible:`zephyr,gpio-emul`
80 * DT binding: :dtcompatible:`zephyr,i2c-emul-controller`
85 * DT binding: :dtcompatible:`zephyr,rtc-emul`
90 * DT binding: :dtcompatible:`zephyr,spi-emul-controller`
95 * DT binding: :dtcompatible:`zephyr,mspi-emul-controller`
[all …]
|
| /Zephyr-latest/dts/bindings/i2c/ |
| D | ti,tca9544a.yaml | 1 # Binding for TI TCA9544A, compatible with NXP PCA9544A
3 description: Texas Instruments TCA9544A binding
9 child-binding:
|
| D | ti,tca9546a.yaml | 1 # Binding for TI TCA9546A, compatible with NXP PCA9546A
3 description: Texas Instruments TCA9546A binding
9 child-binding:
|
| D | ti,tca9548a.yaml | 1 # Binding for TI TCA9548A, compatible with NXP PCA9548A
3 description: Texas Instruments TCA9548A binding
9 child-binding:
|
| /Zephyr-latest/scripts/dts/python-devicetree/src/devicetree/ |
| D | edtlib.py | 17 but a binding can also come from a 'child-binding:' key in the binding for the
23 The top-level entry points for the library are the EDT and Binding classes.
38 # create several EDT objects with independent binding paths and flags. If you
98 class Binding: class
100 Represents a parsed binding.
102 These attributes are available on Binding objects:
105 The absolute path to the file defining the binding.
108 The free-form description of the binding, or None.
111 The compatible string the binding matches.
113 This may be None. For example, it's None when the Binding is inferred
[all …]
|
| /Zephyr-latest/doc/services/ipc/ipc_service/backends/ |
| D | ipc_service_icbmsg.rst | 170 * **Binding message** - Message exchanged during endpoint binding process (described below).
230 The endpoint binding procedure must be finished before sending this control message.
268 The ``MSG_BOUND`` control message is similar to the ``MSG_DATA`` except the blocks carry binding in…
269 See the next section for details on the binding procedure.
289 See the next section for details on the binding procedure.
298 After ICBMsg initialization, you are ready for the endpoint binding procedure.
300 Endpoint Binding
305 The binding process is not symmetrical.
308 * **Initiator** - It assigns endpoint addresses and sends binding messages.
309 * **Follower** - It waits for a binding message.
[all …]
|
| /Zephyr-latest/dts/bindings/video/ |
| D | nxp,mipi-csi2rx.yaml | 13 child-binding:
14 child-binding:
15 child-binding:
|
