| /openbmc/linux/arch/arm/boot/dts/nxp/mxs/ |
| H A D | imx28-duckbill.dts | 88 fsl,drive-strength = <MXS_DRIVE_4mA>;
98 fsl,drive-strength = <MXS_DRIVE_4mA>;
109 fsl,drive-strength = <MXS_DRIVE_4mA>;
|
| H A D | imx28-cfa10057.dts | 93 fsl,drive-strength = <MXS_DRIVE_4mA>;
120 fsl,drive-strength = <MXS_DRIVE_4mA>;
133 fsl,drive-strength = <MXS_DRIVE_4mA>;
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | qcom,mdm9615-pinctrl.yaml | 93 drive-strength = <8>;
101 drive-strength = <8>;
108 drive-strength = <2>;
|
| H A D | qcom,apq8064-pinctrl.txt | 30 parameters, such as pull-up, drive strength, etc.
45 pins, function, bias-disable, bias-pull-down, bias-pull-up, drive-strength,
85 drive-strength = <4>;
91 drive-strength = <2>;
|
| H A D | toshiba,visconti-pinctrl.yaml | 37 configuration, pullups, drive strength.
66 drive-strength:
70 Selects the drive strength for the specified pins, in mA.
|
| H A D | mediatek,mt8183-pinctrl.yaml | 81 configuration, pullups, drive strength, input enable/disable and input
110 drive-strength:
113 drive-strength-microamp:
116 mediatek,drive-strength-adv:
119 DEPRECATED: Please use drive-strength-microamp instead.
225 drive-strength-microamp = <1000>;
|
| H A D | axis,artpec6-pinctrl.txt | 11 drive strength and bias pullup of the pin group. If either of these options is
50 - drive-strength: 4, 6, 8, 9 mA. For SD and NAND pins, this is for 3.3V VCCQ3.
62 drive-strength = <4>;
|
| H A D | brcm,ns2-pinmux.txt | 27 drive-strength, slew-rate, input-enable, input-disable are supported
56 /* Set the drive strength of sdio d4 pin */
59 drive-strength = <8>;
|
| H A D | cypress,cy8c95x0.yaml | 92 drive-push-pull: true
94 drive-open-drain: true
96 drive-open-source: true
|
| H A D | qcom,ipq4019-pinctrl.txt | 33 parameters, such as pull-up, drive strength, etc.
47 pins, function, bias-disable, bias-pull-down, bias-pull-up, drive-open-drain,
48 drive-strength.
56 Supports mux, bias and drive-strength
|
| H A D | qcom,sm8150-pinctrl.yaml | 140 drive-strength = <6>;
148 drive-strength = <2>;
155 drive-strength = <2>;
162 drive-strength = <2>;
|
| H A D | qcom,msm8998-pinctrl.yaml | 141 drive-strength = <2>;
147 drive-strength = <2>;
153 drive-strength = <2>;
162 drive-strength = <2>;
|
| /openbmc/linux/arch/arm64/boot/dts/qcom/ |
| H A D | apq8016-sbc.dts | 407 * 2mA drive strength is not enough when connecting multiple
411 drive-strength = <16>;
415 drive-strength = <16>;
419 drive-strength = <16>;
574 drive-strength = <2>;
589 drive-strength = <8>;
597 drive-strength = <16>;
605 drive-strength = <2>;
613 drive-strength = <16>;
621 drive-strength = <2>;
[all …]
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 200 | 70 …-drive file="${TEST_IMG}",media=disk,if=none,cache=$CACHEMODE,aio=$AIOMODE,id=drive_sysdisk,format…
71 -device scsi-hd,drive=drive_sysdisk,bus=scsi0.0,id=sysdisk,bootindex=0
|
| H A D | 267.out | 17 === -drive if=none ===
20 Testing: -drive driver=file,file=TEST_DIR/t.IMGFMT,if=none
31 Testing: -drive driver=IMGFMT,file=TEST_DIR/t.IMGFMT,if=none
42 Testing: -drive driver=IMGFMT,file=TEST_DIR/t.IMGFMT,if=none -device virtio-blk,drive=none0
53 === -drive if=virtio ===
56 Testing: -drive driver=file,file=TEST_DIR/t.IMGFMT,if=virtio
67 Testing: -drive driver=IMGFMT,file=TEST_DIR/t.IMGFMT,if=virtio
|
| H A D | 091 | 64 _launch_qemu -drive file="${TEST_IMG}",cache=${CACHEMODE},aio=${AIOMODE},id=disk
70 _launch_qemu -drive file="${TEST_IMG}",cache=${CACHEMODE},aio=${AIOMODE},id=disk \
|
| H A D | 249.out | 8 === Send a write command to a drive opened in read-only mode (1)
23 === Send a write command to a drive opened in read-only mode (2)
42 === Send a write command to a drive opened in read-only mode (3)
|
| /openbmc/linux/arch/arm/boot/dts/qcom/ |
| H A D | qcom-msm8974pro-oneplus-bacon.dts | 440 drive-strength = <8>;
447 drive-strength = <4>;
453 drive-strength = <4>;
462 drive-strength = <2>;
469 drive-strength = <2>;
478 drive-strength = <6>;
485 drive-strength = <2>;
|
| H A D | qcom-msm8226.dtsi | 431 drive-strength = <2>;
438 drive-strength = <2>;
445 drive-strength = <2>;
452 drive-strength = <2>;
459 drive-strength = <2>;
467 drive-strength = <2>;
475 drive-strength = <2>;
482 drive-strength = <10>;
511 drive-strength = <8>;
518 drive-strength = <8>;
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/gpio/ |
| H A D | gpio-mmio.yaml | 45 This register may also be used to drive GPIOs if the SET register is
49 register will drive the GPIO line high.
52 register will drive the GPIO line low. If this register is omitted,
80 If this property is present, the controller cannot drive the GPIO lines.
|
| /openbmc/qemu/docs/system/devices/ |
| H A D | usb.rst | 61 -drive if=none,id=usbstick,format=raw,file=/path/to/image \\
65 -device usb-storage,bus=ehci.0,drive=usbstick
113 ``usb-storage,drive=drive_id``
118 a drive backed by a raw format disk image:
123 -drive if=none,id=stick,format=raw,file=/path/to/file.img \\
125 -device usb-storage,bus=xhci.0,drive=stick
130 on the command line, as well as using the ``-drive`` option to
133 logical units: two disks and one cdrom drive:
138 -drive if=none,id=uas-disk1,format=raw,file=/path/to/file1.img \\
145 -device scsi-cd,bus=uas.0,scsi-id=0,lun=5,drive=uas-cdrom
[all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/pinctrl/ |
| H A D | pinctrl-bindings.txt | 4 such as pull-up/down, tri-state, drive-strength etc are designated as pin
183 drive-push-pull - drive actively high and low
184 drive-open-drain - drive with open drain
185 drive-open-source - drive with open source
186 drive-strength - sink or source at most X mA
230 - drive-strength takes as argument the target strength in mA.
|
| /openbmc/linux/Documentation/admin-guide/blockdev/ |
| H A D | paride.rst | 30 were to open up a parallel port CD-ROM drive, for instance, one would
31 find a standard ATAPI CD-ROM drive, a power supply, and a single adapter
44 - MicroSolutions backpack 8000t tape drive
91 If you do not know what kind of parallel port adapter is used in your drive,
107 MicroSolutions PD drive bpck
108 MicroSolutions hard-drive bpck
122 drive to work.
139 also need to know the unit ID number for each drive. This is usually
140 the last two digits of the drive's serial number (but read MicroSolutions'
|
| /openbmc/linux/arch/riscv/boot/dts/starfive/ |
| H A D | jh7110-starfive-visionfive-2.dtsi | 345 drive-strength = <12>;
363 drive-strength = <12>;
374 drive-strength = <12>;
397 drive-strength = <12>;
448 drive-strength = <12>;
459 drive-strength = <2>;
|
| /openbmc/linux/Documentation/devicetree/bindings/mmc/ |
| H A D | rockchip-dw-mshc.yaml | 58 the card interface unit clock. If "ciu-drive" and "ciu-sample" are
67 - const: ciu-drive
71 "ciu-drive" and "ciu-sample" are supported. They are used
118 clock-names = "biu", "ciu", "ciu-drive", "ciu-sample";
|