Home
last modified time | relevance | path

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

123

/linux/Documentation/driver-api/gpio/
H A Ddrivers-on-gpio.rst42 the system by pulling a GPIO line and will register a restart handler so
46 system down by pulling a GPIO line and will register a pm_power_off()
75 regulator providing a certain voltage by pulling a GPIO line, integrating
/linux/mm/
H A Dpage_reporting.h30 * threshold then it will start the process of pulling some pages and
/linux/arch/hexagon/kernel/
H A Dvmlinux.lds.S11 #include <asm/cache.h> /* and now we're pulling cache line size */
/linux/Documentation/devicetree/bindings/input/
H A Dcypress,tm2-touchkey.yaml43 e.g. for pulling up the interrupt line or the I2C pins.
/linux/Documentation/w1/masters/
H A Dw1-uart.rst28 pulling the line low, which is used by the driver to evaluate the result of
/linux/net/sched/
H A Dsch_multiq.c101 * pulling an skb to avoid head-of-line blocking. in multiq_dequeue()
133 * pulling an skb to avoid head-of-line blocking. in multiq_peek()
/linux/Documentation/leds/
H A Dleds-lm3556.rst24 or by pulling the STROBE pin HIGH.
/linux/drivers/scsi/aacraid/
H A Ddpcsup.c50 * Keep pulling response QEs off the response queue and waking in aac_response_normal()
167 * Keep pulling response QEs off the response queue and waking in aac_command_normal()
/linux/drivers/clk/ux500/
H A Dreset-prcc.c29 * the reset by pulling the line low. SET take the device out of
/linux/Documentation/i2c/
H A Dgpio-fault-injection.rst100 test and then pulling SDA low for some time. So, the I2C address sent out
/linux/Documentation/w1/
H A Dw1-generic.rst8 Devices communicate on the bus by pulling the signal to ground via an open
/linux/tools/testing/selftests/drivers/sdsi/
H A Dsdsi_test.py190 # Short wait needed to allow file to close before pulling driver
/linux/Documentation/maintainer/
H A Drebasing-and-merging.rst127 requests, and upstream maintainers should verify the tags when pulling
/linux/net/bluetooth/
H A Daf_bluetooth.c515 /* Pulling partial data */ in bt_sock_stream_recvmsg()
521 /* Pulling all frag data */ in bt_sock_stream_recvmsg()
/linux/Documentation/doc-guide/
H A Dcontributing.rst158 Note that the most value comes from pulling in the documentation for
/linux/arch/arm/kernel/
H A Dentry-header.S211 @ IRQs off again before pulling preserved data off the stack
/linux/arch/arm/boot/dts/samsung/
H A Dexynos5250-spring.dts361 * double-pulling gets us out of spec in some cases.
H A Dexynos5250-snow-common.dtsi452 * double-pulling gets us out of spec in some cases.
/linux/drivers/gpio/
H A Dgpio-pcf857x.c354 * the '75c doesn't have a current source pulling high. in pcf857x_probe()
/linux/tools/tracing/rtla/src/
H A Dtimerlat_top.c532 err_msg("Error pulling BPF data\n"); in timerlat_top_bpf_main_loop()
/linux/drivers/comedi/drivers/
H A Ddas16m1.c25 * pulling the data across the ISA bus. I timed the interrupt handler, and it
H A Dpcmuio.c209 * effectively pulling it low.
/linux/drivers/net/wireguard/
H A Dreceive.c283 /* Another ugly situation of pushing and pulling the header so as to in decrypt_packet()
/linux/drivers/md/bcache/
H A Dalloc.c531 * The ideas is if you've got multiple tasks pulling data into the cache at the
/linux/drivers/mtd/nand/raw/
H A Dmtk_nand.c625 * 31:28: tpoecs, minimum required time for CS post pulling down after in mtk_nfc_setup_interface()
627 * 27:22: tprecs, minimum required time for CS pre pulling down before in mtk_nfc_setup_interface()

123