| /Linux-v5.10/Documentation/devicetree/bindings/display/ |
| D | mipi-dsi-bus.txt | 58 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 */
|
| D | dsi-controller.yaml | 53 channel that the peripheral responds to.
|
| /Linux-v5.10/drivers/scsi/ |
| D | scsi_devinfo.c | 65 {"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 …]
|
| /Linux-v5.10/drivers/net/dsa/mv88e6xxx/ |
| D | smi.c | 17 * 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-v5.10/drivers/block/rnbd/ |
| D | README | 65 RNBD_MSG_SESS_INFO to the server. Server responds with
71 Server responds to the message with RNBD_MSG_OPEN_RSP. This contains
|
| /Linux-v5.10/Documentation/admin-guide/cgroup-v1/ |
| D | freezer-subsystem.rst | 45 responds to them.
47 Another example of a program which catches and responds to these
|
| /Linux-v5.10/Documentation/misc-devices/ |
| D | eeprom.rst | 71 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
|
| /Linux-v5.10/Documentation/hid/ |
| D | intel-ish-hid.rst | 195 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,
|
| D | uhid.rst | 69 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-v5.10/Documentation/devicetree/bindings/rtc/ |
| D | isil,isl12026.txt | 4 registers respond at bus address 0x6f, and the EEPROM array responds
|
| /Linux-v5.10/drivers/media/dvb-frontends/ |
| D | l64781.c | 510 * 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-v5.10/Documentation/networking/device_drivers/ethernet/marvell/ |
| D | octeontx2.rst | 105 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
|
| /Linux-v5.10/Documentation/devicetree/bindings/iio/adc/ |
| D | avia-hx711.yaml | 17 - dout-gpio is the sensor data the sensor responds to the clock
|
| /Linux-v5.10/drivers/staging/comedi/drivers/ |
| D | dt9812.c | 248 /* 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()
|
| /Linux-v5.10/Documentation/w1/masters/ |
| D | omap-hdq.rst | 25 difference between the HDQ and 1-wire mode is how the slave device responds to
|
| /Linux-v5.10/Documentation/i2c/ |
| D | summary.rst | 51 A **slave** chip is a node that responds to communications when addressed
|
| /Linux-v5.10/drivers/net/wireless/intersil/orinoco/ |
| D | fw.c | 201 * the card and make sure it responds. For the secondary firmware take
263 /* Reset hermes chip and make sure it responds */ in symbol_dl_image()
|
| /Linux-v5.10/Documentation/usb/ |
| D | raw-gadget.rst | 19 GadgetFS responds to some USB requests internally based on the provided
|
| /Linux-v5.10/drivers/clk/sunxi/ |
| D | clk-a20-gmac.c | 40 * driver then responds by auto-reparenting the clock.
|
| /Linux-v5.10/drivers/hwmon/ |
| D | lm85.c | 214 * 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-v5.10/Documentation/driver-api/usb/ |
| D | typec_bus.rst | 86 requires, a cable that responds to SOP Prime, and optionally SOP Double Prime
|
| /Linux-v5.10/drivers/misc/eeprom/ |
| D | max6875.c | 19 * The MAX6875 ignores the lowest address bit, so each chip responds to
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | md.rst | 528 This file responds to select/poll. Any change to ``faulty``
657 This file responds to select/poll. Any important change in the value
668 This file responds to select/poll, any increase or decrease
|
| /Linux-v5.10/drivers/video/backlight/ |
| D | apple_bl.c | 162 /* Check that the hardware responds - this may not work under EFI */ in apple_bl_add()
|
| /Linux-v5.10/Documentation/arm/ |
| D | kernel_mode_neon.rst | 71 exception. The kernel responds by inspecting the VFP control registers and the
|
