Home
last modified time | relevance | path

Searched full:responds (Results 1 – 25 of 224) sorted by relevance

123456789

/kernel/linux/linux-4.19/Documentation/isdn/
DREADME.audio48 AT+VRX Start recording. Emulator responds with
81 AT+VTX Start audio playback. Emulator responds
87 On incoming calls, if the application responds to a RING
89 responds with either CONNECT (data call) or VCON (voice call).
91 On outgoing voice calls, the emulator responds with VCON
97 Upon AT+VRX command, the emulator responds with CONNECT, and
128 When sending audio data, upon AT+VTX command, emulator responds with
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/display/
Dmipi-dsi-bus.txt46 that the peripheral responds to.
47 - If the virtual channels that a peripheral responds to are consecutive, the
61 /* peripheral responds to virtual channel 0 */
76 /* peripheral responds to virtual channels 0 and 2 */
91 /* peripheral responds to virtual channels 1, 2 and 3 */
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/
Dmipi-dsi-bus.txt58 that the peripheral responds to.
59 - If the virtual channels that a peripheral responds to are consecutive, the
101 /* peripheral responds to virtual channel 0 */
117 /* peripheral responds to virtual channels 0 and 2 */
133 /* peripheral responds to virtual channels 1, 2 and 3 */
Ddsi-controller.yaml53 channel that the peripheral responds to.
/kernel/linux/linux-4.19/drivers/scsi/
Dscsi_devinfo.c65 {"HITACHI", "DK312C", "CM81", BLIST_NOLUN}, /* responds to all lun */
66 {"HITACHI", "DK314C", "CR21", BLIST_NOLUN}, /* responds to all lun */
75 {"MEDIAVIS", "RENO CD-ROMX2A", "2.03", BLIST_NOLUN}, /* responds to all lun */
76 {"MICROTEK", "ScanMakerIII", "2.30", BLIST_NOLUN}, /* responds to all lun */
78 {"PHILIPS", "PCA80SC", "V4-2", BLIST_NOLUN}, /* responds to all lun */
80 {"SUN", "SENA", NULL, BLIST_NOLUN}, /* responds to all luns */
91 {"SEAGATE", "ST296", "921", BLIST_NOLUN}, /* responds to all lun */
92 {"SEAGATE", "ST1581", "6538", BLIST_NOLUN}, /* responds to all lun */
105 {"TEAC", "MT-2ST/45S2-27", "RV M", BLIST_NOLUN}, /* responds to all lun */
114 {"MICROTEK", "ScanMaker II", "5.61", BLIST_NOLUN}, /* responds to all lun */
[all …]
/kernel/linux/linux-5.10/drivers/scsi/
Dscsi_devinfo.c65 {"HITACHI", "DK312C", "CM81", BLIST_NOLUN}, /* responds to all lun */
66 {"HITACHI", "DK314C", "CR21", BLIST_NOLUN}, /* responds to all lun */
75 {"MEDIAVIS", "RENO CD-ROMX2A", "2.03", BLIST_NOLUN}, /* responds to all lun */
76 {"MICROTEK", "ScanMakerIII", "2.30", BLIST_NOLUN}, /* responds to all lun */
78 {"PHILIPS", "PCA80SC", "V4-2", BLIST_NOLUN}, /* responds to all lun */
80 {"SUN", "SENA", NULL, BLIST_NOLUN}, /* responds to all luns */
91 {"SEAGATE", "ST296", "921", BLIST_NOLUN}, /* responds to all lun */
92 {"SEAGATE", "ST1581", "6538", BLIST_NOLUN}, /* responds to all lun */
105 {"TEAC", "MT-2ST/45S2-27", "RV M", BLIST_NOLUN}, /* responds to all lun */
114 {"MICROTEK", "ScanMaker II", "5.61", BLIST_NOLUN}, /* responds to all lun */
[all …]
/kernel/linux/linux-5.10/drivers/net/dsa/mv88e6xxx/
Dsmi.c17 * is the only device connected to the SMI master. In this mode it responds to
21 * multiple devices to share the SMI interface. In this mode it responds to only
25 * configuration, and the device responds to 16 of the 32 SMI
/kernel/linux/linux-5.10/drivers/block/rnbd/
DREADME65 RNBD_MSG_SESS_INFO to the server. Server responds with
71 Server responds to the message with RNBD_MSG_OPEN_RSP. This contains
/kernel/linux/linux-4.19/Documentation/misc-devices/
Deeprom62 DDC Monitors may contain any device. Often a 24C01, which responds to all 8
70 location). The chip responds to "write quick" detection at this address but
/kernel/linux/linux-4.19/Documentation/hid/
Dintel-ish-hid.txt178 sends). The recipient of DMA message responds with DMA_XFER_ACK, indicating
182 (that includes RX buffer) and FW responds with DMA_ALLOC_NOTIFY_ACK.
223 - FW responds with HOST_START_RES_CMD
225 - FW responds with HOST_ENUM_RES_CMD that includes bitmap of available FW
229 - FW responds with HOST_CLIENT_PROPERTIES_RES_CMD. Properties include UUID,
Duhid.txt68 the device on the control channel. Once the device responds, you must forward
174 remember the "id" field in the payload. Once your hid device responds to the
/kernel/linux/linux-5.10/Documentation/admin-guide/cgroup-v1/
Dfreezer-subsystem.rst45 responds to them.
47 Another example of a program which catches and responds to these
/kernel/linux/linux-4.19/Documentation/cgroup-v1/
Dfreezer-subsystem.txt41 responds to them.
43 Another example of a program which catches and responds to these
/kernel/linux/linux-5.10/Documentation/misc-devices/
Deeprom.rst71 DDC Monitors may contain any device. Often a 24C01, which responds to all 8
79 location). The chip responds to "write quick" detection at this address but
/kernel/linux/linux-5.10/Documentation/hid/
Dintel-ish-hid.rst195 sends). The recipient of DMA message responds with DMA_XFER_ACK, indicating
199 (that includes RX buffer) and FW responds with DMA_ALLOC_NOTIFY_ACK.
243 - FW responds with HOST_START_RES_CMD
245 - FW responds with HOST_ENUM_RES_CMD that includes bitmap of available FW
249 - FW responds with HOST_CLIENT_PROPERTIES_RES_CMD. Properties include UUID,
Duhid.rst69 the device on the control channel. Once the device responds, you must forward
179 remember the "id" field in the payload. Once your hid device responds to the
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/rtc/
Disil,isl12026.txt4 registers respond at bus address 0x6f, and the EEPROM array responds
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/rtc/
Disil,isl12026.txt4 registers respond at bus address 0x6f, and the EEPROM array responds
/kernel/linux/linux-5.10/drivers/media/dvb-frontends/
Dl64781.c510 * broadcast. If nothing responds there is no L64781 on the bus... in l64781_attach()
517 /* The chip always responds to reads */ in l64781_attach()
535 /* Responds to all reads with 0 */ in l64781_attach()
544 /* Responds with register default value */ in l64781_attach()
/kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/marvell/
Docteontx2.rst105 links this driver talks to AF and AF gets that info from firmware and responds
120 forwards that to AF. AF after processing, responds back to PF and PF forwards
/kernel/linux/linux-4.19/drivers/media/dvb-frontends/
Dl64781.c522 * broadcast. If nothing responds there is no L64781 on the bus... in l64781_attach()
529 /* The chip always responds to reads */ in l64781_attach()
547 /* Responds to all reads with 0 */ in l64781_attach()
556 /* Responds with register default value */ in l64781_attach()
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/adc/
Davia-hx711.yaml17 - dout-gpio is the sensor data the sensor responds to the clock
/kernel/linux/linux-4.19/drivers/staging/comedi/drivers/
Ddt9812.c248 /* DT9812 only responds to 32 byte writes!! */ in dt9812_read_info()
272 /* DT9812 only responds to 32 byte writes!! */ in dt9812_read_multiple_registers()
298 /* DT9812 only responds to 32 byte writes!! */ in dt9812_write_multiple_registers()
317 /* DT9812 only responds to 32 byte writes!! */ in dt9812_rmw_multiple_registers()
/kernel/linux/linux-4.19/Documentation/w1/masters/
Domap-hdq24 difference between the HDQ and 1-wire mode is how the slave device responds to
/kernel/linux/linux-4.19/arch/powerpc/kernel/
Didle_power4.S54 /* Tell the tracer interrupts are on, because idle responds to them. */

123456789