Home
last modified time | relevance | path

Searched refs:has (Results 351 – 375 of 1361) sorted by relevance

1...<<11121314151617181920>>...55

/Zephyr-latest/subsys/bluetooth/audio/
DKconfig45 rsource "Kconfig.has"
/Zephyr-latest/boards/google/quincy/doc/
Dindex.rst9 The board has connectors for fingerprint sensors. A UART Console is exposed
/Zephyr-latest/boards/beagle/beagleplay/
Dbeagleplay_cc1352p7.dts43 * The BeaglePlay cc1352 has an on-board antenna switch (SKY13317-373LF) used to
/Zephyr-latest/cmake/
Dverify-toolchain.cmake1 # The purpose of this file is to verify that required variables has been
Dyaml-filter.cmake6 # YAML needs to happen after cmake has completed processing.
/Zephyr-latest/samples/drivers/spi_bitbang/
DREADME.rst20 The application will build only for a target that has a :ref:`devicetree
/Zephyr-latest/samples/net/sockets/sntp_client/
DREADME.rst13 This demo assumes that the platform of choice has networking support,
/Zephyr-latest/samples/drivers/charger/
DREADME.rst19 - Once the charger device reports that the charge cycle has completed, the application returns.
/Zephyr-latest/samples/sensor/lsm6dso/
DREADME.rst18 It has been tested on the :zephyr:board:`stm32l562e_dk`.
/Zephyr-latest/samples/sensor/tmp108/
DKconfig17 One shot requires a callback to be invoked after the tmp108 has
/Zephyr-latest/boards/nxp/mimxrt1050_evk/doc/
Dindex.rst13 and camera sensors. As with other i.MX processors, i.MX RT1050 also has rich
81 This platform has the following external memories:
148 The MIMXRT1050 SoC has five pairs of pinmux/gpio controllers.
290 The MIMXRT1050 SoC has eight UARTs. ``LPUART1`` is configured for the console,
297 The RT1050 SoC has two USB OTG (USBOTG) controllers that supports both
304 This board has two variants that can be targeted,
309 * ``mimxrt1050_evk/mimxrt1052/qspi`` is for a board that has been reworked to use the
/Zephyr-latest/doc/kernel/usermode/
Dkernelobjects.rst27 has sufficient permissions to work with it.
29 Permission on an object also has the semantics of a reference to an object.
35 * If the object has an associated cleanup function, the cleanup function
119 :c:struct:`z_object`, which has all the metadata for that object. This
124 bitfield for an object to see if that thread has permission on it. The size
163 * A thread that has permission on an object, or is running in supervisor mode,
183 Once a thread has been granted access to an object, such access may be
/Zephyr-latest/doc/hardware/peripherals/
Di3c.rst105 the stated static address if ``SETDASA`` has not been
151 * If the hardware has IBI slots, :c:func:`i3c_ibi_enable`
213 For I3C devices, the ``reg`` property has 3 elements:
241 For I\ :sup:`2`\ C devices where the device driver has support for
247 has 3 elements:
266 * I3C device has a 50 ns spike filter where it is not
308 device driver implements the I2C API. This has the advantage of using
/Zephyr-latest/doc/connectivity/networking/api/
Dptp.rst17 for Networked Measurement and Control Systems). It has multiple profiles,
129 The stack has been informally tested using the
/Zephyr-latest/boards/01space/esp32c3_042_oled/doc/
Dindex.rst31 The ESP32-C3 does not have native USB, it has an on-chip USB-serial converter
125 After the board has automatically reset and booted, you should see the following
/Zephyr-latest/drivers/ieee802154/
DKconfig23 When all configurations are done net_if_up() has to be invoked to
51 as this option has no default value.
/Zephyr-latest/boards/peregrine/sam4l_wm400_cape/doc/
Dindex.rst48 The ATSAM4LC4B MCU has 4 USARTs. One of the USARTs (USART3) is shared between
55 The SAM4L WM-400 Cape board has a 10-pin header to connect to a Segger JLink.
/Zephyr-latest/boards/native/nrf_bsim/doc/
Dnrf54l15bsim.rst20 run applications natively on the development system. This has the benefit of
30 Unlike real nRF54L15 devices, the nrf54l15bsim target has unlimited RAM, and code does not
/Zephyr-latest/boards/st/steval_fcu001v1/doc/
Dindex.rst63 The steval_fcu001v1 board has one UART. The Zephyr console output is assigned to UART1.
69 The steval_fcu001v1 board has one I2C. The default I2C mapping for Zephyr is:
/Zephyr-latest/doc/hardware/cache/
Dindex.rst9 Zephyr has different Kconfig options to control how the cache controller is
46 in memory that will have caching disabled once the kernel has initialized.
/Zephyr-latest/dts/arm/nxp/
Dnxp_rt1060.dtsi33 /* i.MX rt1060 has a second Ethernet controller. */
61 /* RT1060 has a dedicated OCRAM region */
/Zephyr-latest/drivers/eeprom/
DKconfig22 priority is used unless the driver implementation has its own
93 The EEPROM is connected to I2C or SPI bus an has to be initialized
/Zephyr-latest/doc/kernel/services/smp/
Dsmp.rst36 At the lowest level, however, Zephyr code has often used the
50 also atomically validates that a shared lock variable has been
73 Zephyr core kernel has now been ported to use spinlocks exclusively.
89 The overhead involved in this process has measurable performance
178 thread becomes runnable, the idle CPU has no way to "wake up" to
255 kernel to generate cascading IPIs until the kernel has selected a valid set of
286 within the :c:struct:`_kernel` struct, which has a ``cpus[]`` array indexed by ID.
309 The traditional Zephyr context switch primitive has been :c:func:`z_swap`.
311 switch to. The expectation has always been that the scheduler has
351 "switch_handle" field after its context has fully been saved.
/Zephyr-latest/doc/kernel/services/data_passing/
Dmessage_queues.rst20 A message queue has the following key properties:
41 it is given to the highest priority sending thread that has waited the longest.
51 the highest priority receiving thread that has waited the longest.
95 The following code has the same effect as the code segment above. Observe
/Zephyr-latest/soc/
DKconfig.v26 # SoCs that has transitioned to SoC scheme v2 are promptless, and thus

1...<<11121314151617181920>>...55