| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | isl68137.rst | 25 Publicly available (after August 2020 launch) at the Renesas website
35 Publicly available (after August 2020 launch) at the Renesas website
45 Publicly available (after August 2020 launch) at the Renesas website
55 Publicly available (after August 2020 launch) at the Renesas website
65 Publicly available (after August 2020 launch) at the Renesas website
75 Publicly available (after August 2020 launch) at the Renesas website
85 Publicly available (after August 2020 launch) at the Renesas website
95 Publicly available (after August 2020 launch) at the Renesas website
105 Publicly available (after August 2020 launch) at the Renesas website
115 Publicly available (after August 2020 launch) at the Renesas website
[all …]
|
| /kernel/linux/linux-5.10/drivers/greybus/ |
| D | greybus_trace.h | 60 * Occurs after an incoming request message has been received
65 * Occurs after an incoming response message has been received,
66 * after its matching request has been found.
71 * Occurs after an operation has been canceled, possibly before the
78 * been queued for sending, this occurs after it is sent.
127 * Occurs after a new operation is created for an outgoing request
133 * Occurs after a new core operation has been created.
138 * Occurs after a new operation has been created for an incoming
150 * Occurs when an operation has been marked active, after updating
199 * Occurs after a new connection is successfully created.
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/wireguard/ |
| D | timers.c | 13 * - Timer for retransmitting the handshake if we don't hear back after
16 * - Timer for sending empty packet if we have received a packet but after have
19 * - Timer for initiating new handshake if we have sent a packet but after have
23 * - Timer for zeroing out all ephemeral keys after `(REJECT_AFTER_TIME * 3)` ms
47 pr_debug("%s: Handshake for peer %llu (%pISpfsc) did not complete after %d attempts, giving up\n", in wg_expired_retransmit_handshake()
65 …pr_debug("%s: Handshake for peer %llu (%pISpfsc) did not complete after %d seconds, retrying (try … in wg_expired_retransmit_handshake()
95 …pr_debug("%s: Retrying handshake with peer %llu (%pISpfsc) because we stopped hearing back after %… in wg_expired_new_handshake()
144 /* Should be called after an authenticated data packet is sent. */
153 /* Should be called after an authenticated data packet is received. */
165 /* Should be called after any type of authenticated packet is sent, whether
[all …]
|
| /kernel/linux/linux-5.10/scripts/ |
| D | config | 29 --enable-after|-E beforeopt option
30 Enable option directly after other option
31 --disable-after|-D beforeopt option
32 Disable option directly after other option
33 --module-after|-M beforeopt option
34 Turn option into module directly after other option
85 local after="$2"
89 sed -e "s$SED_DELIM$before$SED_DELIM$after$SED_DELIM" "$infile" >"$tmpfile"
152 --*-after|-E|-D|-M)
208 --enable-after|-E)
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/media_tests/ |
| D | regression_test.txt | 2 and unregister paths. There have a few problems that result in user-after
18 Regressions test for cdev user-after free error on /dev/mediaX when driver
22 and cdev user-after-free fixes. This opens media dev files and sits in
35 device file goes away after unbind, device file name changes. Start the
37 after unbind, /dev/media1 or /dev/media2 could get created. The idea is
43 Run dmesg looking for any user-after free errors or mutex lock errors.
|
| /kernel/linux/linux-5.10/include/linux/usb/ |
| D | typec_dp.h | 28 TYPEC_DP_STATE_A = TYPEC_STATE_MODAL, /* Not supported after v1.0b */
29 TYPEC_DP_STATE_B, /* Not supported after v1.0b */
33 TYPEC_DP_STATE_F, /* Not supported after v1.0b */
53 DP_PIN_ASSIGN_A, /* Not supported after v1.0b */
54 DP_PIN_ASSIGN_B, /* Not supported after v1.0b */
58 DP_PIN_ASSIGN_F, /* Not supported after v1.0b */
71 #define DP_CAP_GEN2 BIT(3) /* Reserved after v1.0b */
96 #define DP_CONF_SIGNALING_GEN_2 BIT(3) /* Reserved after v1.0b */
|
| /kernel/linux/linux-5.10/drivers/platform/mellanox/ |
| D | mlxbf-bootctl.h | 10 * Request that the on-chip watchdog be enabled, or disabled, after
14 * will not be enabled after the next soft reset. Non-zero errors are
21 * after the next chip soft reset. Returns the interval as set by
46 * after the next soft reset. For a specified valid boot mode, the
48 * MLXBF_BOOTCTL_SET_RESET_ACTION after the next chip soft reset; in
49 * particular, after that reset, the action for the now next reset can
53 * MLXBF_BOOTCTL_SET_RESET_ACTION be taken after the next chip soft reset.
61 * reset after the next soft reset; this will be one of the valid
|
| /kernel/linux/linux-5.10/tools/testing/selftests/drivers/net/mlxsw/ |
| D | fib_offload.sh | 87 check_err $? "lowest metric not offloaded after append"
95 check_err $? "lowest metric not offloaded after prepend"
136 check_err $? "multipath route not offloaded after delete & add"
143 check_err $? "lowest metric not offloaded after append"
152 check_err $? "lowest metric not offloaded after prepend"
179 check_err $? "prefix route not offloaded after replace"
186 check_err $? "multipath route not offloaded after replace"
192 check_err $? "prefix route offloaded after 'replacing' multipath route"
194 check_err $? "multipath route not offloaded after being 'replaced' by prefix route"
201 check_err $? "multipath route not offloaded after replacing multipath route"
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/arm64/pauth/ |
| D | pac.c | 332 struct signatures after; in TEST() local
342 sign_specific(&after, ARBITRARY_VALUE); in TEST()
344 ASSERT_EQ(before.keyia, after.keyia) TH_LOG("keyia changed after context switching"); in TEST()
345 ASSERT_EQ(before.keyib, after.keyib) TH_LOG("keyib changed after context switching"); in TEST()
346 ASSERT_EQ(before.keyda, after.keyda) TH_LOG("keyda changed after context switching"); in TEST()
347 ASSERT_EQ(before.keydb, after.keydb) TH_LOG("keydb changed after context switching"); in TEST()
355 size_t after; in TEST() local
365 after = keyg_sign(ARBITRARY_VALUE); in TEST()
367 ASSERT_EQ(before, after) TH_LOG("keyg changed after context switching"); in TEST()
|
| /kernel/linux/linux-5.10/tools/testing/selftests/vm/ |
| D | thuge-gen.c | 145 unsigned long before, after; in test_mmap() local
154 after = read_free(size); in test_mmap()
155 Dprintf("before %lu after %lu diff %ld size %lu\n", in test_mmap()
156 before, after, before - after, size); in test_mmap()
157 assert(size == getpagesize() || (before - after) == NUM_PAGES); in test_mmap()
166 unsigned long before, after; in test_shmget() local
185 after = read_free(size); in test_shmget()
187 Dprintf("before %lu after %lu diff %ld size %lu\n", in test_shmget()
188 before, after, before - after, size); in test_shmget()
189 assert(size == getpagesize() || (before - after) == NUM_PAGES); in test_shmget()
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/reset/ |
| D | gpio-restart.txt | 14 reset. After a delay specified by active-delay, the GPIO is set to
16 triggered reset. After a delay specified by inactive-delay, the GPIO
17 is driven active again. After a delay specified by wait-delay, the
40 - active-delay: Delay (default 100) to wait after driving gpio active [ms]
41 - inactive-delay: Delay (default 100) to wait after driving gpio inactive [ms]
42 - wait-delay: Delay (default 3000) to wait after completing restart
|
| D | gpio-poweroff.txt | 12 triggering positive edge triggered power off. After a delay of 100ms,
14 triggering negative edge triggered power off. After another 100ms
16 the CPU still running after a 3000ms delay, a WARN_ON(1) is emitted.
30 - active-delay-ms: Delay (default 100) to wait after driving gpio active
31 - inactive-delay-ms: Delay (default 100) to wait after driving gpio inactive
|
| /kernel/linux/linux-5.10/Documentation/driver-api/md/ |
| D | raid5-cache.rst | 34 The write-through cache will cache all data on cache disk first. After the data
36 two-step write will guarantee MD can recover correct data after unclean
40 filesystems) after the data is safe on RAID disks, so cache disk failure
57 RAID disks only after the data becomes a full stripe write. This will
62 filesystems) right after the data hits cache disk. The data is flushed to raid
63 disks later after specific conditions met. So cache disk failure will cause
92 parity to the log, writes the data and parity to RAID disks after the data and
99 MD will calculate parity for the data and write parity into the log. After this
105 After an unclean shutdown, MD does recovery. MD reads all meta data and data
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | suspend.h | 121 * @prepare() is called right after devices have been suspended (ie. the
130 * @prepare_late is called before disabling nonboot CPUs and after
142 * @wake: Called when the system has just left a sleep state, right after
147 * after @prepare_late and @enter(), even if one of them fails.
153 * that implement @prepare(). If implemented, it is always called after
154 * @enter() and @wake(), even if any of them fails. It is executed after
164 * @end: Called by the PM core right after resuming devices, to indicate to
323 * arch_suspend_enable_irqs - enable IRQs after suspend
375 * Called right after shrinking memory and before freezing devices.
377 * @end: Called by the PM core right after resuming devices, to indicate to
[all …]
|
| /kernel/linux/linux-5.10/drivers/scsi/mvsas/ |
| D | mv_64xx.h | 53 /* ports 1-3 follow after this */
56 /* ports 5-7 follow after this */
60 /* ports 1-3 follow after this */
62 /* ports 5-7 follow after this */
68 /* ports 1-3 follow after this */
71 /* ports 5-7 follow after this */
75 /* ports 1-3 follow after this */
78 /* ports 5-7 follow after this */
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/icelake/ |
| D | frontend.json | 277 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro…
286 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d…
292 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro…
301 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d…
307 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front…
316 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d…
322 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front…
331 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d…
337 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front…
346 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d…
[all …]
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | suspend-and-interrupts.rst | 13 suspend after the "late" phase of suspending devices (that is, after all of the
17 The rationale for doing so is that after the "late" phase of device suspend
22 not prepared for interrupts triggering after their devices had been suspended.
52 for it will be executed as usual after suspend_device_irqs(), even if the
72 After wakeup, it generally is better to disable that input to prevent the
90 already suspended. However, after suspend_device_irqs() interrupt handlers are
101 interrupts right after the "noirq" phase of suspending devices.
122 interrupts (interrupt handlers are invoked after suspend_device_irqs()) are
124 handlers are not invoked after suspend_device_irqs()).
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | cachetlb.rst | 10 after the interface is invoked.
34 The most severe flush of all. After this interface runs,
44 the TLB. After running, this interface must make sure that
46 'mm' will be visible to the cpu. That is, after running,
57 address translations from the TLB. After running, this
60 'start' to 'end-1' will be visible to the cpu. That is, after
83 After running, this interface must make sure that any previous
86 is, after running, there will be no entries in the TLB for
140 the caches. That is, after running, there will be no cache
149 the caches. That is, after running, there will be no cache
[all …]
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/ |
| D | ia_css_timer.h | 36 /** Timer Event after Initialization */
38 /** Timer Event after end of Main */
40 /** Timer Event after thread start */
42 /** Timer Event after Frame Process Start */
44 /** Timer Event after Frame Process End */
|
| /kernel/linux/linux-5.10/kernel/rcu/ |
| D | sync.c | 31 * Must be called after rcu_sync_init() and before first use.
55 * rcu_sync_exit(), so that it is invoked after a grace period following the
67 * readers back onto their fastpaths (after a grace period). If both
84 * We're at least a GP after the GP_IDLE->GP_ENTER transition. in rcu_sync_func()
97 * We're at least a GP after the last rcu_sync_exit(); eveybody in rcu_sync_func()
111 * a slowpath during the update. After this function returns, all
159 * rcu_sync_exit() - Allow readers back onto fast path after grace period
163 * now allow readers to make use of their fastpaths after a grace period
164 * has elapsed. After this grace period has completed, all subsequent
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/skylakex/ |
| D | uncore-memory.json | 92 …nt counts whether AutoPrecharge (which closes the DRAM Page automatically after a read/write) is e…
102 …nt counts whether AutoPrecharge (which closes the DRAM Page automatically after a read/write) is …
132 …after they enter the memory controller, and need credits for an entry in this buffer before being …
141 …after they enter the memory controller, and need credits for an entry in this buffer before being …
150 …after they enter the memory controller, and need credits for an entry in this buffer before being …
159 …after they enter the memory controller, and need credits for an entry in this buffer before being …
|
| /kernel/linux/linux-5.10/Documentation/m68k/ |
| D | buddha-driver.rst | 33 as long as $48 is not touched. After $48 has been written,
146 value 0 (Default after reset)
147 497ns Select (7 clock cycles) , IOR/IOW after 172ns (2 clock cycles)
152 639ns Select (9 clock cycles), IOR/IOW after 243ns (3 clock cycles)
155 781ns Select (11 clock cycles), IOR/IOW after 314ns (4 clock cycles)
158 355ns Select (5 clock cycles), IOR/IOW after 101ns (1 clock cycle)
161 355ns Select (5 clock cycles), IOR/IOW after 172ns (2 clock cycles)
164 355ns Select (5 clock cycles), IOR/IOW after 243ns (3 clock cycles)
167 1065ns Select (15 clock cycles), IOR/IOW after 314ns (4 clock cycles)
170 355ns Select, (5 clock cycles), IOR/IOW after 101ns (1 clock cycle)
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/media/ |
| D | dtv-frontend.rst | 107 in order to remove the tuner from the I2C bus after a channel is
115 removed in the future, after we have all existing drivers supporting
237 measurement usually comes from the tuner (e. g. after ``FE_HAS_CARRIER``,
241 as the frontend measures it indirectly from other parameters (e. g. after
244 Having it available after inner FEC is more common.
247 - Those counters measure the number of bits and bit errors errors after
249 (after Viterbi, LDPC or other inner code).
252 (e. g. after ``FE_HAS_SYNC`` or after ``FE_HAS_LOCK``,
263 after ``FE_HAS_VITERBI``, see :c:type:`fe_status`).
266 - Those counters measure the number of blocks and block errors errors after
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/regulator/ |
| D | richtek,rtmv20-regulator.yaml | 38 load current pulse delay in microsecond after strobe pin pulse high.
45 Load current pulse width in microsecond after strobe pin pulse high.
52 Fsin1 pulse high delay in microsecond after vsync signal pulse high.
59 Fsin1 pulse high width in microsecond after vsync signal pulse high.
66 Fsin2 pulse high delay in microsecond after vsync signal pulse high.
73 Fsin2 pulse high width in microsecond after vsync signal pulse high.
|
| /kernel/linux/linux-5.10/tools/testing/selftests/powerpc/pmu/ebb/ |
| D | pmae_handling_test.c | 29 static uint64_t before, after; variable
49 after = mfspr(SPRN_MMCR0); in syscall_ebb_callee()
50 if (before != after) in syscall_ebb_callee()
88 printf("Saw MMCR0 before 0x%lx after 0x%lx\n", before, after); in test_body()
|