Searched refs:pulled (Results 1 – 25 of 54) sorted by relevance
123
| /Linux-v5.10/Documentation/devicetree/bindings/iio/pressure/ |
| D | hp03.txt | 7 it must be pulled HI before the conversion and
9 pulled LO afterward.
|
| /Linux-v5.10/Documentation/devicetree/bindings/sound/ |
| D | everest,es7241.txt | 15 the sdout. If the sdout is pulled down, leftj format is used.
16 If this property is not provided, sdout is assumed to pulled
|
| /Linux-v5.10/drivers/net/ethernet/intel/fm10k/ |
| D | fm10k_mbx.c | 349 end = fm10k_fifo_head_offset(fifo, mbx->pulled); in fm10k_mbx_write_copy()
389 mbx->pulled += mbx->tail_len - ack; in fm10k_mbx_pull_head()
393 len = fm10k_fifo_used(fifo) - mbx->pulled; in fm10k_mbx_pull_head()
403 len && (mbx->pulled >= len); in fm10k_mbx_pull_head()
405 mbx->pulled -= fm10k_fifo_head_drop(fifo); in fm10k_mbx_pull_head()
622 head = fm10k_fifo_head_offset(&mbx->tx, mbx->pulled); in fm10k_mbx_update_local_crc()
863 crc = fm10k_fifo_crc(fifo, fm10k_fifo_head_offset(fifo, mbx->pulled), in fm10k_mbx_create_data_hdr()
1067 mbx->pulled += mbx->tail_len - ack; in fm10k_mbx_reset_work()
1070 while (fm10k_fifo_head_len(&mbx->tx) && mbx->pulled) { in fm10k_mbx_reset_work()
1073 if (mbx->pulled >= len) in fm10k_mbx_reset_work()
[all …]
|
| D | fm10k_mbx.h | 266 u16 tail, tail_len, pulled; member
|
| /Linux-v5.10/Documentation/devicetree/bindings/gpio/ |
| D | gpio-max3191x.txt | 31 pulled high (8-bit mode). Use this if the modesel pin
35 that modesel is pulled low (16-bit mode).
|
| D | gpio-pcf857x.txt | 40 the input (pulled-up) state. When the bit is set to one, the line will be
|
| /Linux-v5.10/Documentation/devicetree/bindings/mfd/ |
| D | samsung,sec-core.txt | 35 - samsung,s2mps11-wrstbi-ground: Indicates that WRSTBI pin of PMIC is pulled
40 register to turn off the power. Usually the ACOKB is pulled up to VBATT so
|
| D | tps6507x.txt | 29 0: If defdcdc pin of DCDC2/DCDC3 is pulled to GND.
|
| /Linux-v5.10/Documentation/dev-tools/ |
| D | index.rst | 6 be used to work on the kernel. For now, the documents have been pulled
|
| /Linux-v5.10/arch/powerpc/boot/dts/fsl/ |
| D | p1023rdb.dts | 186 /* IRQ[0:3] are pulled up on board, set to active-low */
212 * IRQ[7] is pulled up on board, set to active-low
238 * IRQ[8:10] are pulled up on board, set to active-low
|
| /Linux-v5.10/Documentation/devicetree/bindings/extcon/ |
| D | qcom,pm8941-misc.txt | 4 the USB ID pin has been pulled low or high.
|
| /Linux-v5.10/Documentation/devicetree/bindings/iio/dac/ |
| D | ti,dac7612.txt | 7 The internal DACs are loaded when the LOADDACS pin is pulled down.
|
| D | ad5592r.txt | 41 * CH_OFFSTATE_PULLDOWN (the pin is pulled down)
|
| /Linux-v5.10/Documentation/devicetree/bindings/leds/ |
| D | leds-ktd2692.txt | 10 Also, When the AUX pin is pulled high while CTRL pin is high,
|
| /Linux-v5.10/arch/arm/boot/dts/ |
| D | pxa3xx.dtsi | 88 * the configured driven and pulled levels match, so if there is a need for
89 * non-LPM pulled output, the same configuration could probably be used.
|
| D | am335x-bonegreen-wireless.dts | 112 /* BT_AUD_OUT from wl1835 has to be pulled low when WL_EN is activated.*/
|
| D | sun4i-a10-pcduino2.dts | 47 * is controlled by the PD2 pin (pulled-up by default). Also one of
|
| D | stm32mp15xx-dhcom-drc02.dtsi | 59 * pulled high in order to be detected by the USB Controller.
|
| /Linux-v5.10/Documentation/devicetree/bindings/net/wireless/ |
| D | mediatek,mt76.txt | 30 data should be pulled from the OTP ROM
|
| /Linux-v5.10/tools/power/pm-graph/config/ |
| D | custom-timeline-functions.cfg | 78 # The args are pulled directly from the stack using this architecture's registers
143 # The args are pulled directly from the stack using this architecture's registers
|
| /Linux-v5.10/Documentation/fb/ |
| D | metronomefb.rst | 17 The display and error status are each pulled through individual GPIOs.
|
| /Linux-v5.10/Documentation/process/ |
| D | 7.AdvancedTopics.rst | 53 will, of course, need a server that can be pulled from. Setting up such a
85 have pulled into their repositories, you will make life much more difficult
119 can affect your ability to get trees pulled in the future. Quoting Linus:
|
| /Linux-v5.10/Documentation/devicetree/bindings/usb/ |
| D | exynos-usb.txt | 23 needs to be pulled up for the bus to be powered.
|
| /Linux-v5.10/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 49 should usually not be changed. Others may have pulled a copy of your
62 have pulled changes from another developer's repository, you are now a
197 tree fails to be pulled upstream, whatever problems it had will block the
|
| /Linux-v5.10/Documentation/scsi/ |
| D | lpfc.rst | 32 received from the midlayer. In the cases where a cable was pulled, link
|
123
