| /linux-6.6.21/drivers/scsi/ |
| D | 53c700.scr | 181 CLEAR ACK
195 CLEAR ACK
199 CLEAR ACK
208 CLEAR ACK
212 CLEAR ACK
216 CLEAR ACK
220 CLEAR ACK
224 CLEAR ACK
232 CLEAR ACK
240 CLEAR ACK
[all …]
|
| D | 53c700_d.h_shipped | 238 CLEAR ACK
267 CLEAR ACK
280 CLEAR ACK
313 CLEAR ACK
326 CLEAR ACK
339 CLEAR ACK
352 CLEAR ACK
365 CLEAR ACK
382 CLEAR ACK
399 CLEAR ACK
[all …]
|
| /linux-6.6.21/Documentation/translations/zh_CN/process/ |
| D | stable-kernel-rules.rst | 42 - 如果补丁被接受到队列里，发送者会收到一个ACK回复，如果没有被接受，收
53 - 审查委员会有48小时的时间，用来决定给该补丁回复ACK还是NAK。
57 - 在审查周期结束的时候，那些得到ACK回应的补丁将会被加入到最新的稳定版
|
| /linux-6.6.21/Documentation/translations/zh_TW/process/ |
| D | stable-kernel-rules.rst | 45 - 如果補丁被接受到隊列里，發送者會收到一個ACK回復，如果沒有被接受，收
56 - 審查委員會有48小時的時間，用來決定給該補丁回復ACK還是NAK。
60 - 在審查周期結束的時候，那些得到ACK回應的補丁將會被加入到最新的穩定版
|
| /linux-6.6.21/Documentation/networking/ |
| D | snmp_counter.rst | 275 it excludes the retransmitted packets. But it includes the SYN, ACK
296 It means the TCP layer receives a SYN, replies a SYN+ACK, come into
329 TCPSynRetrans: number of SYN and SYN/ACK retransmits to break down
359 half open queue, TCP stack will send SYN+ACK on an exponential backoff
360 timer, after client replies ACK, TCP stack checks whether the accept
363 time client replies ACK, this socket will get another chance to move
450 If a packet set ACK flag and has no data, it is a pure ACK packet, if
457 If a TCP packet has data (which means it is not a pure ACK packet),
537 approached. The two pieces of information are ACK train length and
539 `Hybrid Slow Start paper`_. Either ACK train length or packet delay
[all …]
|
| D | rxrpc.rst | 146 (#) Calls use ACK packets to handle reliability. Data packets are also
150 A hard-ACK indicates to the far side that all the data received to a point
151 has been received and processed; a soft-ACK indicates that the data has
153 not discard any transmittable packets until they've been hard-ACK'd.
155 (#) Reception of a reply data packet implicitly hard-ACK's all the data
159 received and the final hard-ACK on the last packet of the reply has
196 (#) ACK'ing is handled by the protocol driver automatically, including ping
235 the reply is transmitted with one or more sendmsgs, and then the final ACK
333 RXRPC_ACK -rt n/a Final ACK received
364 This is delivered to a server application to indicate that the final ACK
[all …]
|
| D | plip.rst | 145 D3->ACK 5 - 10 10 - 5
181 INIT -> ACK 16 - 10
211 That raises the ACK line, triggering an interrupt in the receiving
212 machine. The receiving machine disables interrupts and raises its own ACK
|
| /linux-6.6.21/Documentation/devicetree/bindings/dma/ |
| D | st,stm32-dma.yaml | 44 0x0: Use standard DMA ACK management, where ACK signal is maintained
46 0x1: Use alternative DMA ACK management, where ACK de-assertion does
47 not wait for the de-assertion of the REQuest, ACK is only managed
|
| /linux-6.6.21/Documentation/translations/ja_JP/ |
| D | stable_kernel_rules.txt | 55 - 送信者はパッチがキューに受け付けられた際には ACK を、却下された場合
70 - レビュー委員会は 48時間の間に ACK か NAK を出す。
74 - レビューサイクルの最後に、ACK を受けたパッチは最新の -stable リリー
|
| /linux-6.6.21/tools/testing/selftests/bpf/prog_tests/ |
| D | cls_redirect.c | 184 ACK, enumerator
233 else if (test->flags == ACK) in test_str()
242 { TCP, ACCEPT, UNKNOWN_CONN, NO_HOPS, ACK },
243 { TCP, FORWARD, UNKNOWN_CONN, ONE_HOP, ACK },
244 { TCP, ACCEPT, KNOWN_CONN, ONE_HOP, ACK },
342 if (test->flags == ACK) in build_input()
|
| /linux-6.6.21/Documentation/input/devices/ |
| D | walkera0701.rst | 31 / O 4 3 O \ pin 3 (GND) LED ________________ 10 ACK
55 Driver use interrupt from parport ACK input bit to measure pulse length
98 (Warning, pulses on ACK are inverted by transistor, irq is raised up on sync
|
| /linux-6.6.21/Documentation/security/ |
| D | SCTP.rst | 124 Called when a COOKIE ACK is received, and the peer secid will be
128 @skb - pointer to skbuff of the COOKIE ACK packet.
159 <----------------------------------------------- INIT ACK
170 <------------------------------------------- COOKIE ACK
274 Called when a COOKIE ACK is received where it sets the connection's peer sid
278 @skb - pointer to skbuff of the COOKIE ACK packet.
|
| /linux-6.6.21/Documentation/driver-api/surface_aggregator/ |
| D | ssh.rst | 10 .. |ACK| replace:: ``ACK`` substdef
119 * - |ACK|
131 Both |NAK|- and |ACK|-type frames are used to control flow of messages and
144 the frame by responding with a message containing an |ACK|-type frame with
146 the |ACK| frame specifies the |DATA| frame to be acknowledged. In case of an
158 used to associate an ``ACK`` with its ``DATA_SEQ``-type frame, but not
169 indicates a |DATA_SEQ|-type frame, ``FRAME(A)`` an ``ACK``-type frame,
334 the EC is sent again, e.g. due to the host not receiving an |ACK|, the EC
|
| /linux-6.6.21/drivers/gpu/drm/amd/display/dc/link/accessories/ |
| D | link_dp_cts.c | 605 test_response.bits.ACK = 1; in dp_handle_automated_test()
613 test_response.bits.ACK = 0; in dp_handle_automated_test()
633 test_response.bits.ACK = dm_helpers_dp_handle_test_pattern_request(link->ctx, link, in dp_handle_automated_test()
639 test_response.bits.ACK = 1; in dp_handle_automated_test()
644 test_response.bits.ACK = 1; in dp_handle_automated_test()
648 if (test_response.bits.ACK) in dp_handle_automated_test()
|
| /linux-6.6.21/Documentation/i2c/ |
| D | slave-interface.rst | 165 About ACK/NACK
168 It is good behaviour to always ACK the address phase, so the master knows if a
170 state being busy is troublesome. SMBus demands to always ACK the address phase,
172 automatically ACK when detecting their slave addresses, so there is no option
176 Currently, there is no slave event to report if the master did ACK or NACK a
|
| D | gpio-fault-injection.rst | 60 it will stop at the ACK phase after the address of the client has been
61 transmitted. Because the device will ACK its presence, this results in SDA
73 The injector will again stop at one ACK phase, so the device will keep SDA low
78 b) after the address byte, a 0x00 byte will be transferred. Then, stop at ACK.
|
| /linux-6.6.21/drivers/usb/gadget/udc/ |
| D | goku_udc.c | 1529 #define ACK(irqbit) { \ macro
1580 ACK(INT_SUSPEND); in goku_irq()
1617 ACK(INT_USBRESET); in goku_irq()
1628 ACK(INT_SETUP); in goku_irq()
1633 ACK(INT_STATUSNAK|INT_ENDPOINT0); in goku_irq()
1643 ACK(INT_ENDPOINT0); in goku_irq()
1651 ACK(INT_MSTRDEND); in goku_irq()
1657 ACK(INT_MSTWREND); in goku_irq()
1663 ACK(INT_MSTWRTMOUT); in goku_irq()
1697 #undef ACK
|
| /linux-6.6.21/Documentation/core-api/ |
| D | netlink.rst | 35 not via the ACK. Try to find useful data to return. Once the command is
36 added whether it replies with a full message or only an ACK is uAPI and
|
| /linux-6.6.21/include/rdma/ |
| D | tid_rdma_defs.h | 94 IB_OPCODE(TID_RDMA, ACK),
|
| /linux-6.6.21/Documentation/driver-api/ |
| D | mailbox.rst | 66 /* An ACK to our last sample sent */
72 /* Remote f/w sends only ACK packets on this channel */
|
| /linux-6.6.21/drivers/net/wireless/ath/ath9k/ |
| D | Kconfig | 118 bool "Atheros ath9k ACK timeout estimation algorithm"
122 This option enables ath9k dynamic ACK timeout estimation algorithm
123 based on ACK frame RX timestamp, TX frame timestamp and frame
|
| /linux-6.6.21/Documentation/devicetree/bindings/misc/ |
| D | olpc,xo1.75-ec.yaml | 16 response data) by strobing the ACK pin with the ready signal. See the
|
| /linux-6.6.21/drivers/usb/serial/ |
| D | garmin_gps.c | 98 #define ACK 0x06 macro
347 *ptr++ = ACK; in gsp_send_ack()
348 cksum += ACK; in gsp_send_ack()
514 if (data == ACK) { in gsp_receive()
515 ack_or_nak_seen = ACK; in gsp_receive()
|
| /linux-6.6.21/drivers/media/pci/bt8xx/ |
| D | dst_common.h | 83 #define ACK 0xff macro
|
| /linux-6.6.21/Documentation/scsi/ |
| D | qlogicfas.rst | 80 that it gets a false ACK causing an extra byte to be inserted into the
82 termination (the ACK can be reflected), or by noise when the chips
|