| /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-6.6/Documentation/devicetree/bindings/phy/ |
| D | realtek,usb2phy.yaml | 93 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>;
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pinctrl/ |
| D | mediatek,mt8183-pinctrl.yaml | 120 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.
|
| D | mediatek,mt8365-pinctrl.yaml | 124 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.
|
| 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/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-6.6/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-6.6/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/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-6.6/Documentation/devicetree/bindings/power/reset/ |
| D | gpio-restart.yaml | 42 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]
|
| D | gpio-poweroff.yaml | 37 description: Delay to wait after driving gpio active
41 description: Delay 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-6.6/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/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-6.6/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()
125 /* Configure driving */ in rts5227_extra_init_hw()
|
| /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-6.6/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/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
|
| /kernel/linux/linux-6.6/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
|