| /linux/Documentation/devicetree/bindings/display/ |
| H A 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 */
|
| H A D | dsi-controller.yaml | 62 channel that the peripheral responds to.
|
| /linux/drivers/net/dsa/mv88e6xxx/ |
| H A 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/drivers/block/rnbd/ |
| H A 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/include/linux/net/intel/ |
| H A D | virtchnl2.h | 465 * 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/media/dvb-frontends/ |
| H A 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/Documentation/devicetree/bindings/rtc/ |
| H A D | isil,isl12026.yaml | 15 array responds at address 0x57. The "reg" property refers to the RTC
|
| /linux/drivers/net/wwan/iosm/ |
| H A D | iosm_ipc_mux.c | 68 * 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/hid/ |
| H A 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/drivers/comedi/drivers/ |
| H A D | dt9812.c | 258 /* 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/usb/ |
| H A D | raw-gadget.rst | 24 GadgetFS responds to some USB requests internally based on the provided
|
| H A D | acm.rst | 131 device and try typing 'at'. If it responds with 'OK', then everything is
|
| /linux/drivers/clk/sunxi/ |
| H A D | clk-a20-gmac.c | 51 * driver then responds by auto-reparenting the clock.
|
| /linux/Documentation/i2c/ |
| H A D | summary.rst | 50 A **target** chip is a node that responds to communications when addressed by a
|
| /linux/Documentation/driver-api/usb/ |
| H A D | typec_bus.rst | 86 requires, a cable that responds to SOP Prime, and optionally SOP Double Prime
|
| /linux/drivers/iio/dac/ |
| H A D | ad5706r.c | 93 /* Full duplex, device responds immediately after command */ in ad5706r_regmap_read()
|
| /linux/drivers/firmware/ |
| H A D | thead,th1520-aon.c | 107 * * A negative error code if the mailbox send fails or if AON responds with
|
| /linux/drivers/char/ |
| H A D | pc8736x_gpio.c | 293 /* read the GPIO unit base addr that chip responds to */ in pc8736x_gpio_init()
|
| /linux/include/uapi/linux/ |
| H A D | hyperv.h | 101 * because the Linux VSS driver responds that it doesn't support
|
| /linux/tools/testing/selftests/net/forwarding/ |
| H A D | vxlan_bridge_1q_mc_ul.sh | 517 check_err_fail "$h3_should_fail" $? "H3 responds"
533 check_err_fail "$h3_should_fail" $? "H3 responds"
|
| /linux/sound/soc/codecs/ |
| H A D | cx20442.c | 229 /* Actual setup will be performed after the modem responds. */ in v253_open()
|
| /linux/Documentation/core-api/real-time/ |
| H A D | hardware.rst | 66 CPU until the device responds.
|
| /linux/tools/power/x86/turbostat/ |
| H A D | turbostat.8 | 222 \fBPKG_%\fP percent of the interval that RAPL throttling was active on the Package. Note that the system summary is the sum of the package throttling time, and thus may be higher than 100% on a multi-package system. Note that the meaning of this field is model specific. For example, some hardware increments this counter when RAPL responds to thermal limits, but does not increment this counter when RAPL responds to power limits. Comparing PkgWatt and PkgTmp to system limits is necessary.
|
| /linux/drivers/media/usb/gspca/ |
| H A D | stk014.c | 221 /* check if the device responds */ in sd_init()
|
| /linux/drivers/usb/gadget/ |
| H A D | Kconfig | 455 responds UMP Stream messages for UMP Endpoint and Function
|