Searched full:specification (Results 1 – 25 of 459) sorted by relevance
12345678910>>...19
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | models.rst | 9 The Bluetooth Mesh specification defines foundation models that can be
36 Model specification models
39 In addition to the foundation models defined in the Bluetooth Mesh specification, the Bluetooth Mesh
40 Model Specification defines several models, some of which are implemented in Zephyr:
|
| D | brg_cfg_srv.rst | 7 specification. It is an optional model, enabled with the
11 The Bridge Configuration Server model was introduced in the Bluetooth Mesh Protocol Specification
|
| D | lcd_cli.rst | 7 specification. The model is optional, and is enabled through the
10 The Large Composition Data Client model was introduced in the Bluetooth Mesh Protocol Specification
|
| D | health_srv.rst | 25 specification, and the full list of specification defined faults are available
60 Fault values defined by the Bluetooth Mesh specification.
|
| D | od_srv.rst | 7 specification. It is enabled with the :kconfig:option:`CONFIG_BT_MESH_OD_PRIV_PROXY_SRV` option.
9 The On-Demand Private Proxy Server model was introduced in the Bluetooth Mesh Protocol Specification
|
| D | op_agg_cli.rst | 7 specification. It is an optional model, enabled with the :kconfig:option:`CONFIG_BT_MESH_OP_AGG_CLI`
10 The Opcodes Aggregator Client model is introduced in the Bluetooth Mesh Protocol Specification
|
| D | op_agg_srv.rst | 7 mesh specification. It is an optional model, enabled with the
11 Specification version 1.1, and is used to support the functionality of processing
|
| D | sar_cfg_srv.rst | 7 specification. It is an optional model, enabled with the
10 The SAR Configuration Server model is introduced in the Bluetooth Mesh Protocol Specification
|
| D | priv_beacon_cli.rst | 7 mesh specification. It is enabled with the
11 Specification version 1.1, and provides functionality for configuring the
|
| D | srpl_cli.rst | 7 mesh specification. The model is optional, and is enabled through the
11 Specification version 1.1, and supports the functionality of removing addresses from the
|
| D | srpl_srv.rst | 7 mesh specification. The model is enabled if the node has the :ref:`bluetooth_mesh_od_srv` enabled.
10 Specification version 1.1, and manages the Solicitation Replay Protection List (SRPL) saved on the
|
| D | od_cli.rst | 7 specification. The model is optional, and is enabled with the
10 The On-Demand Private Proxy Client model was introduced in the Bluetooth Mesh Protocol Specification
|
| /Zephyr-latest/samples/boards/nordic/clock_control/ |
| D | Kconfig | 5 int "Frequency specification to request from clock in Hz"
13 int "Accuracy specification to request from clock in PPM"
21 int "Precision specification to request from clock"
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | tcpc.rst | 50 .. _tcpc-specification:
51 https://www.usb.org/document-library/usb-type-cr-port-controller-interface-specification
53 .. _usb-type-c-specification:
54 https://www.usb.org/document-library/usb-type-cr-cable-and-connector-specification-revision-21
56 .. _usb-pd-specification:
|
| D | bc12.rst | 6 The Battery Charging specification, currently at revision 1.2, is commonly
8 devices to draw current exceeding the USB 2.0 specification limit of 0.5A, 2.5W.
10 The BC1.2 specification uses the term Charging Port for the device that supplies
14 Note that the `BC1.2 Specification`_ uses the acronym PD for Portable Device. This
22 Key parameters from the `BC1.2 Specification`_ include:
39 .. _BC1.2 Specification: https://www.usb.org/document-library/battery-charging-v12-spec-and-adopter…
64 specification.
66 To comply with the USB 2.0 specification, when the driver detects a SDP
|
| D | espi.rst | 18 See `eSPI interface specification`_ for additional details.
26 .. _eSPI interface specification:
|
| /Zephyr-latest/dts/bindings/auxdisplay/ |
| D | hit,hd44780.yaml | 57 Default is as per Hitachi HD44780 specification.
64 Default is as per Hitachi HD44780 specification.
71 another command. Default is as per Hitachi HD44780 specification.
78 sending another command. Default is as per Hitachi HD44780 specification.
85 another command. Default is as per Hitachi HD44780 specification.
|
| /Zephyr-latest/samples/bluetooth/channel_sounding/ |
| D | README.rst | 130 …itude] `Bluetooth Core Specification v. 6.0: Vol. 1, Part A, 9.2 <https://www.bluetooth.com/wp-con…
131 …ckets] `Bluetooth Core Specification v. 6.0: Vol. 1, Part A, 9.3 <https://www.bluetooth.com/wp-con…
132 …hase] `Bluetooth Core Specification v. 6.0: Vol. 6, Part D, 6.34 <https://www.bluetooth.com/wp-con…
133 …tart] `Bluetooth Core Specification v. 6.0: Vol. 6, Part D, 6.35 <https://www.bluetooth.com/wp-con…
|
| /Zephyr-latest/tests/bsim/bluetooth/host/privacy/device/ |
| D | README.rst | 12 type. That, even if they have previously exchanged IRK; (Core Specification version 5.4, vol. 1
17 For references, see the Bluetooth Core specification version 5.4, vol. 1, part A, 5.4.5 and vol. 6,
|
| /Zephyr-latest/soc/common/riscv-privileged/ |
| D | soc_irq.S | 9 * privileged architecture specification
19 * SOCs that do not truly follow the riscv privilege specification.
|
| /Zephyr-latest/modules/canopennode/ |
| D | Kconfig | 69 303-3 specification.
77 specification.
111 to the CiA 302-3 (draft) specification.
|
| /Zephyr-latest/samples/bluetooth/mtu_update/ |
| D | README.rst | 25 Answer: Yes. [#mtu_exchange]_ The Bluetooth specification mandates a symmetric MTU for ATT.
41 According to the Bluetooth specification, [#mtu]_ MTU is the maximum size of
120 .. [#mtu_exchange] Bluetooth Core Specification v. 5.3: Vol. 3, Part F, 3.4.2
121 .. [#mtu] Bluetooth Core Specification v. 5.3: Vol. 3, Part A, 5.1
122 .. [#sud_encapsulation] Bluetooth Core Specification v. 5.3: Vol. 3, Part A, 7.3
|
| /Zephyr-latest/include/zephyr/net/ |
| D | wifi_utils.h | 31 /** Maximum length of the band specification string */
34 /** Maximum length of the channel specification string */
38 * @brief Convert a band specification string to a bitmap representing the bands.
78 * @brief Convert a string containing a specification of scan channels to an array.
94 * An example channel specification specifying channels in the 2.4 GHz and 5 GHz bands is
|
| /Zephyr-latest/doc/build/dts/ |
| D | index.rst | 44 For the platform-independent details, see the `Devicetree specification`_.
46 .. _Devicetree specification: https://www.devicetree.org/
|
| /Zephyr-latest/dts/bindings/gpio/ |
| D | mikro-bus.yaml | 12 … https://download.mikroe.com/documents/standards/mikrobus/mikrobus-standard-specification-v200.pdf
29 the description above as it's according to the standard's specification.
|
12345678910>>...19
