| /Linux-v5.15/Documentation/devicetree/bindings/pinctrl/ |
| D | mediatek,mt8183-pinctrl.yaml | 112 Describe the specific driving setup property.
113 For I2C pins, the existing generic driving setup can only support
114 2/4/6/8/10/12/14/16mA driving. But in specific driving setup, they
116 driving setup, the existing generic setup will be disabled.
117 The specific driving setup is controlled by E1E0EN.
122 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-v5.15/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-v5.15/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
|
| /Linux-v5.15/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.15/include/media/i2c/ |
| D | noon010pc30.h | 15 * @gpio_nreset: GPIO driving nRESET pin
16 * @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
|
| /Linux-v5.15/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.15/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()
|
| 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()
463 /* 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()
519 /* Configure driving */ in rts5261_extra_init_hw()
|
| 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()
275 /* Configure driving */ in rts5249_extra_init_hw()
|
| /Linux-v5.15/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.15/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-v5.15/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-v5.15/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-v5.15/drivers/comedi/drivers/ |
| D | comedi_8255.c | 178 * subdev_8255_init - initialize DIO subdevice for driving I/O mapped 8255
184 * Initializes a comedi subdevice as a DIO subdevice driving an 8255 chip.
213 * subdev_8255_mm_init - initialize DIO subdevice for driving mmio-mapped 8255
219 * Initializes a comedi subdevice as a DIO subdevice driving an 8255 chip.
|
| /Linux-v5.15/Documentation/devicetree/bindings/sound/ |
| D | rt5682.txt | 47 - realtek,dmic-clk-driving-high : Set the high driving of the DMIC clock out.
|
| /Linux-v5.15/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-v5.15/include/media/ |
| D | cec-pin.h | 19 * @high: stop driving the CEC pin. The pull-up will drive the pin
20 * high, unless someone else is driving the pin low.
|
| /Linux-v5.15/Documentation/timers/ |
| D | timekeeping.rst | 94 a different thing. The hardware driving clock events has to be able to
96 system, it is ideal (and customary) to have one such event driving timer per
138 The clock driving sched_clock() may stop or reset to zero during system
|
