| /linux-6.15/net/tipc/ |
| H A D | discover.c | 210 bool respond = false; in tipc_disc_rcv() local
251 &maddr, &respond, &dupl_addr); in tipc_disc_rcv()
254 if (!respond) in tipc_disc_rcv()
|
| H A D | node.h | 96 bool *respond, bool *dupl_addr);
|
| /linux-6.15/Documentation/ABI/testing/ |
| H A D | sysfs-bus-fsi-devices-sbefifo | 6 timeout; i.e. the SBE did not respond within the time allotted
|
| H A D | sysfs-class-power-ltc4162l | 73 remain in this mode (and no longer respond to I2C commands)
|
| /linux-6.15/drivers/usb/gadget/function/ |
| H A D | f_hid.c | 888 goto respond; in hidg_setup()
896 goto respond; in hidg_setup()
906 goto respond; in hidg_setup()
921 goto respond; in hidg_setup()
931 goto respond; in hidg_setup()
949 goto respond; in hidg_setup()
957 goto respond; in hidg_setup()
978 respond: in hidg_setup()
|
| /linux-6.15/Documentation/devicetree/bindings/rtc/ |
| H A D | isil,isl12026.txt | 4 registers respond at bus address 0x6f, and the EEPROM array responds
|
| /linux-6.15/Documentation/devicetree/bindings/i2c/ |
| H A D | hpe,gxp-i2c.yaml | 34 arm and respond to interrupts from its engine. Each bit in the
|
| /linux-6.15/Documentation/block/ |
| H A D | null_blk.rst | 76 Whether or not to use a memory buffer to respond to IO requests
80 1 Use a memory buffer to respond to IO requests
|
| /linux-6.15/Documentation/devicetree/bindings/media/i2c/ |
| H A D | chrontel,ch7322.yaml | 42 the device will respond to power status requests with "standby"
|
| /linux-6.15/drivers/net/wwan/iosm/ |
| H A D | iosm_ipc_mux_codec.h | 280 size_t res_size, bool blocking, bool respond);
|
| /linux-6.15/Documentation/i2c/ |
| H A D | slave-testunit-backend.rst | 137 Partial command. This test will respond to a block process call as defined by
170 128 bytes. However, it will only respond if the read message is connected to
230 If the host does not respond to the alert within 1 second, the test will be
|
| H A D | ten-bit-addresses.rst | 8 address 0x10 (though a single device could respond to both of them).
|
| H A D | i2c-stub.rst | 16 quick commands to the specified addresses; it will respond to the other
|
| /linux-6.15/Documentation/driver-api/xilinx/ |
| H A D | eemi.rst | 17 device to issue or respond to power management requests.
|
| /linux-6.15/drivers/media/usb/dvb-usb-v2/ |
| H A D | dvbsky.c | 350 u8 command[4], respond[2], command_size, respond_size; in dvbsky_ci_ctrl() local
365 respond, respond_size); in dvbsky_ci_ctrl()
369 *mem = respond[1]; in dvbsky_ci_ctrl()
|
| /linux-6.15/Documentation/devicetree/bindings/input/touchscreen/ |
| H A D | ti,tsc2005.yaml | 44 if the touchscreen does not respond after the configured time
|
| /linux-6.15/Documentation/w1/masters/ |
| H A D | omap-hdq.rst | 29 does not respond with a presence pulse as it does in the 1-Wire protocol.
|
| /linux-6.15/Documentation/process/ |
| H A D | 6.Followthrough.rst | 44 impulse to respond in kind. Code review is about the code, not about
66 that the reviewer is asking you to fix. And respond back to the reviewer:
184 respond to these reports is a matter of basic pride in your work. If that
216 really only one way to respond: be pleased that your problem got solved and
|
| /linux-6.15/Documentation/devicetree/bindings/display/ |
| H A D | dsi-controller.yaml | 60 peripherals respond to more than a single virtual channel. In that
|
| /linux-6.15/Documentation/driver-api/pldmfw/ |
| H A D | index.rst | 66 the device. For each component, the firmware may respond with an
|
| /linux-6.15/Documentation/maintainer/ |
| H A D | feature-and-driver-maintainers.rst | 34 reviewers should try to respond quicker than what is the usual patch
81 Maintainers furthermore should respond to reports about other kinds of
|
| /linux-6.15/Documentation/scsi/ |
| H A D | megaraid.rst | 10 Different classes of controllers from LSI Logic accept and respond to the
|
| /linux-6.15/Documentation/filesystems/ |
| H A D | befs.rst | 34 respond to the address given above...
|
| /linux-6.15/Documentation/usb/ |
| H A D | raw-gadget.rst | 25 descriptors. Note that the UDC driver might respond to some requests on
|
| /linux-6.15/Documentation/hwmon/ |
| H A D | pmbus-core.rst | 336 Some PMBus chips respond with valid data when trying to read an unsupported
354 Some PMBus chips don't respond with valid data when reading the CAPABILITY
372 Some PMBus chips respond with invalid data when reading the WRITE_PROTECT
|