Searched full:ready (Results 1 – 25 of 201) sorted by relevance
123456789
| /Documentation/devicetree/bindings/misc/ |
| D | olpc,xo1.75-ec.txt | 9 strobing the ACK pin with the ready signal. See the "ready-gpios" property of the
16 ready-gpios = <&gpio 125 GPIO_ACTIVE_HIGH>;
|
| /Documentation/devicetree/bindings/iio/imu/ |
| D | adi,adis16480.txt | 28 - interrupt-names: Data ready line selection. Valid values are:
33 If this field is left empty, DIO1 is assigned as default data ready
63 Each DIOx pin supports only one function at a time (data ready line
67 Data ready has highest priority.
|
| D | st_lsm6dsx.txt | 21 "data ready" (valid values: 1 or 2).
23 - drive-open-drain: the interrupt/data ready line will be configured
|
| /Documentation/devicetree/bindings/sound/ |
| D | rockchip,rk3399-gru-sound.txt | 10 - dmic-wakeup-delay-ms : specify delay time (ms) for DMIC ready.
12 delay for DMIC to ready so that rt5514 can avoid recording before
|
| D | max98357a.txt | 14 ready before SD_MODE is unmuted in order to avoid the speaker pop noise.
|
| D | rt5514.txt | 21 Set the DMIC initial delay (ms) to wait it ready for I2C.
|
| D | rt5660.txt | 22 added delay time for waiting codec power ready.
|
| /Documentation/devicetree/bindings/mfd/ |
| D | rohm,bd71837-pmic.txt | 31 are called as SNVS and READY. At READY state all the PMIC power outputs go
37 switched power state to SNVS. If reset is done via READY state the power
39 target state is set to READY by default. If SNVS state is used the boot
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-ina2xx-adc | 7 Ready Flag to being set prior to committing a new value to the sample
11 Writing '1' will remove the polling for the Conversion Ready Flags to
|
| /Documentation/devicetree/bindings/spi/ |
| D | spi-pxa2xx.txt | 15 - ready-gpios: GPIO used to signal a SPI master that the FIFO is filled
16 and we're ready to service a transfer. Only useful in slave mode.
|
| /Documentation/hwmon/ |
| D | abituguru-datasheet.rst | 81 uGuru ready
85 in "ready" mode.
87 To put the uGuru in ready mode first write 0x00 to DATA and then wait for DATA
94 After reading CMD, DATA should hold 0x08 which means that the uGuru is ready
103 First the uGuru must be in "ready" mode as described above, DATA should hold
107 wait for to DATA to hold 0x08 again indicating that it wants / is ready for
118 which indicates that the uGuru is ready to be read (max 250 reads) and once
126 ready mode, so that it is ready for the next read / write cycle. This way
137 which indicates that the uGuru is ready to be written (max 250 reads) and
146 ready mode, so that it is ready for the next read / write cycle. This way
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | qcom,adsp.txt | 36 must be "wdog", "fatal", "ready", "handover", "stop-ack"
38 must be "wdog", "fatal", "ready", "handover", "stop-ack",
108 "ready",
142 "ready",
|
| D | qcom,hexagon-v56.txt | 21 Definition: must list the watchdog, fatal IRQs ready, handover and
27 Definition: must be "wdog", "fatal", "ready", "handover", "stop-ack"
113 interrupt-names = "wdog", "fatal", "ready",
|
| D | qcom,wcnss-pil.txt | 29 ready, handover and stop-ack IRQs
34 Definition: should be "wdog", "fatal", optionally followed by "ready",
112 interrupt-names = "wdog", "fatal", "ready", "handover", "stop-ack";
|
| /Documentation/scsi/ |
| D | scsi_eh.txt | 186 device forget about timed out scmds and make them ready for new
188 lower layers and lower layers are ready to process or fail the scmd
327 either offline or ready, scsi_eh_finish_cmd() is invoked for
331 Note that both offline and ready status mean that the sdev is
332 ready to process new scmds, where processing also implies
345 make failed sdevs ready for new commands.
358 If STU succeeds and the sdev is either offline or ready,
386 scmds on all ready or offline sdevs on the channel are
395 all ready or offline sdevs on the host are EH-finished.
419 all failed scmds and either ready for new commands or offline. Also,
[all …]
|
| D | dpti.txt | 46 * V2.4 First version ready to be submitted to be embedded in the kernel
63 * now online (at the FW level) when test unit ready or inquiry
|
| /Documentation/devicetree/bindings/mtd/ |
| D | lpc32xx-slc.txt | 11 - nxp,wdr-clks: Delay before Ready signal is tested on write (W_RDY)
12 - nxp,rdr-clks: Delay before Ready signal is tested on read (R_RDY)
|
| /Documentation/devicetree/bindings/iio/ |
| D | st-sensors.txt | 17 "data ready" (valid values: 1 or 2). This property is not configurable
19 - drive-open-drain: the interrupt/data ready line will be configured
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-qla2xxx | 6 ready for retrieval.
|
| /Documentation/devicetree/bindings/iio/magnetometer/ |
| D | pni,rm3100.txt | 10 - interrupts: data ready (DRDY) from the chip.
|
| D | ak8974.txt | 14 - interrupts: data ready (DRDY) and interrupt (INT1) lines
|
| /Documentation/media/uapi/v4l/ |
| D | func-poll.rst | 42 until the driver has captured data or is ready to accept data for
48 function waits until the device is ready to accept a new buffer to be
86 it waits until the driver is ready for a non-blocking
|
| /Documentation/networking/device_drivers/toshiba/ |
| D | spider_net.txt | 27 "full" and "not-in-use". An "empty" or "ready" descriptor is ready
30 descriptor is neither empty or full; it is simply not ready. It may
35 buffers. These are all marked "empty", ready to receive data. This
65 then mark the descr as "empty", ready to receive data. Thus, when there
|
| /Documentation/ide/ |
| D | ChangeLog.ide-floppy.1996-2002 | 15 * Issue START command only if TEST UNIT READY fails.
59 * drive before the drive was actually ready.
|
| /Documentation/devicetree/bindings/iio/humidity/ |
| D | hts221.txt | 8 - drive-open-drain: the interrupt/data ready line will be configured
|
123456789