| /Zephyr-latest/subsys/task_wdt/ |
| D | Kconfig | 13 per thread, even if the hardware supports only a single watchdog.
25 bool "Use hardware watchdog as a fallback"
28 This option allows to specify a hardware watchdog device in the
42 If a hardware watchdog is configured as a fallback for the task
47 int "Additional delay for hardware watchdog (ms)"
52 The timeout of the hardware watchdog fallback will be increased by
57 between different clock sources for the hardware watchdog and the
58 kernel timer. This is especially important if the hardware watchdog
|
| /Zephyr-latest/include/zephyr/sys/ |
| D | time_units.h | 279 * "cyc" => "hardware cycles",
345 /** @brief Convert seconds to hardware cycles. 32 bits. Truncates.
347 * Converts time values in seconds to hardware cycles.
355 * @return The converted time value in hardware cycles. uint32_t
361 /** @brief Convert seconds to hardware cycles. 64 bits. Truncates.
363 * Converts time values in seconds to hardware cycles.
371 * @return The converted time value in hardware cycles. uint64_t
377 /** @brief Convert seconds to hardware cycles. 32 bits. Round nearest.
379 * Converts time values in seconds to hardware cycles.
387 * @return The converted time value in hardware cycles. uint32_t
[all …]
|
| /Zephyr-latest/include/zephyr/drivers/dma/ |
| D | dma_mcux_lpc.h | 11 * LPC DMA engine channel hardware trigger attributes.
14 * hardware triggering.
22 /* Hardware trigger enable. When set, the hardware trigger connected to this
33 * When it is cleared, the hardware trigger will be edge triggered.
37 /* HW trigger burst mode. When set, the hardware trigger will cause a burst
45 * field, the maximum transfer burst possible is 128. The hardware supports
|
| /Zephyr-latest/dts/bindings/usb/ |
| D | usb-ep.yaml | 4 # Common fields that give the number of endpoints supported by the USB hardware
13 Number of bi-directional endpoints supported by hardware
19 Number of IN endpoints supported by hardware
25 Number of OUT endpoints supported by hardware
|
| /Zephyr-latest/doc/build/dts/ |
| D | dt-vs-kconfig.rst | 12 * Use devicetree to describe **hardware** and its **boot-time configuration**.
19 In other words, devicetree mainly deals with hardware, and Kconfig with
25 * The fact that the board has this UART **hardware** is described with two UART
27 property) and certain settings such as the address range of the hardware
41 * Devicetree should be used to describe the presence of the radio **hardware**,
51 :ref:`status <dt-important-props>` keyword on the corresponding hardware
59 specific to Zephyr drivers and not hardware description or configuration these
64 instance of a hardware device to be used for a particular purpose. An example
|
| D | intro-scope-purpose.rst | 7 hardware. The `Devicetree specification`_ defines its source and binary
14 - the hardware available on its :ref:`boards`
15 - that hardware's initial configuration
17 As such, devicetree is both a hardware description language and a configuration
|
| /Zephyr-latest/drivers/ethernet/dwc_xgmac/ |
| D | Kconfig | 18 as "DesignWare Cores Ethernet XGMAC". Hardware versions
50 Number hardware queues supported by the XGMAC IP
73 Enable Hardware support for L2 filtering of packets.
78 Enable Hardware support for L3 L4 filtering of packets.
83 Enable ARP hardware offloading support.
|
| /Zephyr-latest/dts/bindings/watchdog/ |
| D | nxp,s32-swt.yaml | 27 Defaults to access enabled for all masters (hardware reset value).
42 - fixed: writes a fixed sequence as defined by hardware.
44 Defaults to "fixed" (hardware reset value).
51 Defaults to 0 (hardware reset value).
66 Defaults to unlocked (hardware reset value).
|
| /Zephyr-latest/drivers/ethernet/nxp_enet/ |
| D | Kconfig | 51 bool "Use DTCM for hardware DMA buffers"
54 Place the hardware DMA buffers into DTCM for better
58 bool "Hardware acceleration"
61 Enable hardware acceleration for the following:
102 bool "Use DTCM for hardware DMA buffers"
105 Place the hardware DMA buffers into DTCM for better
109 bool "Hardware acceleration"
112 Enable hardware acceleration for the following:
|
| /Zephyr-latest/boards/nordic/nrf5340_audio_dk/doc/ |
| D | index.rst | 19 Hardware section in nRF5340 Audio DK
22 The nRF5340 Audio DK comes with the following hardware features:
38 …t the board can be found at the `nRF5340 Audio DK website`_. The `nRF5340 Audio DK hardware guide`_
56 The `nRF5340 Audio DK hardware guide`_ contains the processor's information and
62 See :ref:`nrf5340dk_nrf5340` and `nRF5340 Audio DK hardware guide`_
63 for a complete list of nRF5340 Audio DK board hardware features.
108 https://www.nordicsemi.com/Products/Development-hardware/nrf5340-audio-dk
109 .. _nRF5340 Audio DK hardware guide: https://docs.nordicsemi.com/bundle/ug_nrf5340_audio/page/UG/nr…
|
| /Zephyr-latest/drivers/mspi/ |
| D | Kconfig | 12 Enable support for the MSPI hardware bus.
26 support depends on the driver and the hardware it runs on.
43 Describes controller hardware XIP capability and
49 Describes controller hardware scrambling capability and
|
| /Zephyr-latest/drivers/dma/ |
| D | Kconfig.dw_common | 20 bool "hardware supports scatter gather"
23 The hardware is by default expected to support hardware LLI (scatter gather).
32 with the DRAIN bit flag set to allow for the hardware FIFO to be drained
|
| /Zephyr-latest/dts/bindings/regulator/ |
| D | regulator.yaml | 80 ramp delay for regulator(in uV/us) For hardware which supports disabling
122 capabilities of every hardware so each device binding documentation
130 possible operating modes depends on the capabilities of every hardware so
150 Set over current protection limit. This is a limit where hardware performs
158 Set over current error limit. This is a limit where part of the hardware
166 Set over current warning limit. This is a limit where hardware is assumed
175 Set over voltage protection limit. This is a limit where hardware performs
183 Set over voltage error limit. This is a limit where part of the hardware
192 Set over voltage warning limit. This is a limit where hardware is assumed
202 Set over under voltage protection limit. This is a limit where hardware
[all …]
|
| /Zephyr-latest/doc/_scripts/ |
| D | redirects.py | 84 ('guides/arch/arm_cortex_m', 'hardware/arch/arm_cortex_m'),
85 ('guides/arch/index', 'hardware/arch/index'),
86 ('guides/arch/x86', 'hardware/arch/x86'),
112 ('guides/emulator/index', 'hardware/emulator/index'),
127 ('guides/pinctrl/index', 'hardware/pinctrl/index'),
136 ('guides/porting/arch', 'hardware/porting/arch'),
137 ('guides/porting/board_porting', 'hardware/porting/board_porting'),
138 ('guides/porting/index', 'hardware/porting/index'),
139 ('guides/porting/shields', 'hardware/porting/shields'),
169 ('hardware/peripherals/eeprom', 'hardware/peripherals/eeprom/index'),
[all …]
|
| /Zephyr-latest/drivers/entropy/ |
| D | Kconfig.smartbond | 23 hardware to make them ready for thread mode consumers.
32 buffer goes below this number hardware entropy generation will be
41 hardware to make them ready for ISR consumers.
50 buffer goes below this number hardware entropy generation will be
|
| D | Kconfig.nrf5 | 40 hardware to make them ready for thread mode consumers.
49 buffer goes below this number hardware entropy generation will be
58 hardware to make them ready for ISR consumers.
67 buffer goes below this number hardware entropy generation will be
|
| D | Kconfig.stm32 | 26 hardware to make them ready for thread mode consumers.
35 buffer goes below this number hardware entropy generation will be
44 hardware to make them ready for ISR consumers.
53 buffer goes below this number hardware entropy generation will be
|
| /Zephyr-latest/soc/arm/beetle/ |
| D | soc.c | 9 * @brief System/hardware module for the ARM LTD Beetle SoC
11 * This module provides routines to initialize and support board-level hardware
21 * @brief Perform basic hardware initialization at boot.
|
| /Zephyr-latest/tests/boards/altera_max10/sysid/src/ |
| D | sysid.c | 19 TC_PRINT("[SysID] hardware and software appear to be in sync\n"); in ZTEST()
21 TC_PRINT("[SysID] software appears to be older than hardware\n"); in ZTEST()
23 TC_PRINT("[SysID] hardware appears to be older than software\n"); in ZTEST()
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | mspi.rst | 41 #. Initialize the hardware, including but not limited to:
43 * Check :c:struct:`mspi_cfg` against hardware's own capabilities to prevent
50 * Power on the hardware.
52 * Configure the hardware using :c:struct:`mspi_cfg` and possibly more
57 to re-initialize the hardware with new parameters during runtime.
65 #. Call :c:func:`mspi_dev_config` with device specific hardware settings obtained
79 #. Call API for additional setups if supported by hardware
104 In which case that a controller supports hardware command queue, user could take full
105 advantage of the hardware performance if scatter IO and callback management are supported
151 mspi-hardware-ce-num = < 0x0 >;
[all …]
|
| /Zephyr-latest/boards/xen/xenvm/doc/ |
| D | index.rst | 18 Hardware section in ARMv8 Xen Virtual Machine Example
23 The following hardware features are supported:
33 The kernel currently does not support other hardware features on this platform.
46 default value, which should be corrected for user's actual hardware.
58 Depending on the version of the GIC on your hardware, you may choose one of the
68 hardware you might want to change this option in the same way as Interrupt
77 configuration would not boot on your hardware. In this case you need to update
100 - if your hardware is based on GICv2:
106 - if your hardware is based on GICv3:
162 As was said earlier, Xen describes hardware using device tree and expects that
[all …]
|
| /Zephyr-latest/subsys/mgmt/updatehub/ |
| D | updatehub_priv.h | 40 return "Incompatible hardware"; in updatehub_response()
126 const char *hardware; member
137 const char *hardware; member
167 "supported-hardware", supported_hardware,
179 "supported-hardware", supported_hardware,
209 hardware, JSON_TOK_STRING),
227 hardware, JSON_TOK_STRING),
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig.sam_gmac | 28 int "Number of active hardware TX and RX queues"
35 Select the number of hardware queues used by the driver. Packets will be
44 traffic to be routed through a specific hardware queue. With this enabled
45 it is easier to verify whether the chosen hardware queue actually works.
47 the SAM GMAC hardware supports screening up to four traffic classes.
|
| /Zephyr-latest/dts/bindings/cpu/ |
| D | sifive-common.yaml | 9 hardware-exec-breakpoint-count:
11 description: Number of hardware break points
|
| /Zephyr-latest/doc/services/crypto/random/ |
| D | index.rst | 13 FIPS 140-2 [NIST02]_ recommended algorithms. Hardware based random-number
14 generators (RNG) can be used on platforms with appropriate hardware support.
15 Platforms without hardware RNG support shall use the `CTR-DRBG algorithm
55 enables a random number generator that uses the enabled hardware
77 hardware random generator driver
|
