| /linux-4.1.27/net/tipc/ |
| D | discover.c | 143 bool respond = false; in tipc_disc_rcv() local
187 respond = true; in tipc_disc_rcv()
205 respond = true; in tipc_disc_rcv()
224 respond = true; in tipc_disc_rcv()
236 respond = true; in tipc_disc_rcv()
249 respond = false; in tipc_disc_rcv()
254 if (respond && (mtyp == DSC_REQ_MSG)) { in tipc_disc_rcv()
|
| /linux-4.1.27/drivers/usb/misc/ |
| D | ftdi-elan.c | 159 struct u132_respond respond[RESPOND_SIZE]; member
338 struct u132_respond *respond = &ftdi->respond[RESPOND_MASK & in ftdi_elan_abandon_completions() local
340 *respond->result = -ESHUTDOWN; in ftdi_elan_abandon_completions()
341 *respond->value = 0; in ftdi_elan_abandon_completions()
342 complete(&respond->wait_completion); in ftdi_elan_abandon_completions()
1071 struct u132_respond *respond = &ftdi->respond[ in ftdi_elan_respond_engine() local
1080 *respond->value = data; in ftdi_elan_respond_engine()
1081 *respond->result = 0; in ftdi_elan_respond_engine()
1082 complete(&respond->wait_completion); in ftdi_elan_respond_engine()
1360 struct u132_respond *respond = &ftdi->respond[ in ftdi_elan_read_reg() local
[all …]
|
| /linux-4.1.27/Documentation/misc-devices/ |
| D | eeprom | 59 The other devices will not be found on a DIMM because they respond to more
71 does not respond to byte reads. If this register is present, the lower 128
74 device will no longer respond at the 0x30-37 address. The eeprom driver
|
| /linux-4.1.27/Documentation/devicetree/bindings/input/touchscreen/ |
| D | tsc2005.txt | 14 - ti,esd-recovery-timeout-ms : integer, if the touchscreen does not respond after
|
| /linux-4.1.27/Documentation/i2c/ |
| D | ten-bit-addresses | 4 address 0x10 (though a single device could respond to both of them).
|
| D | i2c-stub | 13 quick commands to the specified addresses; it will respond to the other
|
| D | fault-codes | 18 to respond correctly. Other code may need to rely on YOUR code reporting
|
| /linux-4.1.27/Documentation/devicetree/bindings/iio/ |
| D | st-sensors.txt | 9 - reg: the I2C or SPI address the device will respond to
|
| /linux-4.1.27/drivers/usb/gadget/function/ |
| D | f_hid.c | 415 goto respond; in hidg_setup()
451 goto respond; in hidg_setup()
459 goto respond; in hidg_setup()
480 respond: in hidg_setup()
|
| /linux-4.1.27/Documentation/devicetree/bindings/mfd/ |
| D | cros-ec.txt | 23 between transactions is not long enough the EC may not be able to respond
|
| /linux-4.1.27/Documentation/w1/masters/ |
| D | omap-hdq | 28 does not respond with a presence pulse as it does in the 1-Wire protocol.
|
| /linux-4.1.27/drivers/media/usb/dvb-usb-v2/ |
| D | dvbsky.c | 391 u8 command[4], respond[2], command_size, respond_size; in dvbsky_ci_ctrl() local
406 respond, respond_size); in dvbsky_ci_ctrl()
410 *mem = respond[1]; in dvbsky_ci_ctrl()
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 6.Followthrough | 40 impulse to respond in kind. Code review is about the code, not about
55 that the reviewer is asking you to fix. And respond back to the reviewer:
172 respond to these reports is a matter of basic pride in your work. If that
203 really only one way to respond: be pleased that your problem got solved and
|
| D | 5.Posting | 173 changed, detail those changes and how other developers should respond. In
|
| D | 4.Coding | 396 a change that they need to respond to. Supporting out-of-tree code is not
|
| /linux-4.1.27/Documentation/devicetree/bindings/mipi/dsi/ |
| D | mipi-dsi-bus.txt | 43 Some DSI peripherals respond to more than a single virtual channel. In that
|
| /linux-4.1.27/Documentation/scsi/ |
| D | megaraid.txt | 7 Different classes of controllers from LSI Logic accept and respond to the
|
| D | BusLogic.txt | 283 respond to synchronous transfer negotiation for UltraSCSI speed. AutoSCSI
299 The BT-948/958/958D will not respond to any of the ISA compatible I/O ports
300 that previous BusLogic SCSI Host Adapters respond to. This driver supports
348 UltraSCSI operation, or where existing SCSI devices do not properly respond
490 respond correctly when Logical Units above 0 are addressed.
|
| D | scsi_mid_low_api.txt | 127 will respond to a sysfs probe() callback that indicates an HBA has been
142 scsi devices of which only the first 2 respond:
165 respond, a slave_alloc(), slave_destroy() pair is called.
252 finds 1 SCSI device (and a second device does not respond).
279 respond, a slave_alloc(), slave_destroy() pair is called.
748 ioctl - driver can respond to ioctls
945 * ioctl - driver can respond to ioctls
|
| D | ChangeLog.megaraid_sas | 371 a max of 60 seconds to respond to the INIT cmd.
405 10. FW may take a max of 60 seconds to respond to the INIT
|
| D | aic7xxx.txt | 51 8. Multiple Target IDs - Allows the controller to respond to selection
|
| /linux-4.1.27/Documentation/input/ |
| D | alps.txt | 30 All ALPS touchpads should respond to the "E6 report" command sequence:
31 E8-E6-E6-E6-E9. An ALPS touchpad should respond with either 00-00-0A or
52 EC-EC-EC-E9 places the device in command mode, and the device will respond
|
| D | iforce-protocol.txt | 166 The device should respond by sending the number of effects that can be played
|
| D | joystick-parport.txt | 468 respond try raising it until they work. Setting the type to 8 allows the
|
| D | sentelic.txt | 13 @5. FSP will respond 0x04.
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | befs.txt | 28 respond to the address given above...
|
| /linux-4.1.27/Documentation/hid/ |
| D | uhid.txt | 48 register the device. UHID will respond with an UHID_START event. You can now
171 parallel. However, if you fail to respond with a UHID_GET_REPORT_REPLY, the
|
| /linux-4.1.27/Documentation/usb/ |
| D | gadget_multi.txt | 142 [6] To put it in some other nice words, Windows failed to respond to
|
| D | error-codes.txt | 108 error, a failure to respond (often caused by
|
| D | ehci.txt | 142 controller can process requests, and how fast devices can respond to
|
| D | power-management.txt | 559 connection with its device, not respond to hotplug events, and not
560 respond to remote wakeup events*.
706 not respond to new connect events.
|
| /linux-4.1.27/Documentation/ |
| D | flexible-arrays.txt | 6 Kernel programmers will sometimes respond to this problem by allocating
|
| D | SubmittingDrivers | 38 maintainer does not respond or you cannot find the appropriate
|
| D | parport.txt | 175 for the peripheral to respond. You might find that
|
| D | intel_txt.txt | 108 - Because the processors will not respond to an INIT or SIPI when
|
| D | sysrq.txt | 6 It is a 'magical' key combo you can hit which the kernel will respond to
|
| D | SubmittingPatches | 371 which the patch can be improved. You must respond to those comments;
379 reviewers sometimes get grumpy. Even in that case, though, respond
|
| D | HOWTO | 396 If multiple people respond to your mail, the CC: list of recipients may
|
| D | kernel-parameters.txt | 4041 unnecessary even if the host did not respond to
|
| /linux-4.1.27/Documentation/networking/ |
| D | xfrm_sync.txt | 131 or kernel to announce events or respond to a XFRM_MSG_GETAE.
|
| D | e100.txt | 157 will respond to IP traffic for any IP address assigned to the system.
|
| D | rds.txt | 345 respond to pings
|
| D | vortex.txt | 160 The 3com cards appear to only respond to PAUSE frames which are
|
| D | ixgb.txt | 394 will respond to IP traffic for any IP address assigned to the system.
|
| D | ip-sysctl.txt | 1048 of which cards (usually 1) will respond to an arp request.
1050 0 - (default) The kernel can respond to arp requests with addresses
|
| D | bonding.txt | 958 It will respond with a line of text starting with either
|
| /linux-4.1.27/Documentation/scheduler/ |
| D | sched-rt-group.txt | 62 have to play some music and respond to input, leaving it with around 80% CPU
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | configfs-usb-gadget-uvc | 255 bTriggerUsage - how the host software will respond to
|
| /linux-4.1.27/Documentation/isdn/ |
| D | INTERFACE | 322 HL-driver should respond to ALL incoming calls,
351 Service-Indicators it will respond to.
658 With this call, the driver has to respond to a prior ISDN_CMD_DIAL, if
|
| D | README.sc | 165 problems, but the board would not respond beyond that point. When a check was
|
| /linux-4.1.27/ |
| D | REPORTING-BUGS | 159 In general, kernel maintainers take 1 to 5 business days to respond to
|
| D | MAINTAINERS | 65 does not respond.
|
| /linux-4.1.27/fs/ocfs2/dlm/ |
| D | dlmdomain.c | 833 goto respond; in dlm_query_join_handler()
920 respond: in dlm_query_join_handler()
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | pmbus-core | 274 Some PMBus chips respond with valid data when trying to read an unsupported
|
| /linux-4.1.27/Documentation/PCI/ |
| D | pci.txt | 438 "unhooked" device asserts IRQ line, the system will respond assuming
632 expected to not respond to a readl(). Most x86 platforms will allow
|
| /linux-4.1.27/Documentation/s390/ |
| D | 3270.txt | 103 3270s, and this enables the tub3270 driver once loaded to respond
|
| /linux-4.1.27/Documentation/power/ |
| D | freezing-of-tasks.txt | 190 fail, because the user land process that should respond to the request is frozen
|
| D | pci.txt | 105 (i.e. the device is required to respond to PCI configuration accesses), although
|
| /linux-4.1.27/Documentation/sysctl/ |
| D | kernel.txt | 428 The hard lockup detector monitors each CPU for its ability to respond to
837 from running. The mechanism depends on the CPUs ability to respond to timer
|
| /linux-4.1.27/drivers/staging/fwserial/ |
| D | fwserial.c | 630 goto respond; in fwtty_port_handler()
667 respond: in fwtty_port_handler()
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | videobuf | 237 The V4L2 API includes a very long list of driver callbacks to respond to
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | pci_iov_resource_on_powernv.txt | 268 respond to segments [0, total_VFs - 1]. There's nothing in hardware that
|
| /linux-4.1.27/Documentation/filesystems/configfs/ |
| D | configfs.txt | 33 kernel modules backing the items must respond to this.
|
| /linux-4.1.27/Documentation/filesystems/cifs/ |
| D | README | 518 server to respond to the write. Since SMB Flush can be
|
| /linux-4.1.27/drivers/scsi/aic7xxx/ |
| D | aic79xx.reg | 1792 * Bitmask of ids to respond as a target.
|
| D | aic7xxx.seq | 939 * and respond as quickly as possible to the standard
|
| D | aic79xx.seq | 1701 * and respond as quickly as possible to the standard
|
| /linux-4.1.27/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 974 only acting as a gateway. It will respond to pings sent to it
|