Home
last modified time | relevance | path

Searched refs:driving (Results 1 – 25 of 145) sorted by relevance

123456

/linux-6.15/Documentation/devicetree/bindings/pinctrl/
H A Dmediatek,mt8183-pinctrl.yaml120 Describe the specific driving setup property.
121 For I2C pins, the existing generic driving setup can only support
122 2/4/6/8/10/12/14/16mA driving. But in specific driving setup, they
124 driving setup, the existing generic setup will be disabled.
125 The specific driving setup is controlled by E1E0EN.
130 EN is used to enable or disable the specific driving setup.
H A Drealtek,rtd1315e-pinctrl.yaml115 The driving strength of the P-MOS/N-MOS transistors impacts the
116 waveform's rise/fall times. Greater driving strength results in
119 greater driving strength, contributing to achieving the desired
122 The realtek,drive-strength-p is used to control the driving strength
131 is used to control the driving strength of the N-MOS output.
H A Dmediatek,mt8365-pinctrl.yaml124 Describe the specific driving setup property.
125 For I2C pins, the existing generic driving setup can only support
126 2/4/6/8/10/12/14/16mA driving. But in specific driving setup, they
128 driving setup, the existing generic setup will be disabled.
129 The specific driving setup is controlled by E1E0EN.
134 EN is used to enable or disable the specific driving setup.
H A Drealtek,rtd1619b-pinctrl.yaml113 The driving strength of the P-MOS/N-MOS transistors impacts the
114 waveform's rise/fall times. Greater driving strength results in
117 greater driving strength, contributing to achieving the desired
120 The realtek,drive-strength-p is used to control the driving strength
129 is used to control the driving strength of the N-MOS output.
H A Drealtek,rtd1319d-pinctrl.yaml114 The driving strength of the P-MOS/N-MOS transistors impacts the
115 waveform's rise/fall times. Greater driving strength results in
118 greater driving strength, contributing to achieving the desired
121 The realtek,drive-strength-p is used to control the driving strength
130 is used to control the driving strength of the N-MOS output.
H A Dsprd,pinctrl.txt8 pad driving level, system control select and so on ("domain pad
9 driving level": One pin can output 3.0v or 1.8v, depending on the
10 related domain pad driving selection, if the related domain pad
H A Dnuvoton,ma35d1-pinctrl.yaml121 description: 1.8V I/O driving strength
123 description: 3.3V I/O driving strength
/linux-6.15/Documentation/devicetree/bindings/phy/
H A Drealtek,usb2phy.yaml93 usb-dc-cal is the driving level for each phy specified via efuse.
102 realtek,driving-level:
113 realtek,driving-level-compensate:
115 For RTD1315e SoC, the driving level can be adjusted by reading the
159 realtek,driving-level-compensate: false
173 realtek,driving-level = <0xa>;
/linux-6.15/drivers/misc/cardreader/
H A Drts5227.c39 u8 (*driving)[3], drive_sel; in rts5227_fill_driving() local
42 driving = driving_3v3; in rts5227_fill_driving()
45 driving = driving_1v8; in rts5227_fill_driving()
50 0xFF, driving[drive_sel][0]); in rts5227_fill_driving()
52 0xFF, driving[drive_sel][1]); in rts5227_fill_driving()
54 0xFF, driving[drive_sel][2]); in rts5227_fill_driving()
H A Drts5260.c41 u8 (*driving)[3], drive_sel; in rts5260_fill_driving() local
44 driving = driving_3v3; in rts5260_fill_driving()
47 driving = driving_1v8; in rts5260_fill_driving()
52 0xFF, driving[drive_sel][0]); in rts5260_fill_driving()
55 0xFF, driving[drive_sel][1]); in rts5260_fill_driving()
58 0xFF, driving[drive_sel][2]); in rts5260_fill_driving()
H A Drts5228.c41 u8 (*driving)[3], drive_sel; in rts5228_fill_driving() local
44 driving = driving_3v3; in rts5228_fill_driving()
47 driving = driving_1v8; in rts5228_fill_driving()
52 0xFF, driving[drive_sel][0]); in rts5228_fill_driving()
55 0xFF, driving[drive_sel][1]); in rts5228_fill_driving()
58 0xFF, driving[drive_sel][2]); in rts5228_fill_driving()
H A Drts5261.c40 u8 (*driving)[3], drive_sel; in rts5261_fill_driving() local
43 driving = driving_3v3; in rts5261_fill_driving()
46 driving = driving_1v8; in rts5261_fill_driving()
51 0xFF, driving[drive_sel][0]); in rts5261_fill_driving()
54 0xFF, driving[drive_sel][1]); in rts5261_fill_driving()
57 0xFF, driving[drive_sel][2]); in rts5261_fill_driving()
H A Drts5249.c38 u8 (*driving)[3], drive_sel; in rts5249_fill_driving() local
41 driving = driving_3v3; in rts5249_fill_driving()
44 driving = driving_1v8; in rts5249_fill_driving()
49 0xFF, driving[drive_sel][0]); in rts5249_fill_driving()
51 0xFF, driving[drive_sel][1]); in rts5249_fill_driving()
53 0xFF, driving[drive_sel][2]); in rts5249_fill_driving()
H A Drts5264.c39 u8 (*driving)[3], drive_sel; in rts5264_fill_driving() local
42 driving = driving_3v3; in rts5264_fill_driving()
45 driving = driving_1v8; in rts5264_fill_driving()
50 0xFF, driving[drive_sel][0]); in rts5264_fill_driving()
52 0xFF, driving[drive_sel][1]); in rts5264_fill_driving()
54 0xFF, driving[drive_sel][2]); in rts5264_fill_driving()
/linux-6.15/Documentation/devicetree/bindings/media/
H A Dpxa-camera.txt11 - clock-output-names: should contain the name of the clock driving the
13 - clock-frequency: host interface is driving MCLK, and MCLK rate is this rate
/linux-6.15/Documentation/ABI/testing/
H A Dsysfs-bus-i3c53 This entry describes the BCR of the master controller driving
63 This entry describes the DCR of the master controller driving
75 This entry describes the PID of the master controller driving
89 driving the bus.
104 Controller driving the bus.
111 that all devices are represented including the master driving
/linux-6.15/Documentation/devicetree/bindings/power/reset/
H A Dgpio-restart.yaml42 description: Treat the GPIO as being open source and defer driving it to when the restart is
51 description: Delay (default 100) to wait after driving gpio active [ms]
56 description: Delay (default 100) to wait after driving gpio inactive [ms]
H A Dgpio-poweroff.yaml40 description: Delay to wait after driving gpio active
44 description: Delay to wait after driving gpio inactive
/linux-6.15/Documentation/devicetree/bindings/leds/backlight/
H A Drichtek,rt4831-backlight.yaml16 For the LCD backlight, it can provide four channel WLED driving capability.
17 Each channel driving current is up to 30mA
/linux-6.15/Documentation/devicetree/bindings/bus/
H A Drenesas,bsc.yaml15 devices to the SoC, driving several chip select lines, for e.g. NOR
21 must be powered on, and the functional clock driving the BSC must be
/linux-6.15/Documentation/devicetree/bindings/hwmon/
H A Dfan-common.yaml42 fan-driving-mode:
44 Select the driving mode of the fan.(DC, PWM and so on)
/linux-6.15/Documentation/devicetree/bindings/mfd/
H A Drichtek,rt4831.yaml19 For the LCD backlight, it can provide four channel WLED driving capability.
20 Each channel driving current is up to 30mA
/linux-6.15/Documentation/driver-api/gpio/
H A Dintro.rst57 MMC/SD card insertion/removal, detecting card write-protect status, driving
103 The same logic can be applied to emulate open source signaling, by driving the
107 If you are "driving" the signal high but gpiod_get_value(gpio) reports a low
109 driving the shared signal low. That's not necessarily an error. As one common
/linux-6.15/Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm/
H A Dbrg.txt11 - clock-frequency : Specifies the base frequency driving
/linux-6.15/Documentation/devicetree/bindings/media/i2c/
H A Ddongwoon,dw9714.yaml14 driving voice coil lenses in camera modules.

123456