| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/display/sunxi/ |
| D | sun4i-drm.txt | 112 - resets: phandle to the reset controller driving the PHY
128 - clocks: the clocks driving the TV encoder
129 - resets: phandle to the reset controller driving the encoder
158 - 'tcon-ch0': The clock driving the TCON channel 0, if supported
159 - resets: phandles to the reset controllers driving the encoder
181 - 'tcon-ch0': The clock driving the TCON channel 0
183 - 'tcon-ch1': The clock driving the TCON channel 1
187 - 'lvds': The reset line driving the LVDS logic
230 - resets: phandle to the reset line driving the TCON TOP
271 - resets: phandles to the reset line driving the DRC
[all …]
|
| /kernel/linux/linux-4.19/drivers/misc/cardreader/ |
| D | rts5227.c | 51 u8 (*driving)[3], drive_sel; in rts5227_fill_driving() local
54 driving = driving_3v3; in rts5227_fill_driving()
57 driving = driving_1v8; in rts5227_fill_driving()
62 0xFF, driving[drive_sel][0]); in rts5227_fill_driving()
64 0xFF, driving[drive_sel][1]); in rts5227_fill_driving()
66 0xFF, driving[drive_sel][2]); in rts5227_fill_driving()
125 /* Configure driving */ in rts5227_extra_init_hw()
|
| /kernel/linux/linux-4.19/drivers/pinctrl/mediatek/ |
| D | pinctrl-mtk-common.h | 79 * struct mtk_drv_group_desc - Provide driving group data.
104 * struct mtk_pin_drv_grp - Provide each pin driving info.
106 * @offset: The offset of driving register for this pin.
107 * @bit: The bit of driving register for this pin.
202 * @grp_desc: The driving group info.
203 * @pin_drv_grp: The driving group for all pins.
|
| /kernel/linux/linux-5.10/drivers/pinctrl/mediatek/ |
| D | pinctrl-mtk-common.h | 71 * struct mtk_drv_group_desc - Provide driving group data.
96 * struct mtk_pin_drv_grp - Provide each pin driving info.
98 * @offset: The offset of driving register for this pin.
99 * @bit: The bit of driving register for this pin.
194 * @grp_desc: The driving group info.
195 * @pin_drv_grp: The driving group for all pins.
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-4.19/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]
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-5.10/include/media/i2c/ |
| D | noon010pc30.h | 14 * @gpio_nreset: GPIO driving nRESET pin
15 * @gpio_nstby: GPIO driving nSTBY pin
|
| D | s5k4ecgx.h | 24 * @gpio_reset: GPIO driving RESET pin
25 * @gpio_stby : GPIO driving STBY pin
|
| D | s5k6aa.h | 29 * @gpio_reset: GPIO driving RESET pin
30 * @gpio_stby: GPIO driving STBY pin
|
| D | s5c73m3.h | 36 * @gpio_reset: GPIO driving RESET pin
37 * @gpio_stby: GPIO driving STBY pin
|
| /kernel/linux/linux-4.19/include/media/i2c/ |
| D | noon010pc30.h | 18 * @gpio_nreset: GPIO driving nRESET pin
19 * @gpio_nstby: GPIO driving nSTBY pin
|
| D | s5k4ecgx.h | 28 * @gpio_reset: GPIO driving RESET pin
29 * @gpio_stby : GPIO driving STBY pin
|
| D | s5k6aa.h | 33 * @gpio_reset: GPIO driving RESET pin
34 * @gpio_stby: GPIO driving STBY pin
|
| D | s5c73m3.h | 36 * @gpio_reset: GPIO driving RESET pin
37 * @gpio_stby: GPIO driving STBY pin
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.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()
166 /* Configure driving */ in rts5227_extra_init_hw()
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/pinctrl/ |
| 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
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.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
|