Searched refs:hardware (Results 1 – 25 of 1056) sorted by relevance
12345678910>>...43
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 the42 If a hardware watchdog is configured as a fallback for the task47 int "Additional delay for hardware watchdog (ms)"52 The timeout of the hardware watchdog fallback will be increased by57 between different clock sources for the hardware watchdog and the58 kernel timer. This is especially important if the hardware watchdog
12 * Use devicetree to describe **hardware** and its **boot-time configuration**.19 In other words, devicetree mainly deals with hardware, and Kconfig with25 * The fact that the board has this UART **hardware** is described with two UART27 property) and certain settings such as the address range of the hardware41 * Devicetree should be used to describe the presence of the radio **hardware**,51 :ref:`status <dt-important-props>` keyword on the corresponding hardware59 specific to Zephyr drivers and not hardware description or configuration these64 instance of a hardware device to be used for a particular purpose. An example
7 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
7 hardware. The `Devicetree specification`_ defines its source and binary14 - the hardware available on its :ref:`boards`15 - that hardware's initial configuration17 As such, devicetree is both a hardware description language and a configuration
126 const char *hardware; member137 const char *hardware; member209 hardware, JSON_TOK_STRING),227 hardware, JSON_TOK_STRING),
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
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 and49 Describes controller hardware scrambling capability and
9 multiple software and hardware platforms.11 These sections describe the software and hardware abstraction layers
23 hardware to make them ready for thread mode consumers.32 buffer goes below this number hardware entropy generation will be41 hardware to make them ready for ISR consumers.50 buffer goes below this number hardware entropy generation will be
40 hardware to make them ready for thread mode consumers.49 buffer goes below this number hardware entropy generation will be58 hardware to make them ready for ISR consumers.67 buffer goes below this number hardware entropy generation will be
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 and62 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-dk109 .. _nRF5340 Audio DK hardware guide: https://docs.nordicsemi.com/bundle/ug_nrf5340_audio/page/UG/nr…
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 the68 hardware you might want to change this option in the same way as Interrupt77 configuration would not boot on your hardware. In this case you need to update100 - 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 that169 Zephyr xenvm image on new hardware.
16 with an actual nRF51 Microbit hardware system, or any other hardware system.23 The following hardware features are supported:37 The kernel currently does not support other hardware features on this platform.57 * Writing to the hardware's flash memory
23 message(WARNING "You appear to be using the GPT hardware timer. "25 "hardware timer resolution")
548 def _create_command(self, runner, hardware): argument567 board_id = hardware.probe_id or hardware.id568 product = hardware.product602 if hardware.runner_params:603 for param in hardware.runner_params:670 hardware = None672 hardware = self.device_is_available(self.instance)674 while not hardware:679 hardware = self.device_is_available(self.instance)684 return hardware[all …]
26 # hardware45 # hardware47 …pytest --twister-harness --device-type=hardware --device-serial=/dev/ttyACM0 --build-dir=build -p …
11 This driver supports SHA256 hardware accelerator of the it8xxx2 series.22 This driver supports SHA256 hardware accelerator of the it82xx2 series.
11 All software for the nRF54L09 SoC is experimental and hardware availability14 The nRF54L09 Preview Development Kit hardware provides39 The ``nrf54l09pdk/nrf54l09/cpuapp`` board target supports the following hardware features:57 Other hardware features have not been enabled yet for this board.
30 Supported hardware33 Although the stack itself is hardware independent, Ethernet frame timestamping44 due to lack of hardware clock)45 - :zephyr:board:`qemu_x86` (emulated, limited capabilities due to lack of hardware clock)
11 All software for the nRF54L20 SoC is experimental and hardware availability14 The nRF54L20 Preview Development Kit hardware provides40 hardware features:58 Other hardware features have not been enabled yet for this board.
41 #. Initialize the hardware, including but not limited to:43 * Check :c:struct:`mspi_cfg` against hardware's own capabilities to prevent50 * Power on the hardware.52 * Configure the hardware using :c:struct:`mspi_cfg` and possibly more57 to re-initialize the hardware with new parameters during runtime.65 #. Call :c:func:`mspi_dev_config` with device specific hardware settings obtained79 #. Call API for additional setups if supported by hardware104 In which case that a controller supports hardware command queue, user could take full105 advantage of the hardware performance if scatter IO and callback management are supported151 mspi-hardware-ce-num = < 0x0 >;[all …]
11 All software for the Ganymed Break-Out-Board (BOB) is experimental and hardware availability14 The Ganymed board hardware provides support for the Ganymed sy1xx series IoT multicore71 The ``ganymed-bob/sy120-gbm`` board supports the following hardware features:103 Other hardware features have not been enabled yet for this board.105 The ``ganymed-bob/sy120-gen1`` board includes all hardware features of the ``ganymed-bob/sy120-gbm`…120 Other hardware features have not been enabled yet for this board.
17 with an actual ZCU102 hardware system, or any other hardware system.24 The following hardware features are supported:37 The kernel currently does not support other hardware features on this platform.
17 with an actual MIPS Malta hardware system, or any other hardware system.25 The following hardware features are supported:38 The kernel currently does not support other hardware features on this platform.
20 * 1.0 GHz Arm Cortex-R52 core (hardware Lock step is supported);21 * two 400MHz G4MH cores (hardware Lock step is supported);39 hardware features:51 Other hardware features have not been enabled yet for this board.
