Searched +full:hw +full:- +full:flow +full:- +full:control +full:- +full:supported (Results 1 – 25 of 36) sorted by relevance
12
| /Zephyr-latest/dts/bindings/serial/ |
| D | renesas,smartbond-uart.yaml | 3 compatible: "renesas,smartbond-uart"
5 include: [uart-controller.yaml, pinctrl-device.yaml]
14 periph-clock-config:
19 current-speed:
24 - 4800
25 - 9600
26 - 14400
27 - 19200
28 - 28800
29 - 38400
[all …]
|
| /Zephyr-latest/boards/phytec/phyboard_pollux/ |
| D | phyboard_pollux_mimx8ml8_m7.dts | 4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
10 #include "phyboard_pollux-pinctrl.dtsi"
13 model = "phyBOARD-Pollux i.MX8MP";
22 zephyr,shell-uart = &uart4;
27 * BSP-Linux standard output. Can cause problems if used with standard bsp
30 compatible = "nxp,imx-iuart";
34 pinctrl-0 = <&uart1_default>;
35 pinctrl-names = "default";
40 * to Bluetooth module (currently not supported by zephyr)
[all …]
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-dev.rst | 1 .. _bluetooth-dev:
26 .. _bluetooth-hw-setup:
38 #. :ref:`Embedded <bluetooth-hw-setup-embedded>`
39 #. :ref:`External controller <bluetooth-hw-setup-external-ll>`
41 - :ref:`QEMU host <bluetooth-hw-setup-qemu-host>`
42 - :ref:`native_sim host <bluetooth-hw-setup-native-sim-host>`
44 #. :ref:`Simulated nRF5x with BabbleSim <bluetooth-hw-setup-bsim>`
46 .. _bluetooth-hw-setup-embedded:
53 All the :ref:`bluetooth-configs` and :ref:`bluetooth-build-types` are supported
54 but you might need to build Zephyr more than once if you are using a dual-chip
[all …]
|
| /Zephyr-latest/drivers/spi/ |
| D | spi_b91.c | 4 * SPDX-License-Identifier: Apache-2.0
38 #define SPI_CFG(dev) ((struct spi_b91_cfg *) ((dev)->config))
44 #define SPI_DATA(dev) ((struct spi_b91_data *) ((dev)->data))
47 /* disable hardware cs flow control */
55 pin = config->cs_pin[i]; in spi_b91_hw_cs_disable()
59 if (config->peripheral_id == PSPI_MODULE) { in spi_b91_hw_cs_disable()
70 /* config cs flow control: hardware or software */
77 /* software flow control */ in spi_b91_config_cs()
84 /* hardware flow control */ in spi_b91_config_cs()
87 if (config->slave >= CHIP_SELECT_COUNT) { in spi_b91_config_cs()
[all …]
|
| /Zephyr-latest/boards/native/nrf_bsim/ |
| D | nrf52_bsim.dts | 5 * SPDX-License-Identifier: Apache-2.0
8 /dts-v1/;
13 #include <../boards/nordic/nrf52833dk/nrf52833dk_nrf52833-pinctrl.dtsi>
21 /delete-property/ i2c-0;
22 /delete-property/ i2c-1;
23 /delete-property/ spi-0;
24 /delete-property/ spi-1;
25 /delete-property/ spi-2;
26 /delete-property/ spi-3;
27 /delete-property/ adc-0;
[all …]
|
| /Zephyr-latest/drivers/serial/ |
| D | uart_gecko.c | 5 * SPDX-License-Identifier: Apache-2.0
40 : -1)
44 : -1)
49 : -1)
55 : -1)
62 : -1)
70 : -1)
77 : -1)
84 /* Helper define to determine if SOC supports hardware flow control */
95 /* Has any enabled uart instance hw-flow-control enabled? */
[all …]
|
| D | uart_native_tty.c | 14 * SPDX-License-Identifier: Apache-2.0
77 bottom_cfg->baudrate = cfg->baudrate; in native_tty_conv_to_bottom_cfg()
79 switch (cfg->parity) { in native_tty_conv_to_bottom_cfg()
81 bottom_cfg->parity = NTB_PARITY_NONE; in native_tty_conv_to_bottom_cfg()
84 bottom_cfg->parity = NTB_PARITY_ODD; in native_tty_conv_to_bottom_cfg()
87 bottom_cfg->parity = NTB_PARITY_EVEN; in native_tty_conv_to_bottom_cfg()
90 return -ENOTSUP; in native_tty_conv_to_bottom_cfg()
93 switch (cfg->stop_bits) { in native_tty_conv_to_bottom_cfg()
95 bottom_cfg->stop_bits = NTB_STOP_BITS_1; in native_tty_conv_to_bottom_cfg()
98 bottom_cfg->stop_bits = NTB_STOP_BITS_2; in native_tty_conv_to_bottom_cfg()
[all …]
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-2.0.rst | 12 * The kernel now supports both 32- and 64-bit architectures.
17 * We added support for :ref:`Point-to-Point Protocol (PPP) <ppp>`. PPP is a
20 * We added support for UpdateHub, an end-to-end solution for large scale
21 over-the-air device updates.
22 * We added support for ARM Cortex-R Architecture (Experimental).
32 * Fixes CVE-2019-9506: The Bluetooth BR/EDR specification up to and
35 negotiation. This allows practical brute-force attacks (aka "KNOB")
42 * New kernel API for per-thread disabling of Floating Point Services for
43 ARC, ARM Cortex-M, and x86 architectures.
45 * Additional support for compatibility with 64-bit architectures.
[all …]
|
| D | release-notes-1.11.rst | 12 * Thread-level memory protection on x86, ARC and Arm, userspace and memory
15 * Initial Armv8-M architecture support.
20 * Firmware over-the-air (FOTA) updates over BLE using MCUmgr.
22 * Additional SoC, platform and driver support for many of the already supported
32 * SMP-aware scheduler
47 * Armv8-M initial architecture support, including the following cores:
49 * Arm Cortex-M23
50 * Arm Cortex-M33
74 * Refactored dts.fixup so common SoC-related fixes are in arch/<*>/soc
75 and board dts.fixup is only used for board-specific items.
[all …]
|
| D | release-notes-1.13.rst | 16 * Support for IEEE 802.1AS-2011 generalized Precision Time Protocol (gPTP)
23 * Basic support for Arm TrustZone in Armv8-M
42 * arch: arm: implement ARMv8-M MPU driver
44 * arch: arm: macro API for defining non-secure entry functions
48 * arch: ARM: Change the march used by cortex-m0 and cortex-m0plus
50 * arch: arm: basic Arm TrustZone-M functionality for Cortex-M23 and Cortex-M33
51 * arch: arm: built-in stack protection using Armv8-M SPLIM registers
52 * arch: arm: API for using TT intrinsics in Secure/Non-Secure Armv8-M firmware
63 * riscv32: riscv-privilege: Microsemi Mi-V support
85 * clock_control: Added STM32F7 family clock control
[all …]
|
| D | release-notes-1.14.rst | 17 * CVE-2020-10066
18 * CVE-2020-10069
19 * CVE-2020-13601
20 * CVE-2020-13602
32 * :github:`issuenumber` - issue title
34 * :github:`18334` - DNS resolution is broken for some addresses in master/2.0-pre
35 * :github:`19917` - Bluetooth: Controller: Missing LL_ENC_RSP after HCI LTK Negative Reply
36 * :github:`21107` - LL_ASSERT and 'Imprecise data bus error' in LL Controller
37 * :github:`21257` - tests/net/net_pkt failed on mimxrt1050_evk board.
38 * :github:`21299` - bluetooth: Controller does not release buffer on central side after peripheral …
[all …]
|
| D | release-notes-1.10.rst | 12 * Initial alpha-quality thread-level memory protection on x86, userspace and memory
18 * Additional SoC, platform and driver support for many of the already supported
27 * Initial alpha-quality thread-level memory protection on x86, userspace and memory
35 * Memory domain APIs for fine-tuning memory region permissions
38 * Add the following application-facing memory domain APIs:
40 * k_mem_domain_init() - to initialize a memory domain
41 * k_mem_domain_destroy() - to destroy a memory domain
42 * k_mem_domain_add_partition() - to add a partition into a domain
43 * k_mem_domain_remove_partition() - to remove a partition from a domain
44 * k_mem_domain_add_thread() - to add a thread into a domain
[all …]
|
| D | release-notes-1.7.rst | 10 nano- and micro-kernel APIs found in the 1.5.0 release and earlier.
52 * Added NXP FRDM-KW41Z board
53 * Added ST Nucleo-F334R8, Nucleo-L476G, STM3210C-EVAL, and STM32373C-EVAL boards
67 * Added Beetle clock control and watchdog drivers
102 * Created net-shell module for interacting with network sub-system.
136 * Imported Segger J-Link RTT library
143 * Moved supported board information back to the website site.
145 * New local-content generation theme (read-the-docs)
147 * Site-wide glossary added.
150 * Improved consistency of :ref:`boards` and :zephyr:code-sample-category:`samples`.
[all …]
|
| D | release-notes-2.5.rst | 27 * CVE-2021-3323: Under embargo until 2021-04-14
28 * CVE-2021-3321: Under embargo until 2021-04-14
29 * CVE-2021-3320: Under embargo until 2021-04-14
39 <https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aissue+is%3Aopen+label%3Abug>`_.
56 * Changed vcnl4040 dts binding default for property 'proximity-trigger'.
57 Changed the default to match the HW POR state for this property.
63 * The :c:func:`mqtt_keepalive_time_left` function now returns -1 if keep alive
67 timeout usage must use the new-style k_timeout_t type and not the
87 GPIO-only regulators a devicetree property ``supply-gpios`` is defined as a
88 standard way to identify the control signal in nodes that support power
[all …]
|
| D | release-notes-3.7.rst | 10 This release is the last non-maintenance 3.x release and, as such, will be the next
18 * A long-awaited :ref:`HTTP Server <http_server_interface>` library, and associated service API,
21 * :ref:`POSIX support <posix_support>` has been extended, with most Options of the IEEE 1003-2017
25 * Bluetooth Host has been extended with support for the Nordic UART Service (NUS), Hands-free Audio
29 :ref:`read-then-decode approach <sensor-read-and-decode>` that enables more types of sensors and
35 * Trusted Firmware-M (TF-M) 2.1.0 and Mbed TLS 3.6.0 have been integrated into Zephyr.
39 1588) allows to synchronize time across devices with sub-microsecond accuracy.
52 * 1-Wire
70 * Pinmux API has been removed. Pin control needs to be used as its replacement, refer to
71 :ref:`pinctrl-guide` for more details.
[all …]
|
| /Zephyr-latest/dts/arm/renesas/smartbond/ |
| D | da1469x.dtsi | 3 * SPDX-License-Identifier: Apache-2.0
6 #include <arm/armv8-m.dtsi>
9 #include <zephyr/dt-bindings/gpio/gpio.h>
10 #include <zephyr/dt-bindings/adc/smartbond-adc.h>
11 #include <zephyr/dt-bindings/pinctrl/smartbond-pinctrl.h>
12 #include <zephyr/dt-bindings/dma/dma_smartbond.h>
17 zephyr,flash-controller = &flash_controller;
21 compatible = "zephyr,lvgl-pointer-input";
25 #address-cells = <1>;
26 #size-cells = <0>;
[all …]
|
| /Zephyr-latest/boards/st/nucleo_wb55rg/ |
| D | nucleo_wb55rg.dts | 4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
9 #include <st/wb/stm32wb55rgvx-pinctrl.dtsi>
11 #include <zephyr/dt-bindings/input/input-event-codes.h>
14 model = "STMicroelectronics STM32WB55RG-NUCLEO board";
15 compatible = "st,stm32wb55rg-nucleo";
19 zephyr,shell-uart = &usart1;
20 zephyr,bt-mon-uart = &lpuart1;
21 zephyr,bt-c2h-uart = &lpuart1;
24 zephyr,code-partition = &slot0_partition;
[all …]
|
| /Zephyr-latest/include/zephyr/drivers/ |
| D | dma.h | 10 * SPDX-License-Identifier: Apache-2.0
137 * - 0b00 increment
138 * - 0b01 decrement
139 * - 0b10 no change
145 * - 0b00 increment
146 * - 0b01 decrement
147 * - 0b10 no change
154 /** FIFO fill before starting transfer, HW specific meaning */
157 * Transfer flow control mode
159 * - 0b0 source request service upon data availability
[all …]
|
| /Zephyr-latest/boards/u-blox/ubx_evkninab1/doc/ |
| D | index.rst | 3 u-blox EVK NINA-B11x
9 The u-blox NINA-B1 Evaluation Kit hardware is a Bluetooth
11 ARM Cortex-M4F CPU and has support for the following features:
17 * :abbr:`I2C (Inter-Integrated Circuit)`
25 * :abbr:`UART (Universal asynchronous receiver-transmitter)`
28 .. figure:: img/EVK-NINA-B1.jpg
30 EVK NINA-B1
32 More information about the NINA-B1 module and the EVK NINA-B1
33 can be found at `NINA-B1 product page`_ and
34 `EVK-NINA-B1 product page`_.
[all …]
|
| /Zephyr-latest/boards/u-blox/ubx_evkannab1/doc/ |
| D | index.rst | 3 u-blox EVK-ANNA-B11x
9 The u-blox ANNA-B1 Evaluation Kit hardware is a Bluetooth low energy
10 module based on the Nordic Semiconductor nRF52832 ARM Cortex-M4F CPU
17 * :abbr:`I2C (Inter-Integrated Circuit)`
25 * :abbr:`UART (Universal asynchronous receiver-transmitter)`
28 .. figure:: img/EVK-ANNA-B112.jpg
30 EVK ANNA-B1
32 More information about the ANNA-B1 module and the EVK-ANNA-B1
33 can be found at `ANNA-B1 product page`_ and
34 `EVK-ANNA-B1 product page`_.
[all …]
|
| /Zephyr-latest/boards/u-blox/ubx_evkninab4/doc/ |
| D | index.rst | 3 u-blox EVK NINA-B40x
9 The u-blox NINA-B4 Evaluation Kit hardware is a Bluetooth low energy
10 module based on the Nordic Semiconductor nRF52833 ARM Cortex-M4F CPU
17 * :abbr:`I2C (Inter-Integrated Circuit)`
25 * :abbr:`UART (Universal asynchronous receiver-transmitter)`
29 .. figure:: img/EVK-NINA-B406_Top_web.jpg
31 EVK NINA-B4
33 More information about the NINA-B4 module and the EVK-NINA-B4 can be
34 found at `NINA-B40 product page`_ and `EVK-NINA-B4 product page`_.
36 Supported Features
[all …]
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | arm_cortex_m.rst | 3 Arm Cortex-M Developer Guide
9 This page contains detailed information about the status of the Arm Cortex-M
11 developing Zephyr applications for Arm Cortex-M-based platforms.
13 Key supported features
17 Arm Cortex-M implementation variants.
20 …---------------------------------+-----------------------------------+-----------------+---------+…
22 …---------------------------------+-----------------------------------+-----------------+---------+…
23 … | Arm v6-M | Arm v7-M | Arm v8-M …
24 …---------------------------------+-----------------------------------+-----------------+---------+…
26 …---------------------------------+-----------------------------------+-----------------+---------+…
[all …]
|
| /Zephyr-latest/boards/intel/socfpga_std/cyclonev_socdk/doc/ |
| D | index.rst | 10 The Zephyr kernel is supported on the Intel® Cyclone® V SoC Development Kit,
37 * J26: Short pins 1-2
38 * J27: Short pins 2-3
39 * J28: Short pins 1-2
40 * J29: Short pins 2-3
41 * J30: Short pins 1-2
48 * SW3: ON-OFF-ON-OFF-ON-ON
49 * SW4: OFF-OFF-ON-ON
51 Other switches are user switches, their position is application-specific.
58 ….intel.com/content/www/us/en/software-kit/684215/intel-quartus-prime-lite-edition-design-software-…
[all …]
|
| /Zephyr-latest/doc/connectivity/usb/device_next/ |
| D | usb_device.rst | 18 high-speed device controllers are supported. It also provides support for
20 or changing the configuration later. It has built-in support for several USB
29 * :zephyr:code-sample:`usb-hid-keyboard`
31 * :zephyr:code-sample:`uac2-explicit-feedback`
33 * :zephyr:code-sample:`uac2-implicit-feedback`
36 ----------------------------------------
39 configuration ``-DCONF_FILE=usbd_next_prj.conf`` either directly or via
42 * :zephyr:code-sample:`bluetooth_hci_usb`
44 * :zephyr:code-sample:`usb-cdc-acm`
46 * :zephyr:code-sample:`usb-cdc-acm-console`
[all …]
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | arch.rst | 8 Interface)` that is not currently supported.
13 * ARMv7-M ISA with Thumb2 instruction set and ARM Embedded ABI (aeabi)
33 and architecture-dependent, and thread abortion possibly as well (required).
39 architecture-specific implementation for performance reasons (required).
44 * **Fault management**: for implementing architecture-specific debug help and
47 * **Linker scripts and toolchains**: architecture-specific details will most
50 * **Memory Management and Memory Mapping**: for architecture-specific details
53 * **Stack Objects**: for architecture-specific details on memory protection
71 * If running an :abbr:`XIP (eXecute-In-Place)` kernel, copy initialized data
79 Some examples of architecture-specific steps that have to be taken:
[all …]
|
12
