/Linux-v5.10/Documentation/devicetree/bindings/pinctrl/ |
D | pinctrl-mt8183.txt | 65 For I2C pins, there are existing generic driving setup and the specific 66 driving setup. I2C pins can only support 2/4/6/8/10/12/14/16mA driving 67 adjustment in generic driving setup. But in specific driving setup, 69 driving setup for I2C pins, the existing generic driving setup will be 71 driving setup. The specific driving setup is controlled by E1E0EN. 72 So we need add extra vendor driving preperty instead of 73 the generic driving property. 75 driving setup property. "XXX" means the value of E1E0EN. EN is 0 or 1. 76 It 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-v5.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-v5.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-v5.10/Documentation/devicetree/bindings/power/reset/ |
D | gpio-restart.txt | 28 - open-source : Treat the GPIO as being open source and defer driving 40 - active-delay: Delay (default 100) to wait after driving gpio active [ms] 41 - inactive-delay: Delay (default 100) to wait after driving gpio inactive [ms]
|
D | gpio-poweroff.txt | 30 - active-delay-ms: Delay (default 100) to wait after driving gpio active 31 - inactive-delay-ms: Delay (default 100) to wait after driving gpio inactive
|
/Linux-v5.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-v5.10/Documentation/devicetree/bindings/media/i2c/ |
D | dongwoon,dw9714.txt | 4 for driving voice coil lenses in camera modules.
|
/Linux-v5.10/Documentation/devicetree/bindings/serial/ |
D | brcm,bcm2835-aux-uart.txt | 8 - clocks: Clock driving the hardware; used to figure out the baud rate
|
D | brcm,bcm6345-uart.txt | 11 - clocks: Clock driving the hardware; used to figure out the baud rate
|
/Linux-v5.10/Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm/ |
D | brg.txt | 11 - clock-frequency : Specifies the base frequency driving
|
/Linux-v5.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-v5.10/Documentation/devicetree/bindings/timer/ |
D | fsl,gtm.txt | 10 - clock-frequency : specifies the frequency driving the timer.
|
/Linux-v5.10/Documentation/devicetree/bindings/iio/temperature/ |
D | mlx90614.txt | 15 is no need for a GPIO driving the SCL line. If no GPIO is given, power
|
/Linux-v5.10/Documentation/hwmon/ |
D | pwm-fan.rst | 14 The driver implements a simple interface for driving a fan connected to
|
/Linux-v5.10/drivers/clk/versatile/ |
D | Kconfig | 28 Simple regmap-based driver driving clock generators on Versatile
|
/Linux-v5.10/Documentation/devicetree/bindings/gpio/ |
D | ni,169445-nand-gpio.txt | 20 - no-output: disables driving output on the pins
|
D | cdns,gpio.txt | 12 - clocks: should contain one entry referencing the peripheral clock driving
|
/Linux-v5.10/Documentation/devicetree/bindings/leds/ |
D | leds-an30259a.txt | 3 The AN30259A is a LED controller capable of driving three LEDs independently. It supports
|
/Linux-v5.10/arch/arm64/boot/dts/amlogic/ |
D | meson-g12b-a311d-khadas-vim3.dts | 22 * The PHY driving these differential lines is shared between
|