| /linux-6.12.1/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>;
|
| /linux-6.12.1/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 | realtek,rtd1315e-pinctrl.yaml | 115 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.
|
| D | realtek,rtd1619b-pinctrl.yaml | 113 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.
|
| D | realtek,rtd1319d-pinctrl.yaml | 114 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.
|
| 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-6.12.1/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.
104 Controller driving the bus.
111 that all devices are represented including the master driving
|
| /linux-6.12.1/drivers/comedi/drivers/ |
| D | comedi_8255.c | 180 * subdev_8255_io_init - initialize DIO subdevice for driving I/O mapped 8255
185 * Initializes a comedi subdevice as a DIO subdevice driving an 8255 chip.
199 * subdev_8255_mm_init - initialize DIO subdevice for driving mmio-mapped 8255
204 * Initializes a comedi subdevice as a DIO subdevice driving an 8255 chip.
216 * subdev_8255_cb_init - initialize DIO subdevice for driving callback-mapped 8255
222 * Initializes a comedi subdevice as a DIO subdevice driving an 8255 chip.
|
| /linux-6.12.1/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.
|
| /linux-6.12.1/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 | 40 description: Delay to wait after driving gpio active
44 description: Delay to wait after driving gpio inactive
|
| /linux-6.12.1/Documentation/driver-api/gpio/ |
| D | intro.rst | 57 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.12.1/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()
|
| 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()
430 /* Configure driving */ in rts5228_extra_init_hw()
|
| 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 | 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()
505 /* Configure driving */ in rts5261_extra_init_hw()
|
| /linux-6.12.1/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-6.12.1/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-6.12.1/Documentation/devicetree/bindings/hwmon/ |
| D | fan-common.yaml | 42 fan-driving-mode:
44 Select the driving mode of the fan.(DC, PWM and so on)
|
| /linux-6.12.1/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-6.12.1/arch/arm/mach-tegra/ |
| D | platsmp.c | 49 * flow controller to stop driving reset if the CPU has been in tegra20_boot_secondary()
59 * stop driving reset. The CPU will remain in reset because the in tegra20_boot_secondary()
60 * clock and reset block is now driving reset. in tegra20_boot_secondary()
|
| /linux-6.12.1/Documentation/devicetree/bindings/display/panel/ |
| D | boe,bf060y8m-aj0.yaml | 33 description: EL Driving positive (VDD) supply (4.40-4.80V)
35 description: EL Driving negative (VSS) supply (-5.00V to -1.40V)
|
| /linux-6.12.1/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-6.12.1/Documentation/devicetree/bindings/sound/ |
| D | rt5682.txt | 62 - realtek,dmic-clk-driving-high : Set the high driving of the DMIC clock out.
|