Home
last modified time | relevance | path

Searched refs:level (Results 776 – 800 of 843) sorted by relevance

1...<<31323334

/Zephyr-4.1.0/
DCMakeLists.txt5 # Note that this is *NOT* the top-level CMakeLists.txt. That's in the
192 # Kconfig.zephyr "Optimization level" is a kconfig choice, ensuring
223 "Unreachable code. Expected optimization level to have been chosen. See Kconfig.zephyr")
730 # on directory level.
763 # when using depend on directory level.
/Zephyr-4.1.0/doc/releases/
Drelease-notes-2.2.rst99 - GPIO_ACTIVE_LOW, GPIO_ACTIVE_HIGH used to set pin active level
104 * Reading / writing of pin logical level is supported by gpio_pin_get,
106 * Reading / writing of pin physical level is supported by gpio_pin_get_raw,
133 were reworked to honor pin active level. Any external users of these
799 * :github:`22660` - gpio: legacy level interrupt disable API not backwards compatible
Drelease-notes-3.0.rst451 * mimxrt11xx: Added SOC level power management
597 * Enabled level triggered interrupts in LIS2DH driver.
671 * IPSO Filling level (ID 3435)
1290 * :github:`39269` - Fail to initialize BLE stack with optimization level zero
1325 * :github:`23052` - nrf52840_pca10056: Spurious RTS pulse and incorrect line level with hardware fl…
Drelease-notes-1.11.rst12 * Thread-level memory protection on x86, ARC and Arm, userspace and memory
223 * :github:`2937` - Thread-level Memory Protection Support
Drelease-notes-1.14.rst203 * :github:`17979` - Security level cannot be elevated after re-connection with privacy
407 * :github:`17979` - Security level cannot be elevated after re-connection with privacy
607 * High-level Kconfig symbol structure for Trusted Execution
892 * Fixed security level 4 handling
1146 * :github:`15213` - cmake infrastructure in code missing file level license identifiers
1215 * :github:`14974` - Kconfig.modules needs to be at the top level build folder
1659 …766` - drivers: gpio: stm32: implementation silently ignores attempts to configure level interrupts
1662 * :github:`12763` - drivers: gpio: sch: implementation does not configure interrupt level/edge
1820 * :github:`11806` - gpio_nrf mishandles level interrupts
2254 * :github:`5603` - Bluetooth logging is hardcoded with level 4 (debug)
Drelease-notes-2.3.rst133 * See :ref:`dt-from-c` for a high-level guide to the new API, and
235 * Refactored Cortex-R interrupt system to remove fake multi-level interrupt
891 * :github:`25141` - Cannot use C++ on APPLICATION level initialization
1343 * :github:`18085` - I2C log level ignored
1436 * :github:`6648` - Trusted Execution Framework: practical use-cases (high-level overview)
Drelease-notes-1.13.rst54 * arch: arm: Set Zero Latency IRQ to priority level zero
604 * :github:`7595` - Promiscuous mode and receiving all packets at applications level
634 * :github:`6730` - ARMv8-M: internal low-level (TrustZone) API & implementation for configuring IRQ…
Drelease-notes-1.10.rst12 * Initial alpha-quality thread-level memory protection on x86, userspace and memory
27 * Initial alpha-quality thread-level memory protection on x86, userspace and memory
/Zephyr-4.1.0/drivers/wifi/nrf_wifi/
DKconfig.nrfwifi161 module-str = Log level for Wi-Fi nRF70 driver
162 module-help = Sets log level for Wi-Fi nRF70 driver
/Zephyr-4.1.0/drivers/usb_c/tcpc/
Ducpd_numaker.c2251 bool numaker_tcpc_vbus_check_level(const struct device *dev, enum tc_vbus_level level) in numaker_tcpc_vbus_check_level() argument
2260 switch (level) { in numaker_tcpc_vbus_check_level()
/Zephyr-4.1.0/doc/connectivity/usb/device/
Dusb_device.rst331 is already described at the board level, application devicetree overlay must also
536 : (Defined at Interface level) (00/00/00)
/Zephyr-4.1.0/boards/udoo/udoo_neo_full/doc/
Dindex.rst145 the M4 out of reset. The A9 can perform these steps at the bootloader level
/Zephyr-4.1.0/doc/hardware/peripherals/can/
Dcontroller.rst305 implementation, where many other high-level CAN projects build on top.
/Zephyr-4.1.0/doc/connectivity/usb/device_next/
Dusb_device.rst149 function, and initialize it again. At the USB controller level,
/Zephyr-4.1.0/drivers/modem/
Dhl7800.c1428 uint32_t mdm_hl7800_log_filter_set(uint32_t level) in mdm_hl7800_log_filter_set() argument
1436 level); in mdm_hl7800_log_filter_set()
2461 int mdm_hl7800_set_desired_sleep_level(enum mdm_hl7800_sleep level) in mdm_hl7800_set_desired_sleep_level() argument
2466 switch (level) { in mdm_hl7800_set_desired_sleep_level()
2471 iface_ctx.desired_sleep_level = level; in mdm_hl7800_set_desired_sleep_level()
/Zephyr-4.1.0/doc/hardware/porting/
Dboard_porting.rst276 #. :file:`board.yml`: a YAML file describing the high-level meta data of the
317 The board YAML file describes the board at a high level.
732 - Run ``west flash --help`` and ``west debug --help`` for top-level options
/Zephyr-4.1.0/boards/ezurio/bl5340_dvk/doc/
Dindex.rst153 Refer to the `ER_TFTM028_4 datasheet`_ for a high level overview of the
/Zephyr-4.1.0/doc/develop/west/
Dworkspaces.rst267 and specifies a list of projects all at the same "level"
Dbuilt-in.rst263 - ``west topdir``: print the top level directory of the west workspace
/Zephyr-4.1.0/doc/kernel/usermode/
Dkernelobjects.rst52 * The object must be declared as a top-level global at build time, such that it
/Zephyr-4.1.0/dts/arm/nxp/
Dnxp_s32k344_m7.dtsi35 /* Dummy pinctrl node, filled with pin mux options at board level */
/Zephyr-4.1.0/doc/security/
Dsecure-coding.rst120 shall be notified if low-level options and APIs are enabled but not
/Zephyr-4.1.0/boards/nxp/imx93_evk/doc/
Dindex.rst8 small and low cost package. The MCIMX93-EVK board is an entry-level development
/Zephyr-4.1.0/subsys/net/lib/sockets/
DKconfig398 module-str = Log level for BSD sockets compatible API calls
/Zephyr-4.1.0/soc/intel/intel_adsp/tools/
Dcavstool.py18 logging.basicConfig(level=logging.INFO)

1...<<31323334