/linux-5.19.10/Documentation/devicetree/bindings/pinctrl/ |
D | mediatek,mt8183-pinctrl.yaml | 115 Describe the specific driving setup property. 116 For I2C pins, the existing generic driving setup can only support 117 2/4/6/8/10/12/14/16mA driving. But in specific driving setup, they 119 driving setup, the existing generic setup will be disabled. 120 The specific driving setup is controlled by E1E0EN. 125 EN is used to enable or disable the specific driving setup.
|
D | sprd,pinctrl.txt | 8 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
|
/linux-5.19.10/drivers/misc/cardreader/ |
D | rts5227.c | 39 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()
|
D | rts5260.c | 41 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()
|
D | rts5228.c | 41 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()
|
D | rts5261.c | 40 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()
|
D | rts5249.c | 38 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()
|
/linux-5.19.10/Documentation/devicetree/bindings/media/ |
D | pxa-camera.txt | 11 - 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-5.19.10/Documentation/devicetree/bindings/leds/backlight/ |
D | richtek,rt4831-backlight.yaml | 16 For the LCD backlight, it can provide four channel WLED driving capability. 17 Each channel driving current is up to 30mA
|
/linux-5.19.10/Documentation/ABI/testing/ |
D | sysfs-bus-i3c | 53 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. 96 that all devices are represented including the master driving
|
D | sysfs-bus-iio-frequency-ad9523 | 30 Writing this file has the effect as driving the external
|
/linux-5.19.10/Documentation/devicetree/bindings/power/reset/ |
D | gpio-restart.yaml | 39 description: Treat the GPIO as being open source and defer driving it to when the restart is 58 description: Delay (default 100) to wait after driving gpio active [ms] 63 description: Delay (default 100) to wait after driving gpio inactive [ms]
|
D | gpio-poweroff.yaml | 37 description: Delay to wait after driving gpio active 41 description: Delay to wait after driving gpio inactive
|
/linux-5.19.10/Documentation/devicetree/bindings/bus/ |
D | renesas,bsc.yaml | 15 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-5.19.10/Documentation/devicetree/bindings/mfd/ |
D | richtek,rt4831.yaml | 19 For the LCD backlight, it can provide four channel WLED driving capability. 20 Each channel driving current is up to 30mA
|
/linux-5.19.10/Documentation/devicetree/bindings/sound/ |
D | rt5682.txt | 47 - realtek,dmic-clk-driving-high : Set the high driving of the DMIC clock out.
|
D | realtek,rt5682s.yaml | 69 realtek,dmic-clk-driving-high: 72 Set the high driving of the DMIC clock out.
|
/linux-5.19.10/Documentation/devicetree/bindings/media/i2c/ |
D | dongwoon,dw9714.txt | 4 for driving voice coil lenses in camera modules.
|
/linux-5.19.10/Documentation/devicetree/bindings/serial/ |
D | brcm,bcm2835-aux-uart.txt | 8 - clocks: Clock driving the hardware; used to figure out the baud rate
|
/linux-5.19.10/Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm/ |
D | brg.txt | 11 - clock-frequency : Specifies the base frequency driving
|
/linux-5.19.10/Documentation/driver-api/gpio/ |
D | intro.rst | 69 MMC/SD card insertion/removal, detecting card write-protect status, driving 115 The same logic can be applied to emulate open source signaling, by driving the 119 If you are "driving" the signal high but gpiod_get_value(gpio) reports a low 121 driving the shared signal low. That's not necessarily an error. As one common
|
/linux-5.19.10/Documentation/devicetree/bindings/timer/ |
D | fsl,gtm.txt | 10 - clock-frequency : specifies the frequency driving the timer.
|
/linux-5.19.10/drivers/clk/versatile/ |
D | Kconfig | 28 Simple regmap-based driver driving clock generators on Versatile
|
/linux-5.19.10/Documentation/hwmon/ |
D | pwm-fan.rst | 14 The driver implements a simple interface for driving a fan connected to
|
/linux-5.19.10/Documentation/devicetree/bindings/iio/temperature/ |
D | melexis,mlx90614.yaml | 28 driving the SCL line. If no GPIO is given, power management is disabled.
|