Home
last modified time | relevance | path

Searched full:actively (Results 1 – 25 of 25) sorted by relevance

/Zephyr-Core-3.5.0/dts/bindings/pinctrl/
Dpincfg-node.yaml45 description: drive actively high and low
105 enable output on a pin without actively driving it (e.g. enable an output
Datmel,sam0-pinctrl.yaml64 - output-enable: Enable output on a pin without actively driving it.
/Zephyr-Core-3.5.0/arch/posix/
DLinux.aarch64.cmake3 # For Aarch64, multilib is not an actively pursued solution for most Linux
/Zephyr-Core-3.5.0/dts/bindings/pwm/
Dti,cc13xx-cc26xx-timer-pwm.yaml27 output and actively driven by the PWM driver.
/Zephyr-Core-3.5.0/dts/bindings/can/
Dcan-controller.yaml53 Actively controlled CAN transceiver.
/Zephyr-Core-3.5.0/soc/arm/ambiq/apollo4x/
Dpinctrl_soc.h26 /** Drive actively high or low */
/Zephyr-Core-3.5.0/subsys/net/ip/
DKconfig.debug44 any means, unless you are actively debugging.
/Zephyr-Core-3.5.0/drivers/power_domain/
Dpower_domain_gpio.c96 /* Actively control the enable pin now that the device is powered */ in pd_gpio_pm_action()
/Zephyr-Core-3.5.0/doc/connectivity/networking/api/
Dlwm2m.rst611 - Used only in queue mode, not actively listening for incoming packets.
612 In queue mode the client is not required to actively listen for the incoming packets
/Zephyr-Core-3.5.0/doc/kernel/services/
Dpolling.rst21 conditions to be fulfilled without actively looking at each one individually.
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/
Dl2cap-pics.rst67 TSPC_L2CAP_2_24 False Actively request Basic Mode for a PSM that supports the use of ERTM or St…
/Zephyr-Core-3.5.0/drivers/ps2/
Dps2_mchp_xec.c161 * is because the channel may be actively receiving data. in ps2_xec_write()
/Zephyr-Core-3.5.0/include/zephyr/tracing/
Dtracing_macros.h191 * of an API must be actively disabled.
/Zephyr-Core-3.5.0/doc/contribute/
Dexternal.rst65 - Is the external project being actively maintained? This is particularly
/Zephyr-Core-3.5.0/tests/arch/riscv/fpu_sharing/src/
Dmain.c161 * it anymore afterwards as we didn't actively used it this time. in thread1_entry()
/Zephyr-Core-3.5.0/drivers/serial/
Duart_cc13xx_cc26xx.c420 * actively powered down in postNotifyFxn()
/Zephyr-Core-3.5.0/doc/build/dts/
Dintro-syntax-structure.rst310 the :c:macro:`DT_LABEL` macro in new code, are actively discouraged. Label
/Zephyr-Core-3.5.0/include/zephyr/pm/
Ddevice.h388 * to the suspended state, or actively put the device into the suspended state.
/Zephyr-Core-3.5.0/doc/connectivity/usb/device/
Dusb_device.rst30 one USB device configuration. We are actively working on new USB support, which
/Zephyr-Core-3.5.0/doc/kernel/services/threads/
Dworkqueue.rst174 a dedicated thread waiting or actively polling for a poll event.
/Zephyr-Core-3.5.0/doc/releases/
Drelease-notes-1.7.rst33 actively polling them, but rather pending for one or more to become ready.
Drelease-notes-2.6.rst1414 * :github:`34206` - Question: Is zephyrproject actively maintaining the windows-curses sub-project?
/Zephyr-Core-3.5.0/tests/arch/arm/arm_thread_swap/src/
Darm_thread_arch.c486 /* The main test thread is not (yet) actively using the FP registers */ in ZTEST()
/Zephyr-Core-3.5.0/subsys/usb/device/
Dusb_device.c1517 * The class does not actively engage in request in custom_handler()
/Zephyr-Core-3.5.0/include/zephyr/bluetooth/audio/
Dbap.h1954 * is actively scanning for broadcast sources.