| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A 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.
|
| H A 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.
|
| H A 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
|
| /openbmc/linux/Documentation/devicetree/bindings/phy/ |
| H A 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>;
|
| /openbmc/linux/drivers/misc/cardreader/ |
| H A 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()
|
| H A 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()
|
| H A 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()
|
| H A 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()
|
| H A 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()
|
| /openbmc/linux/Documentation/devicetree/bindings/media/ |
| H A 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
|
| /openbmc/linux/Documentation/devicetree/bindings/leds/backlight/ |
| H A 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
|
| /openbmc/linux/Documentation/devicetree/bindings/power/reset/ |
| H A 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]
|
| H A D | gpio-poweroff.yaml | 37 description: Delay to wait after driving gpio active
41 description: Delay to wait after driving gpio inactive
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A 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
|
| /openbmc/linux/Documentation/devicetree/bindings/bus/ |
| H A 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
|
| /openbmc/linux/Documentation/devicetree/bindings/hwmon/ |
| H A D | fan-common.yaml | 42 fan-driving-mode:
44 Select the driving mode of the fan.(DC, PWM and so on)
|
| /openbmc/linux/Documentation/devicetree/bindings/mfd/ |
| H A 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
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Debug/Pid/ |
| H A D | Zone.interface.yaml | 10 This means the name of the thermal/Power PID config that is driving
|
| /openbmc/linux/Documentation/devicetree/bindings/serial/ |
| H A D | brcm,bcm2835-aux-uart.txt | 8 - clocks: Clock driving the hardware; used to figure out the baud rate
|
| /openbmc/linux/Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm/ |
| H A D | brg.txt | 11 - clock-frequency : Specifies the base frequency driving
|
| /openbmc/linux/Documentation/driver-api/gpio/ |
| H A 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
|
| /openbmc/linux/Documentation/devicetree/bindings/sound/ |
| H A D | rt5682.txt | 62 - realtek,dmic-clk-driving-high : Set the high driving of the DMIC clock out.
|
| /openbmc/openbmc/meta-asrock/meta-e3c256d4i/recipes-x86/chassis/x86-power-control/ |
| H A D | power-config-host0.json | 20 // (normally the NMI button input) instead as an output and driving
|
| /openbmc/linux/Documentation/devicetree/bindings/timer/ |
| H A D | fsl,gtm.txt | 10 - clock-frequency : specifies the frequency driving the timer.
|
| /openbmc/linux/Documentation/devicetree/bindings/media/i2c/ |
| H A D | dongwoon,dw9714.yaml | 14 driving voice coil lenses in camera modules.
|