Home
last modified time | relevance | path

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

12

/Documentation/devicetree/bindings/iio/pressure/
Dhoperf,hp03.yaml24 The XCLR pin is a reset of the ADC in the chip, it must be pulled
26 registers and pulled LO afterward.
/Documentation/devicetree/bindings/iio/light/
Dveml6030.yaml34 - 0x10 # ADDR pin pulled down
35 - 0x48 # ADDR pin pulled up
/Documentation/devicetree/bindings/sound/
Deverest,es7241.yaml33 the sdout. If the sdout is pulled down, leftj format is used.
34 If this property is not provided, sdout is assumed to pulled
/Documentation/devicetree/bindings/gpio/
Dgpio-max3191x.txt31 pulled high (8-bit mode). Use this if the modesel pin
35 that modesel is pulled low (16-bit mode).
Dnxp,pcf8575.yaml60 the input (pulled-up) state.
/Documentation/dev-tools/
Dindex.rst6 be used to work on the kernel. For now, the documents have been pulled
/Documentation/devicetree/bindings/iio/dac/
Dti,dac7612.yaml29 DACs are loaded when the pin connected to this GPIO is pulled low.
Dadi,ad5592r.yaml104 * CH_OFFSTATE_PULLDOWN (the pin is pulled down)
/Documentation/devicetree/bindings/extcon/
Dqcom,pm8941-misc.yaml14 the USB ID pin has been pulled low or high.
/Documentation/fb/
Dmetronomefb.rst17 The display and error status are each pulled through individual GPIOs.
/Documentation/devicetree/bindings/mfd/
Dsamsung,s2mps11.yaml49 power. Usually the ACOKB is pulled up to VBATT so when PWRHOLD pin goes
55 Indicates that WRSTBI pin of PMIC is pulled down. When the system is
Dtps6507x.txt29 0: If defdcdc pin of DCDC2/DCDC3 is pulled to GND.
/Documentation/process/
D7.AdvancedTopics.rst53 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:
/Documentation/maintainer/
Drebasing-and-merging.rst49 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
Dpull-requests.rst136 against (to show the correct changes to be pulled and the diffstat). The
152 asking to be pulled from, git will complain saying it is not there,
Dmaintainer-entry-profile.rst30 - Git branches that are pulled into -next?
Dmessy-diffstat.rst77 to be pulled into, but to do it privately, as if it were the source of
/Documentation/devicetree/bindings/usb/
Dsamsung,exynos-usb2.yaml44 needs to be pulled up for the bus to be powered.
/Documentation/devicetree/bindings/leds/
Dkinetic,ktd2692.yaml20 Also, When the AUX pin is pulled high while CTRL pin is high,
/Documentation/scsi/
Dlpfc.rst32 received from the midlayer. In the cases where a cable was pulled, link
DChangeLog.sym53c8xx_233 - Check against GPIO3 pulled low for HVD controllers (driver did
/Documentation/power/
Dcharger-manager.rst199 At the charger/battery-related events such as battery-pulled-out,
200 charger-pulled-out, charger-inserted, DCIN-over/under-voltage, charger-stopped,
/Documentation/arch/arm/nwfpe/
Dtodo.rst59 pulled out from some docs on ARM floating point, specifically
/Documentation/devicetree/bindings/iio/resolver/
Dadi,ad2s1210.yaml113 the type of fault present, if any. As these pins a pulled low to indicate
/Documentation/doc-guide/
Dcontributing.rst149 many of those comments are never pulled into the docs build. That makes
160 kerneldoc comments for internal use; those should not be pulled into the

12