Home
last modified time | relevance | path

Searched refs:has (Results 751 – 775 of 1361) sorted by relevance

1...<<31323334353637383940>>...55

/Zephyr-4.1.0/doc/releases/
Drelease-notes-3.1.rst27 unconfirmed message, this has to be changed to ``LORAWAN_MSG_UNCONFIRMED``.
118 * The TinyCBOR module has been deprecated in favor of the new zcbor CBOR
135 * The ``pin`` prefix has been removed from all PWM API calls. So for example,
145 * :c:macro:`UTIL_LISTIFY` has been deprecated. Use :c:macro:`LISTIFY` instead.
254 function has been deprecated. Use the new ``subscribe`` callback
301 documentation has always promised but the kernel has never
314 when a thread timeslice has expired. The intent is that this will
758 * A new Zephyr SDK has been created which now supports macOS and Windows in
790 * :dtcompatible:`espressif,esp32-pinctrl` has replaced ``espressif,esp32-pinmux``
796 …* :dtcompatible:`nxp,kinetis-pinctrl` has replaced the ``nxp,kinetis-port-pins`` property found in…
[all …]
/Zephyr-4.1.0/subsys/bluetooth/host/
DKconfig209 When this option has been enabled, it's important that the
247 bool "Store CCC value immediately after it has been written"
252 Store Client Configuration Characteristic value right after it has
257 bool "Store CF value immediately after it has been written"
262 Store Client Supported Features value right after it has been updated.
406 stack. The remote information is retrieved once a connection has been
474 An attacker that has stolen or once bonded and retained the IRK can
475 forever resolve addresses from that IRK, even if that bond has been
492 If the application has not setup an identity before calling
498 If the controller has a public address (HCI_Read_BD_ADDR), that becomes
[all …]
/Zephyr-4.1.0/doc/connectivity/bluetooth/api/audio/
Dbluetooth-le-audio-arch.rst214 HAS_H [label="has.h"];
390 * As the table shows, the Broadcast Source role has no dependencies on other LE Audio profiles or s…
892 the procedure has active involvement or requirements from the CAP Initiator, CAP Accept and CAP
935 ASCS require that each characteristic in the service has unique data per client.
1047 For example, if there is more than one TBS on a device and each has a unique telephone bearer
1058 GTBS may be standalone (i.e.the device only has a GTBS instance without any TBS instances),
1062 but the majority of the information in the GTBS instance in Zephyr has been implemented to be a
1102 Thus if a device has multiple MCS instances,
1186 and how much control the role has in a given context.
1221 The Basic Audio Profile (BAP) has a requirement that both sides shall support a minimum ATT_MTU of
[all …]
/Zephyr-4.1.0/samples/kernel/metairq_dispatch/
DREADME.rst17 Each message has a random (and non-trivial) amount of processing that
44 occasionally has more work to do than time available.
/Zephyr-4.1.0/boards/seeed/lora_e5_mini/doc/
Dindex.rst64 LoRa-E5 mini has 4 GPIO controllers. These controllers are responsible for pin
106 firmware, from which seeed studio has neither released the source code nor a binary.
/Zephyr-4.1.0/cmake/modules/
DFindZephyr-sdk.cmake34 # Each entry in Zephyr-SDK has a corresponding entry in Zephyr-SDK_DIRS.
149 # A compatible version of the Zephyr SDK has been found which is the highest
/Zephyr-4.1.0/boards/lilygo/ttgo_t8s3/doc/
Dindex.rst21 has an USB-C port for programming and debugging, integrated battery charging
202 After the board has automatically reset and booted, you should see the following
/Zephyr-4.1.0/boards/lilygo/ttgo_t8c3/doc/
Dindex.rst20 has an USB-C port for programming and debugging, integrated battery charging
188 After the board has automatically reset and booted, you should see the following
/Zephyr-4.1.0/dts/arm/renesas/ra/ra8/
Dr7fa8t1xh.dtsi409 has-internal-output;
410 has-output-amplifier;
/Zephyr-4.1.0/boards/st/nucleo_l432kc/doc/
Dindex.rst99 Nucleo L432KC Board has 6 GPIO controllers. These controllers are responsible for pin muxing,
132 Nucleo L432KC board has 3 U(S)ARTs. The Zephyr console output is assigned to UART2.
/Zephyr-4.1.0/boards/nxp/lpcxpresso55s28/doc/
Dindex.rst89 The LPC55S28 SoC has IOCON registers, which can be used to configure
130 The LPC55S28 SoC has 8 FLEXCOMM interfaces for serial communication. One is
/Zephyr-4.1.0/boards/st/nucleo_f767zi/doc/
Dindex.rst87 nucleo_f767zi with soc cut-A (Device marking A) has some ethernet
129 Nucleo F767ZI board has 4 UARTs and 4 USARTs. The Zephyr console output is
/Zephyr-4.1.0/boards/adi/eval_adin2111ebz/doc/
Dindex.rst86 ADI ADIN2111EBZ evaluation board has 7 GPIO controllers (from A to G).
115 EVAL-ADIN2111EBZ has 1 U(S)ART. The Zephyr console output is assigned to UART1 that is connected
/Zephyr-4.1.0/boards/st/nucleo_l433rc_p/doc/
Dindex.rst100 Nucleo L433RC-P Board has 6 GPIO controllers. These controllers are responsible for pin muxing,
135 Nucleo L433RC-P board has 4 U(S)ARTs and 1 LPUART. The Zephyr console output is assigned
/Zephyr-4.1.0/doc/security/standards/
Detsi-303645.rst26 - user who has the highest-privilege level possible for a user of the device,
42 - cryptography that is suitable for the corresponding use case and has no
46 - device which has physical limitations in either the ability to process data, the
55 - network-connected (and network-connectable) device that has relationships to
153 about the implementation of the provisions presented in the standard. Zephyr has
657 - Users should be provided with clear confirmation that personal data has been deleted
/Zephyr-4.1.0/doc/hardware/pinctrl/
Dindex.rst72 concept that has been adapted from the one in the Linux kernel. Each device
73 driver owns a set of states. Each state has a unique name and contains a full
102 required. In order to make things consistent, a naming convention has been
129 ``{STATE_NAME}`` is the capitalized state name. For example, if ``mystate`` has
351 the board already has one or because its value depends on the operating bus
432 Once the driver has defined the pin control configuration and kept a reference
/Zephyr-4.1.0/doc/connectivity/usb/device/
Dusb_device.rst15 It is a port of the LPCUSB device stack and has been modified and expanded
57 A second interface for the voice channels has not been implemented as there is
81 * Data transfer is only possible after the USB device stack has been
113 Sample :zephyr:code-sample:`usb-cdc-acm` has similar overlay files.
192 the best indication that host application has opened the tty device, Zephyr will
387 This option also has the effect of changing device descriptor ``bcdUSB`` to ``0210``.
567 Each USB :zephyr:code-sample-category:`sample<usb>` has its own unique Product ID.
/Zephyr-4.1.0/subsys/mgmt/osdp/
DKconfig65 As per the OSDP specification, the first byte in the channel has
/Zephyr-4.1.0/samples/net/sockets/coap_download/
DREADME.rst39 `Eclipse Californium`_ (Java) has a demo `Simple File Server`_ application.
/Zephyr-4.1.0/samples/sensor/ds18b20/
DREADME.rst38 Make sure this node has ``status = "okay";``, then build and run with:
/Zephyr-4.1.0/boards/shields/sparkfun_carrier_asset_tracker/doc/
Dindex.rst18 Besides, this shield has an integrated ICM-20948 Inertial Measurement Unit
/Zephyr-4.1.0/samples/drivers/led/xec/
DREADME.rst20 MEC172x has a fourth instance of BBLED:
/Zephyr-4.1.0/boards/silabs/radio_boards/slwrb4161a/doc/
Dindex.rst78 The EFR32MG12P SoC has four USARTs and one Low Energy UARTs (LEUART).
/Zephyr-4.1.0/boards/silabs/radio_boards/slwrb4170a/doc/
Dindex.rst78 The EFR32MG12P SoC has four USARTs and one Low Energy UARTs (LEUART).
/Zephyr-4.1.0/samples/boards/nordic/nrfx_prs/
DREADME.rst40 This sample has been tested on the Nordic Semiconductor nRF9160 DK

1...<<31323334353637383940>>...55