Home
last modified time | relevance | path

Searched full:ready (Results 1 – 25 of 220) sorted by relevance

123456789

/Documentation/devicetree/bindings/spi/
Dmarvell,mmp2-ssp.yaml29 ready-gpios:
32 ready to service a transfer. Only useful in slave mode.
42 ready-gpios: [ spi-slave ]
/Documentation/devicetree/bindings/misc/
Dolpc,xo1.75-ec.yaml16 response data) by strobing the ACK pin with the ready signal. See the
17 "ready-gpios" property of the SSP binding as documented in:
47 ready-gpios = <&gpio 125 GPIO_ACTIVE_HIGH>;
/Documentation/devicetree/bindings/iio/imu/
Dadi,adis16480.txt29 - interrupt-names: Data ready line selection. Valid values are:
34 If this field is left empty, DIO1 is assigned as default data ready
64 Each DIOx pin supports only one function at a time (data ready line
68 Data ready has highest priority.
Dst_lsm6dsx.txt23 "data ready" (valid values: 1 or 2).
25 - drive-open-drain: the interrupt/data ready line will be configured
/Documentation/devicetree/bindings/sound/
Drockchip,rk3399-gru-sound.txt10 - dmic-wakeup-delay-ms : specify delay time (ms) for DMIC ready.
12 delay for DMIC to ready so that rt5514 can avoid recording before
Drt5514.txt21 Set the DMIC initial delay (ms) to wait it ready for I2C.
/Documentation/ABI/testing/
Dsysfs-bus-iio-ina2xx-adc7 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/hwmon/
Dabituguru-datasheet.rst81 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/virt/kvm/
Dmsr.rst203 /* Used for 'page ready' events delivered via interrupt notification */
215 present in CPUID. Bit 3 enables interrupt based delivery of 'page ready'
236 hypervisor at the time of APF 'page ready' event injection. The content
239 supposed to write '0' to 'token' when it is done handling 'page ready'
245 ready' APF delivery needs to be written to before enabling APF mechanism
249 Note, previously, 'page ready' events were delivered via the same #PF
256 Currently 'page ready' APF events will be always delivered on the
360 Bits 0-7: APIC vector for delivery of 'page ready' APF events.
363 Interrupt vector for asynchnonous 'page ready' notifications delivery.
374 When the guest is done processing 'page ready' APF event and 'token'
/Documentation/devicetree/bindings/iio/light/
Dams,as73211.yaml28 Interrupt specifier for the READY interrupt generated by the device.
51 interrupts = <19 IRQ_TYPE_EDGE_RISING>; /* READY */
/Documentation/devicetree/bindings/mtd/
Dlpc32xx-slc.txt11 - 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/scsi/
Dscsi_eh.rst203 device forget about timed out scmds and make them ready for new
205 lower layers and lower layers are ready to process or fail the scmd
360 either offline or ready, scsi_eh_finish_cmd() is invoked for
364 Note that both offline and ready status mean that the sdev is
365 ready to process new scmds, where processing also implies
378 make failed sdevs ready for new commands.
391 If STU succeeds and the sdev is either offline or ready,
419 scmds on all ready or offline sdevs on the channel are
428 all ready or offline sdevs on the host are EH-finished.
453 all failed scmds and either ready for new commands or offline. Also,
[all …]
/Documentation/devicetree/bindings/remoteproc/
Dqcom,hexagon-v56.txt21 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",
Dqcom,adsp.txt54 must be "wdog", "fatal", "ready", "handover", "stop-ack"
58 must be "wdog", "fatal", "ready", "handover", "stop-ack",
164 "ready",
198 "ready",
Dqcom,wcnss-pil.txt29 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/devicetree/bindings/iio/magnetometer/
Dasahi-kasei,ak8975.yaml33 AK8975 has a "Data ready" pin (DRDY) which informs that data
34 is ready to be read and is possible to listen on it. If used,
Dpni,rm3100.txt10 - interrupts: data ready (DRDY) from the chip.
/Documentation/userspace-api/media/v4l/
Dfunc-poll.rst32 until the driver has captured data or is ready to accept data for
38 function waits until the device is ready to accept a new buffer to be
76 it waits until the driver is ready for a non-blocking
/Documentation/devicetree/bindings/mfd/
Drohm,bd71847-pmic.yaml45 # states. States are called as SNVS and READY. At READY state all the PMIC
51 # reset has switched power state to SNVS. If reset is done via READY state the
53 # target state is set to READY by default. If SNVS state is used the boot
Drohm,bd71837-pmic.yaml39 # are called as SNVS and READY. At READY state all the PMIC power outputs go
45 # switched power state to SNVS. If reset is done via READY state the power
47 # target state is set to READY by default. If SNVS state is used the boot
/Documentation/devicetree/bindings/iio/
Dst-sensors.txt17 "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/
Dsysfs-driver-qla2xxx6 ready for retrieval.
/Documentation/devicetree/bindings/iio/proximity/
Dvl53l0x.txt8 - interrupts: Interrupt for notifying that new measurement is ready.
/Documentation/networking/device_drivers/ethernet/toshiba/
Dspider_net.rst29 "full" and "not-in-use". An "empty" or "ready" descriptor is ready
32 descriptor is neither empty or full; it is simply not ready. It may
37 buffers. These are all marked "empty", ready to receive data. This
67 then mark the descr as "empty", ready to receive data. Thus, when there
/Documentation/ide/
DChangeLog.ide-floppy.1996-200215 * Issue START command only if TEST UNIT READY fails.
59 * drive before the drive was actually ready.

123456789