Home
last modified time | relevance | path

Searched refs:hardware (Results 1 – 25 of 847) sorted by relevance

12345678910>>...34

/Zephyr-Core-3.5.0/subsys/task_wdt/
DKconfig13 per thread, even if the hardware supports only a single watchdog.
25 bool "Use hardware watchdog as a fallback"
29 This option allows to specify a hardware watchdog device in the
43 If a hardware watchdog is configured as a fallback for the task
48 int "Additional delay for hardware watchdog (ms)"
53 The timeout of the hardware watchdog fallback will be increased by
58 between different clock sources for the hardware watchdog and the
59 kernel timer. This is especially important if the hardware watchdog
/Zephyr-Core-3.5.0/boards/arm/am62x_m4/doc/
Dindex.rst13 Currently the following hardware platforms are supported:
24 The AM62x M4F platform supports the following hardware features:
38 Other hardware features are not currently supported by the port.
/Zephyr-Core-3.5.0/subsys/logging/backends/
DKconfig.adsp_hda10 periodically flushes to hardware using ringbuffer like
26 The period of time is decided by how often to inform the hardware of
30 int "Time in milliseconds to periodically flush writes to hardware"
35 to hardware by informing the DMA hardware the contents of the ring
/Zephyr-Core-3.5.0/doc/build/dts/
Ddt-vs-kconfig.rst12 * 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
Dindex.rst7 hardware. Zephyr uses devicetree in two main ways:
9 - to describe hardware to the :ref:`device_model_api`
10 - to provide that hardware's initial configuration
Dintro-scope-purpose.rst7 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-Core-3.5.0/subsys/mgmt/updatehub/
Dupdatehub_priv.h121 const char *hardware; member
132 const char *hardware; member
197 hardware, JSON_TOK_STRING),
215 hardware, JSON_TOK_STRING),
/Zephyr-Core-3.5.0/drivers/dma/
DKconfig.dw_common20 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-Core-3.5.0/doc/services/portability/
Dindex.rst9 multiple software and hardware platforms.
11 These sections describe the software and hardware abstraction layers
/Zephyr-Core-3.5.0/drivers/entropy/
DKconfig.smartbond23 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
DKconfig.nrf540 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
DKconfig.stm3226 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-Core-3.5.0/scripts/pylib/twister/twisterlib/
Dhandlers.py470 def _create_command(self, runner, hardware): argument
489 board_id = hardware.probe_id or hardware.id
490 product = hardware.product
510 if hardware.runner_params:
511 for param in hardware.runner_params:
567 hardware = None
569 hardware = self.device_is_available(self.instance)
570 while not hardware:
572 hardware = self.device_is_available(self.instance)
577 return hardware
[all …]
Dharness.py307 hardware = handler.get_hardware()
308 if not hardware:
311 self.reserved_serial = hardware.serial_pty or hardware.serial
312 if hardware.serial_pty:
321 if runner := hardware.runner or options.west_runner:
327 if board_id := hardware.probe_id or hardware.id:
330 if hardware.product:
333 if hardware.pre_script:
336 if hardware.post_flash_script:
339 if hardware.post_script:
/Zephyr-Core-3.5.0/boards/arm64/xenvm/doc/
Dindex.rst23 The following hardware features are supported:
33 The kernel currently does not support other hardware features on this platform.
47 default value, which should be corrected for user's actual hardware.
59 Depending on the version of the GIC on your hardware, you may choose one of the
69 hardware you might want to change this option in the same way as Interrupt
78 configuration would not boot on your hardware. In this case you need to update
99 - if your hardware is based on GICv2:
105 - if your hardware is based on GICv3:
161 As was said earlier, Xen describes hardware using device tree and expects that
168 Zephyr xenvm image on new hardware.
/Zephyr-Core-3.5.0/scripts/pylib/pytest-twister-harness/
DREADME.rst26 # hardware
45 # hardware
47 …pytest --twister-harness --device-type=hardware --device-serial=/dev/ttyACM0 --build-dir=build -p …
/Zephyr-Core-3.5.0/boards/arm/qemu_cortex_m0/doc/
Dindex.rst19 with an actual nRF51 Microbit hardware system, or any other hardware system.
26 The following hardware features are supported:
40 The kernel currently does not support other hardware features on this platform.
60 * Writing to the hardware's flash memory
/Zephyr-Core-3.5.0/doc/connectivity/networking/api/
Dgptp.rst30 Supported hardware
33 Although the stack itself is hardware independent, Ethernet frame timestamping
44 due to lack of hardware clock)
45 - :ref:`qemu_x86` (emulated, limited capabilities due to lack of hardware clock)
/Zephyr-Core-3.5.0/boards/arm/vmu_rt1170/
DCMakeLists.txt23 message(WARNING "You appear to be using the GPT hardware timer. "
25 "hardware timer resolution")
/Zephyr-Core-3.5.0/boards/arm/qemu_cortex_r5/doc/
Dindex.rst20 with an actual ZCU102 hardware system, or any other hardware system.
27 The following hardware features are supported:
40 The kernel currently does not support other hardware features on this platform.
/Zephyr-Core-3.5.0/samples/basic/blinky_pwm/
DREADME.rst18 Some PWM hardware cannot set the PWM period to 1 second to achieve the blinking
19 frequency of 1 Hz. This sample calibrates itself to what the hardware supports
21 supported by the hardware is found.
34 No additional wiring is necessary if ``pwm_led0`` refers to hardware that is
/Zephyr-Core-3.5.0/boards/mips/qemu_malta/doc/
Dindex.rst20 with an actual MIPS Malta hardware system, or any other hardware system.
28 The following hardware features are supported:
41 The kernel currently does not support other hardware features on this platform.
/Zephyr-Core-3.5.0/boards/arm/qemu_cortex_m3/doc/
Dindex.rst19 with an actual ti_lm3s6965 hardware system, or any other hardware system.
26 The following hardware features are supported:
40 The kernel currently does not support other hardware features on this platform.
66 * Writing to the hardware's flash memory
/Zephyr-Core-3.5.0/samples/net/zperf/boards/
Dmimxrt1050_evk.overlay7 /* Use cortex systick as hardware timer */
Dmimxrt1060_evk.overlay7 /* Use cortex systick as hardware timer */

12345678910>>...34