| /Zephyr-latest/doc/hardware/peripherals/ |
| D | bc12.rst | 10 The BC1.2 specification uses the term Charging Port for the device that supplies
11 VBUS on the USB connection and the term Portable Device for the device that
14 Note that the `BC1.2 Specification`_ uses the acronym PD for Portable Device. This
15 should not be confused with the USB-C Power Delivery, which also uses the
19 charger capability on USB type C ports when the attached type-C partner does not
27 Allowed PD (portable device) Current Draw from Charging Port IDEV_CHG 1.5 A
28 Charging Downstream Port Rated Current ICDP 1.5 - 5.0 A
30 Dedicated Charging Port Rated Current IDCP 1.5 - 5.0 A
37 the Zephyr implementation when using portable-device mode.
39 …. _BC1.2 Specification: https://www.usb.org/document-library/battery-charging-v12-spec-and-adopter…
[all …]
|
| D | rtc.rst | 3 Real-Time Clock (RTC)
9 .. list-table:: **Glossary**
11 :header-rows: 1
13 * - Word
14 - Definition
15 * - Real-time clock
16 - Low power device tracking time using broken-down time
17 * - Real-time counter
18 - Low power counter which can be used to track time
19 * - RTC
[all …]
|
| /Zephyr-latest/drivers/usb/bc12/ |
| D | Kconfig.pi3usb9201 | 2 # SPDX-License-Identifier: Apache-2.0
9 This is a Dual-Role USB Charging-Type Detector. It can operate in
12 (SDP/CDP/DCP) advertisement when in host mode. In portable device or
24 charginging device.
39 before switching to SDP mode, so the attached portable device can
|
| /Zephyr-latest/include/zephyr/drivers/usb/ |
| D | emul_bc12.h | 4 * SPDX-License-Identifier: Apache-2.0
43 * @brief Set the charging partner type connected to the BC1.2 device.
54 * @retval -EINVAL if the partner type is not supported.
60 (const struct bc12_emul_driver_api *)target->backend_api; in bc12_emul_set_charging_partner()
62 return backend_api->set_charging_partner(target, partner_type); in bc12_emul_set_charging_partner()
66 * @brief Set the portable device partner state.
69 * to simulate connection or disconnection of a portable device partner.
74 * @param connected If true, emulate a connection of a portable device partner. If
78 * @retval -EINVAL if the connection/disconnection of PD partner is not supported.
83 (const struct bc12_emul_driver_api *)target->backend_api; in bc12_emul_set_pd_partner()
[all …]
|
| /Zephyr-latest/dts/bindings/usb/ |
| D | usb-bc12.yaml | 2 # SPDX-License-Identifier: Apache-2.0
9 charging-mode:
13 Define the charging port mode supported by the BC1.2 device.
15 - BC12_TYPE_NONE: Device does not support charging and only supports
16 portable-device mode.
17 - BC12_TYPE_SDP: Device supports SDP (standard downstream port)
20 - BC12_TYPE_CDP: Device supports CDP (charging downstream port)
23 - BC12_TYPE_DCP: Device supports DCP (dedicated charging port)
27 - BC12_TYPE_NONE
28 - BC12_TYPE_SDP
[all …]
|
| /Zephyr-latest/tests/drivers/usb/bc12/src/ |
| D | pd_mode.c | 4 * SPDX-License-Identifier: Apache-2.0
12 * @brief TestPurpose: Verify BC1.2 devices in portable device mode.
26 const struct device *bc12_dev;
33 static void bc12_test_result_cb(const struct device *dev, struct bc12_partner_state *state, in bc12_test_result_cb()
38 fixture->callback_count++; in bc12_test_result_cb()
41 if (state->bc12_role == BC12_PORTABLE_DEVICE) { in bc12_test_result_cb()
42 LOG_INF("charging partner: type %d, voltage %d, current %d", state->type, in bc12_test_result_cb()
43 state->voltage_uv, state->current_ua); in bc12_test_result_cb()
44 } else if (state->bc12_role == BC12_CHARGING_PORT) { in bc12_test_result_cb()
45 LOG_INF("portable device partner: connected %d", in bc12_test_result_cb()
[all …]
|
| D | charging_mode.c | 4 * SPDX-License-Identifier: Apache-2.0
26 const struct device *bc12_dev;
31 static void bc12_test_result_cb(const struct device *dev, struct bc12_partner_state *state, in bc12_test_result_cb()
37 if (state->bc12_role == BC12_PORTABLE_DEVICE) { in bc12_test_result_cb()
38 LOG_INF("charging partner: type %d, voltage %d, current %d", state->type, in bc12_test_result_cb()
39 state->voltage_uv, state->current_ua); in bc12_test_result_cb()
40 } else if (state->bc12_role == BC12_CHARGING_PORT) { in bc12_test_result_cb()
41 LOG_INF("portable device partner: connected %d", in bc12_test_result_cb()
42 state->pd_partner_connected); in bc12_test_result_cb()
44 fixture->partner_state = *state; in bc12_test_result_cb()
[all …]
|
| /Zephyr-latest/drivers/led_strip/ |
| D | ws2812_gpio.c | 6 * SPDX-License-Identifier: Apache-2.0
22 #include <zephyr/device.h>
25 #include <zephyr/dt-bindings/led/led.h>
41 * We should be able to make this portable using the results of
42 * https://github.com/zephyrproject-rtos/zephyr/issues/11917.
44 * We already have the GPIO device stashed in ws2812_gpio_config, so
47 * Per Arm docs, both Rd and Rn must be r0-r7, so we use the "l"
76 static int send_buf(const struct device *dev, uint8_t *buf, size_t len) in send_buf()
78 const struct ws2812_gpio_cfg *config = dev->config; in send_buf()
79 volatile uint32_t *base = (uint32_t *)&NRF_GPIO->OUTSET; in send_buf()
[all …]
|
| /Zephyr-latest/subsys/secure_storage/ |
| D | Kconfig | 2 # SPDX-License-Identifier: Apache-2.0
12 API in a standard and portable way.
16 the device-specific security features that are available and used, the subsystem may
18 This is however highly dependent on the device and configuration in use, and not a
24 module-str = secure_storage
|
| /Zephyr-latest/doc/services/crypto/ |
| D | psa_crypto.rst | 9 The PSA (Platform Security Architecture) Crypto API offers a portable
11 across a wide range of hardware. It is designed to be user-friendly
12 while still providing access to the low-level primitives essential for
20 open-source cryptographic library that provides the underlying
27 special-purpose cryptographic processors that process data with a
28 built-in key, to constrained devices running custom application code,
29 such as microcontrollers, and multi-application devices, such as
52 Future-Proofing
55 practices, enhancing long-term security and compliance.
65 or file-based, with master encryption keys stored inside a key store.
[all …]
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | overview.rst | 15 Example use-cases of Zephyr's user mode features:
17 - The kernel can protect against many unintentional programming errors which
20 - The kernel can sandbox complex data parsers such as interpreters, network
21 protocols, and filesystems such that malicious third-party code or data
24 - The kernel can support the notion of multiple logical "applications", each
31 For threads running in a non-privileged CPU state (hereafter referred to as
34 - We prevent access to memory not specifically granted, or incorrect access to
36 read-only area.
38 - Access to thread stack buffers will be controlled with a policy which
41 - A user thread will by default have read/write access to its own stack
[all …]
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | clocks.rst | 18 the advantages of being universally portable and pervasively
46 ----------
66 word, these conversions expand to a 2-4 operation sequence, requiring
77 expected to be the utility used by most portable application code.
81 own conversions to portable real time units) may access this with
127 being 32 bits. Large uptime counts in non-tick units will experience
129 timing-sensitive applications with long uptimes will be configured to
142 -------------
146 a double-linked list, with an attendant delta count in ticks from the
150 expected to be embedded within subsystem-defined data structures (for
[all …]
|
| /Zephyr-latest/include/zephyr/drivers/ |
| D | i2c.h | 10 * SPDX-License-Identifier: Apache-2.0
27 #include <zephyr/device.h>
55 /** Device Tree specified speed */
65 /** Use 10-bit addressing. DEPRECATED - Use I2C_MSG_ADDR_10_BITS instead. */
78 const struct device *bus;
89 * @param node_id Devicetree node identifier for the I2C device whose
103 * @param node_id Devicetree node identifier for the I2C device whose
117 * @param node_id Devicetree node identifier for the I2C device whose
160 * that follows a write, or vice-versa. Some drivers will merge
165 /** Use 10-bit addressing for this message.
[all …]
|
| D | i3c.h | 5 * SPDX-License-Identifier: Apache-2.0
24 #include <zephyr/device.h>
42 * - BCR[7:6]: Device Role
43 * - 0: I3C Target
44 * - 1: I3C Controller capable
45 * - 2: Reserved
46 * - 3: Reserved
48 * - BCR[5]: Advanced Capabilities
49 * - 0: Does not support optional advanced capabilities.
50 * - 1: Supports optional advanced capabilities which
[all …]
|
| /Zephyr-latest/doc/kernel/services/smp/ |
| D | smp.rst | 14 a supported dual processor device, they will both run simultaneously.
26 non-Zephyr code).
54 on top of the pre-existing :c:struct:`atomic_` layer (itself usually
65 re-acquire it or it will deadlock (it is perfectly legal to nest
71 recursive semantics above, spinlocks in single-CPU contexts produce
85 and that it is re-acquired when necessary to restore the lock state
109 :c:func:`k_thread_cpu_mask_enable` will re-enable execution. There are also
113 suspended, otherwise an ``-EINVAL`` will be returned.
116 involved in doing the per-CPU mask test requires that the list be
117 traversed in full. The kernel does not keep a per-CPU run queue.
[all …]
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr.rst | 9 The management subsystem allows remote management of Zephyr-enabled devices.
28 management subsystem that is portable across multiple real-time operating
34 Additionally, there is a :zephyr:code-sample:`sample <smp-svr>` server that provides
43 device which are listed below. Note that these tools are not part of or related to the Zephyr
51 …--------------------------------------------------------------------------------+-----------------…
53 … +---------+-------+-----+--------+----------+--------+-----------+-----+----+-----+----…
56 …✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | Application | C++ (Qt) | GPL-3.0 |
57 …--------------------------------------------------------------------------------+---------+-------…
58 …-client <https://github.com/vouch-opensource/mcumgr-client/>`_ | ✓ | ✓ | ✓ | …
59 …--------------------------------------------------------------------------------+---------+-------…
[all …]
|
| /Zephyr-latest/include/zephyr/bluetooth/ |
| D | gap.h | 8 * SPDX-License-Identifier: Apache-2.0
42 #define BT_DATA_UUID16_SOME 0x02 /**< 16-bit UUID, more available */
43 #define BT_DATA_UUID16_ALL 0x03 /**< 16-bit UUID, all listed */
44 #define BT_DATA_UUID32_SOME 0x04 /**< 32-bit UUID, more available */
45 #define BT_DATA_UUID32_ALL 0x05 /**< 32-bit UUID, all listed */
46 #define BT_DATA_UUID128_SOME 0x06 /**< 128-bit UUID, more available */
47 #define BT_DATA_UUID128_ALL 0x07 /**< 128-bit UUID, all listed */
51 #define BT_DATA_DEVICE_CLASS 0x0d /**< Class of Device */
52 #define BT_DATA_SIMPLE_PAIRING_HASH_C192 0x0e /**< Simple Pairing Hash C-192 */
53 #define BT_DATA_SIMPLE_PAIRING_RAND_C192 0x0f /**< Simple Pairing Randomizer R-192 */
[all …]
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | index.rst | 69 value -- for example, to allow device hardware used by the thread
75 re-spawned before it can be used.
91 thread self-exits, or the target thread aborts (either due to a
96 re-used for any purpose, including spawning a new thread. Note that
176 - There may need to be additional memory reserved for memory management
178 - If guard-based stack overflow detection is enabled, a small write-protected
181 - If userspace is enabled, a separate fixed-size privilege elevation stack must
183 - If userspace is enabled, the thread's stack buffer must be appropriately
191 Because of this, portable code can't simply pass an arbitrary character buffer
195 Kernel-only Stacks
[all …]
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-2.3.rst | 18 with future support for features like 64-bit and absolute timeouts in mind
21 * Zephyr now integrates with the TF-M (Trusted Firmware M) PSA-compliant
24 * The CMSIS-DSP library is now included and integrated
33 * CVE-2020-10022: UpdateHub Module Copies a Variable-Sized Hash String
34 into a fixed-size array.
35 * CVE-2020-10059: UpdateHub Module Explicitly Disables TLS
37 * CVE-2020-10061: Improper handling of the full-buffer case in the
39 * CVE-2020-10062: Packet length decoding error in MQTT
40 * CVE-2020-10063: Remote Denial of Service in CoAP Option Parsing Due
42 * CVE-2020-10068: In the Zephyr project Bluetooth subsystem, certain
[all …]
|
| D | release-notes-3.3.rst | 14 * Introduced :ref:`USB-C <usbc_api>` device stack with PD (power delivery)
17 CMSIS-DSP as the default backend.
30 * CVE-2023-0359: Under embargo until 2023-04-20
32 * CVE-2023-0779: Under embargo until 2023-04-22
66 removed in favor of new :dtcompatible:`zephyr,flash-disk` devicetree binding.
71 * Starting from this release ``zephyr-`` prefixed tags won't be created
82 image states). Use of a truncated hash or non-sha256 hash will still work
88 registration function at boot-up. If applications register this then
93 application code, these will now automatically be registered at boot-up (this
129 This may cause out-of-tree scripts or commands to fail if they have relied
[all …]
|
| D | release-notes-2.6.rst | 13 * Added support for 64-bit ARCv3
14 * Split ARM32 and ARM64, ARM64 is now a top-level architecture
15 * Added initial support for Arm v8.1-m and Cortex-M55
19 * Device runtime power management (PM), former IDLE runtime, was
22 https://github.com/zephyrproject-rtos/example-application
34 * CVE-2021-3581: Under embargo until 2021-09-04
41 <https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aissue+is%3Aopen+label%3Abug>`_.
46 * Driver APIs now return ``-ENOSYS`` if optional functions are not implemented.
47 If the feature is not supported by the hardware ``-ENOTSUP`` will be returned.
48 Formerly ``-ENOTSUP`` was returned for both failure modes, meaning this change
[all …]
|
| /Zephyr-latest/scripts/ |
| D | spelling.txt | 470 deivce||device
516 deviece||device
1062 none existent||non-existent
1257 protable||portable
1703 vicefersa||vice-versa
|
| /Zephyr-latest/boards/adi/max78002evkit/doc/ |
| D | index.rst | 5 The MAX78002 evaluation kit (EV kit) provides a platform and tools for leveraging device capabiliti…
10 are supported, while a pair of industry-standard QWIIC connectors supports a large and growing arra…
11 development boards. An onboard stereo audio codec offers line-level audio input and output, and tac…
12 provided by a touch-enabled 2.4in TFT display. The MAX78002 energy consumption is tracked by a powe…
13 with four channels of formatted results presented on a secondary TFT display. All device GPIOs are …
14 … headers. A standard coaxial power jack serves as power input, using the included 5V, 3A wall-mount
17 microSD connector provides the capability for inexpensive highdensity portable data storage.
32 - MAX78002 MCU:
34 - Dual-Core, Low-Power Microcontroller
36 - Arm Cortex-M4 Processor with FPU up to 120MHz
[all …]
|
| /Zephyr-latest/boards/adi/max32690evkit/doc/ |
| D | index.rst | 6 of the MAX32690 microcontroller, which is an advanced system-on-chip (SoC).
7 It features an Arm® Cortex®-M4F CPU for efficient computation of complex functions and
9 for wearable and hearable fitness devices, portable and wearable wireless medical devices,
25 - MAX32690 MCU:
27 - Ultra-Efficient Microcontroller for Battery-Powered Applications
29 - 120MHz Arm Cortex-M4 Processor with FPU
30 - 7.3728MHz and 60MHz Low-Power Oscillators
31 - External Crystal Support (32MHz required for BLE)
32 - 32.768kHz RTC Clock (Requires External Crystal)
33 - 8kHz Always-On Ultra-Low Power Oscillator
[all …]
|
| /Zephyr-latest/include/zephyr/ |
| D | kernel.h | 4 * SPDX-License-Identifier: Apache-2.0
53 #define K_PRIO_COOP(x) (-(CONFIG_NUM_COOP_PRIORITIES - (x)))
56 #define K_HIGHEST_THREAD_PRIO (-CONFIG_NUM_COOP_PRIORITIES)
60 #define K_LOWEST_APPLICATION_THREAD_PRIO (K_LOWEST_THREAD_PRIO - 1)
245 * bits, arch-specific use high bits.
289 * from within a user-provided callback they have been invoked.
290 * Effectively it serves as a tiny bit of zero-overhead TLS data.
328 /* end - thread options */
335 * - @ref K_USER allocate a userspace thread (requires `CONFIG_USERSPACE=y`)
353 * @retval -EBUSY if the thread stack is in use.
[all …]
|
