Home
last modified time | relevance | path

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

1234

/linux/Documentation/devicetree/bindings/display/
H A 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 */
H A Ddsi-controller.yaml62 channel that the peripheral responds to.
/linux/drivers/scsi/
H A Dscsi_devinfo.c64 {"HITACHI", "DK312C", "CM81", BLIST_NOLUN}, /* responds to all lun */
65 {"HITACHI", "DK314C", "CR21", BLIST_NOLUN}, /* responds to all lun */
74 {"MEDIAVIS", "RENO CD-ROMX2A", "2.03", BLIST_NOLUN}, /* responds to all lun */
75 {"MICROTEK", "ScanMakerIII", "2.30", BLIST_NOLUN}, /* responds to all lun */
77 {"PHILIPS", "PCA80SC", "V4-2", BLIST_NOLUN}, /* responds to all lun */
79 {"SUN", "SENA", NULL, BLIST_NOLUN}, /* responds to all luns */
90 {"SEAGATE", "ST296", "921", BLIST_NOLUN}, /* responds to all lun */
91 {"SEAGATE", "ST1581", "6538", BLIST_NOLUN}, /* responds to all lun */
104 {"TEAC", "MT-2ST/45S2-27", "RV M", BLIST_NOLUN}, /* responds to all lun */
113 {"MICROTEK", "ScanMaker II", "5.61", BLIST_NOLUN}, /* responds to all lun */
[all …]
/linux/drivers/net/dsa/mv88e6xxx/
H A 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
/linux/drivers/net/ethernet/intel/idpf/
H A Dvirtchnl2.h465 * PF/VF posts its version number to the CP. CP responds with its version number
500 * responds with the maximum VFs granted.
521 * CP responds with a virtchnl2_get_capabilities structure updated
524 * that can be created by this PF. For any other value 'n', CP responds
529 * value 'n', CP responds with a value <= n based on the CP's policy of
533 * It also responds with default number of vports that the dataplane driver
659 * CP responds with the updated virtchnl2_create_vport structure containing the
703 * CP responds with the status of the requested operation.
872 * CP responds with the same structure with the actual number of queues assigned
953 * structure is used to specify the number of vectors requested. CP responds
[all …]
/linux/drivers/block/rnbd/
H A DREADME65 RNBD_MSG_SESS_INFO to the server. Server responds with
71 Server responds to the message with RNBD_MSG_OPEN_RSP. This contains
/linux/drivers/media/dvb-frontends/
H A 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()
/linux/drivers/net/wwan/iosm/
H A Diosm_ipc_mux.c68 * It is a blocking function call, until CP responds or timeout. in ipc_mux_session_open_send()
106 * It is a blocking function call, until CP responds or timeout. in ipc_mux_session_open()
161 * It is a blocking function call, until CP responds or timeout. in ipc_mux_session_close()
/linux/Documentation/devicetree/bindings/rtc/
H A Disil,isl12026.yaml15 array responds at address 0x57. The "reg" property refers to the RTC
/linux/Documentation/devicetree/bindings/iio/adc/
H A Davia-hx711.yaml17 - dout-gpio is the sensor data the sensor responds to the clock
/linux/Documentation/hid/
H A 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
/linux/drivers/comedi/drivers/
H A Ddt9812.c258 /* DT9812 only responds to 32 byte writes!! */ in dt9812_read_info()
302 /* DT9812 only responds to 32 byte writes!! */ in dt9812_read_multiple_registers()
343 /* DT9812 only responds to 32 byte writes!! */ in dt9812_write_multiple_registers()
370 /* DT9812 only responds to 32 byte writes!! */ in dt9812_rmw_multiple_registers()
/linux/Documentation/w1/masters/
H A Domap-hdq.rst25 difference between the HDQ and 1-wire mode is how the slave device responds to
/linux/drivers/hwmon/
H A Dlm85.c214 * 1 -- PWM responds to Zone 1
215 * 2 -- PWM responds to Zone 2
216 * 3 -- PWM responds to Zone 3
217 * 23 -- PWM responds to the higher temp of Zone 2 or 3
218 * 123 -- PWM responds to highest of Zone 1, 2, or 3
221 * -2 -- PWM responds to manual control
724 case -2: /* PWM responds to manual control */ in pwm_enable_show()
/linux/Documentation/usb/
H A Draw-gadget.rst24 GadgetFS responds to some USB requests internally based on the provided
H A Dacm.rst131 device and try typing 'at'. If it responds with 'OK', then everything is
/linux/drivers/clk/sunxi/
H A Dclk-a20-gmac.c51 * driver then responds by auto-reparenting the clock.
/linux/Documentation/i2c/
H A Dsummary.rst50 A **target** chip is a node that responds to communications when addressed by a
/linux/Documentation/driver-api/usb/
H A Dtypec_bus.rst86 requires, a cable that responds to SOP Prime, and optionally SOP Double Prime
/linux/drivers/misc/eeprom/
H A Dmax6875.c19 * The MAX6875 ignores the lowest address bit, so each chip responds to
/linux/Documentation/arch/arm/
H A Dkernel_mode_neon.rst71 exception. The kernel responds by inspecting the VFP control registers and the
/linux/drivers/firmware/
H A Dthead,th1520-aon.c107 * * A negative error code if the mailbox send fails or if AON responds with
/linux/tools/testing/selftests/net/forwarding/
H A Dvxlan_bridge_1q_mc_ul.sh517 check_err_fail "$h3_should_fail" $? "H3 responds"
533 check_err_fail "$h3_should_fail" $? "H3 responds"
/linux/drivers/char/
H A Dpc8736x_gpio.c293 /* read the GPIO unit base addr that chip responds to */ in pc8736x_gpio_init()
/linux/include/uapi/linux/
H A Dhyperv.h101 * because the Linux VSS driver responds that it doesn't support

1234