Searched full:challenge (Results 1 – 21 of 21) sorted by relevance
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-arb-gpio-challenge.yaml | 4 $id: http://devicetree.org/schemas/i2c/i2c-arb-gpio-challenge.yaml#
7 title: GPIO-based I2C Arbitration Using a Challenge & Response Mechanism
14 This uses GPIO lines and a challenge & response mechanism to arbitrate who is
51 const: i2c-arb-gpio-challenge
106 compatible = "i2c-arb-gpio-challenge";
|
| /Documentation/admin-guide/ |
| D | thunderbolt.rst | 69 a challenge that should match the expected one based on a random key
148 Next time the device is plugged in the user can verify (challenge) the
154 If the challenge the device returns back matches the one we expect based
156 However, if the challenge fails no tunnels are created and error is
|
| /Documentation/arch/riscv/ |
| D | patch-acceptance.rst | 13 challenge for RISC-V Linux maintenance. Linux maintainers disapprove
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-thunderbolt | 91 2 Send a challenge based on the 32 byte hex string. If the
92 challenge response from device is valid, the device is
95 EKEYREJECTED if the challenge response did not match.
|
| /Documentation/livepatch/ |
| D | callbacks.rst | 113 example, commit 75ff39ccc1bd ("tcp: make challenge acks less predictable")
|
| /Documentation/networking/ |
| D | snmp_counter.rst | 833 The ACK is skipped if the ACK is a challenge ACK. The RFC 5961 defines
834 3 kind of challenge ACK, please refer `RFC 5961 section 3.2`_,
837 send challenge ACKs if the ACK number is before the first
981 Challenge ACK
983 For details of challenge ACK, please refer the explanation of
988 The number of challenge acks sent.
992 The number of challenge acks sent in response to SYN packets. After
993 updates this counter, the TCP stack might send a challenge ACK and
995 send the challenge and update the TcpExtTCPACKSkippedChallenge.
|
| D | rxrpc.rst | 139 requested, the server then issues a "challenge" and then the client
251 (#) Aborts, busy notifications and challenge packets are delivered by recvmsg,
274 in the keyring and then sends a challenge packet to the client and
|
| D | timestamping.rst | 355 timing of measurement are chosen correctly. This challenge is no
|
| D | ip-sysctl.rst | 1089 Limits number of Challenge ACK sent per second, as recommended
|
| /Documentation/core-api/ |
| D | printk-index.rst | 17 It is a huge challenge for maintaining the system log monitors. It requires
|
| /Documentation/scheduler/ |
| D | sched-rt-group.rst | 181 the biggest challenge as the current linux PI infrastructure is geared towards
|
| D | sched-util-clamp.rst | 134 level, which brings us to the main design challenge.
|
| /Documentation/dev-tools/ |
| D | testing-overview.rst | 9 when to use each of them can be a challenge. This document provides a rough
|
| /Documentation/admin-guide/thermal/ |
| D | intel_powerclamp.rst | 217 EOI for level triggered interrupts. But it is a challenge to be
|
| /Documentation/sound/designs/ |
| D | compress-offload.rst | 14 returned values in frames are the norm, making it a challenge to
|
| /Documentation/filesystems/ |
| D | seq_file.rst | 21 Creating those files correctly has always been a bit of a challenge,
|
| /Documentation/driver-api/ |
| D | xillybus.rst | 47 The challenge with FPGAs is that everything is implemented at a very low
|
| /Documentation/i2c/ |
| D | i2c-topology.rst | 380 i2c-arb-gpio-challenge Parent-locked
|
| /Documentation/virt/kvm/x86/ |
| D | mmu.rst | 84 The primary challenge is to encode between 1 and 3 translations into hardware
|
| D | timekeeping.rst | 557 Additionally, this lack of serialization from the TSC poses another challenge
|
| /Documentation/process/ |
| D | coding-style.rst | 916 Coming up with good debugging messages can be quite a challenge; and once
|