Home
last modified time | relevance | path

Searched refs:ACK (Results 1 – 25 of 45) sorted by relevance

12

/Linux-v4.19/drivers/scsi/
D53c700.scr181 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 …]
D53c700_d.h_shipped238 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-v4.19/Documentation/translations/zh_CN/
Dstable_kernel_rules.txt46 - 如果补丁被接受到队列里,发送者会收到一个ACK回复,如果没有被接受,收
56 - 审查委员会有48小时的时间,用来决定给该补丁回复ACK还是NAK。
60 - 在审查周期结束的时候,那些得到ACK回应的补丁将会被加入到最新的稳定版
/Linux-v4.19/Documentation/translations/ja_JP/
Dstable_kernel_rules.txt55 - 送信者はパッチがキューに受け付けられた際には ACK を、却下された場合
70 - レビュー委員会は 48時間の間に ACK か NAK を出す。
74 - レビューサイクルの最後に、ACK を受けたパッチは最新の -stable リリー
/Linux-v4.19/Documentation/security/
DLSM-sctp.rst118 Called when a COOKIE ACK is received::
121 @skb - pointer to skbuff of the COOKIE ACK packet.
151 <----------------------------------------------- INIT ACK
159 <------------------------------------------- COOKIE ACK
DSELinux-sctp.rst88 Called when a COOKIE ACK is received where it sets the connection's peer sid
92 @skb - pointer to skbuff of the COOKIE ACK packet.
/Linux-v4.19/Documentation/i2c/
Dgpio-fault-injection56 it will stop at the ACK phase after the address of the client has been
57 transmitted. Because the device will ACK its presence, this results in SDA
69 The injector will again stop at one ACK phase, so the device will keep SDA low
74 b) after the address byte, a 0x00 byte will be transferred. Then, stop at ACK.
Dslave-interface156 About ACK/NACK
159 It is good behaviour to always ACK the address phase, so the master knows if a
161 state being busy is troublesome. SMBus demands to always ACK the address phase,
163 automatically ACK when detecting their slave addresses, so there is no option
167 Currently, there is no slave event to report if the master did ACK or NACK a
/Linux-v4.19/Documentation/input/devices/
Dwalkera0701.rst31 / 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-v4.19/Documentation/networking/
Drxrpc.txt146 (*) 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
197 (*) ACK'ing is handled by the protocol driver automatically, including ping
236 the reply is transmitted with one or more sendmsgs, and then the final ACK
334 RXRPC_ACK -rt n/a Final ACK received
364 This is delivered to a server application to indicate that the final ACK
[all …]
DPLIP.txt141 D3->ACK 5 - 10 10 - 5
176 INIT -> ACK 16 - 10
204 That raises the ACK line, triggering an interrupt in the receiving
205 machine. The receiving machine disables interrupts and raises its own ACK
Dproc_net_tcp.txt34 | | | | | | (delayed ACK control data)
Dmac80211-injection.txt29 an ACK even if it is a unicast frame
Drmnet.txt70 packets and either ACK the MAP command or deliver the IP packet to the
/Linux-v4.19/drivers/usb/gadget/udc/
Dgoku_udc.c1525 #define ACK(irqbit) { \ macro
1576 ACK(INT_SUSPEND); in goku_irq()
1613 ACK(INT_USBRESET); in goku_irq()
1624 ACK(INT_SETUP); in goku_irq()
1629 ACK(INT_STATUSNAK|INT_ENDPOINT0); in goku_irq()
1639 ACK(INT_ENDPOINT0); in goku_irq()
1647 ACK(INT_MSTRDEND); in goku_irq()
1653 ACK(INT_MSTWREND); in goku_irq()
1659 ACK(INT_MSTWRTMOUT); in goku_irq()
1693 #undef ACK
/Linux-v4.19/drivers/net/wireless/ath/ath9k/
DKconfig119 bool "Atheros ath9k ACK timeout estimation algorithm (EXPERIMENTAL)"
123 This option enables ath9k dynamic ACK timeout estimation algorithm
124 based on ACK frame RX timestamp, TX frame timestamp and frame
/Linux-v4.19/Documentation/
Dmailbox.txt66 /* An ACK to our last sample sent */
72 /* Remote f/w sends only ACK packets on this channel */
/Linux-v4.19/Documentation/scsi/
Dqlogicfas.txt71 that it gets a false ACK causing an extra byte to be inserted into the
73 termination (the ACK can be reflected), or by noise when the chips
/Linux-v4.19/drivers/media/pci/bt8xx/
Ddst_common.h95 #define ACK 0xff macro
/Linux-v4.19/drivers/usb/serial/
Dgarmin_gps.c98 #define ACK 0x06 macro
344 *ptr++ = ACK; in gsp_send_ack()
345 cksum += ACK; in gsp_send_ack()
511 if (data == ACK) { in gsp_receive()
512 ack_or_nak_seen = ACK; in gsp_receive()
/Linux-v4.19/Documentation/i2c/busses/
Di2c-mlxcpld45 Bit 4 - ACK/NACK.
/Linux-v4.19/Documentation/devicetree/bindings/mailbox/
Dfsl,mu.txt39 2 - TX doorbell channel. Without own register and no ACK support.
/Linux-v4.19/drivers/gpu/drm/amd/display/dc/core/
Ddc_link_dp.c1980 test_response.bits.ACK = 1; in handle_automated_test()
1988 test_response.bits.ACK = 0; in handle_automated_test()
1992 test_response.bits.ACK = 1; in handle_automated_test()
1996 test_response.bits.ACK = 1; in handle_automated_test()
2002 test_response.bits.ACK = 1; in handle_automated_test()
2004 if (test_response.bits.ACK) in handle_automated_test()
/Linux-v4.19/Documentation/process/
Dstable-kernel-rules.rst139 - The sender will receive an ACK when the patch has been accepted into the
153 - The review committee has 48 hours in which to ACK or NAK the patch.
/Linux-v4.19/drivers/staging/wilc1000/
Dcoreconfigurator.c30 ACK = 0xD4, enumerator

12