| /kernel/linux/linux-5.10/crypto/ |
| D | jitterentropy.c | 191 static void jent_rct_insert(struct rand_data *ec, int stuck) in jent_rct_insert() argument
200 if (stuck) { in jent_rct_insert()
381 int stuck) in jent_lfsr_time() argument
433 if (!stuck) in jent_lfsr_time()
519 int stuck; in jent_measure_jitter() local
533 stuck = jent_stuck(ec, current_delta); in jent_measure_jitter()
536 jent_lfsr_time(ec, current_delta, 0, stuck); in jent_measure_jitter()
538 return stuck; in jent_measure_jitter()
742 int stuck; in jent_entropy_init() local
762 stuck = jent_stuck(&ec, delta); in jent_entropy_init()
[all …]
|
| /kernel/linux/linux-5.10/fs/xfs/ |
| D | xfs_trans_ail.c | 426 int stuck = 0; in xfsaild_push() local
499 stuck++; in xfsaild_push()
506 stuck++; in xfsaild_push()
528 if (stuck > 100) in xfsaild_push()
552 } else if (((stuck + flushing) * 100) / count > 90) { in xfsaild_push()
|
| /kernel/linux/linux-5.10/arch/sparc/kernel/ |
| D | smp_64.c | 399 int stuck, tmp; in spitfire_xcall_helper() local
437 stuck = 100000; in spitfire_xcall_helper()
447 stuck -= 1; in spitfire_xcall_helper()
448 if (stuck == 0) in spitfire_xcall_helper()
453 if (stuck == 0) { in spitfire_xcall_helper()
553 long stuck; in cheetah_xcall_deliver() local
555 stuck = 100000 * nack_busy_id; in cheetah_xcall_deliver()
578 if (!--stuck) in cheetah_xcall_deliver()
|
| /kernel/linux/linux-5.10/drivers/infiniband/hw/qib/ |
| D | qib_qsfp.c | 52 int stuck = 0; in qsfp_read() local
92 stuck = 1; in qsfp_read()
135 if (stuck) in qsfp_read()
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | ipddp.rst | 69 Encapsulation has been used to allow a Linux box stuck on a LocalTalk
70 network to use IP. It should work equally well if you are stuck on an
|
| D | net_dim.rst | 69 done in order to avoid getting stuck in a "deep sleep" scenario. Once a
|
| /kernel/linux/linux-5.10/drivers/md/bcache/ |
| D | Kconfig | 28 operations that get stuck.
|
| /kernel/linux/linux-5.10/Documentation/networking/devlink/ |
| D | mlx4.rst | 51 In case a firmware command times out, firmware getting stuck, or a non zero
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-class-bdi | 48 mount that is prone to get stuck, or a FUSE mount which cannot
|
| /kernel/linux/linux-5.10/drivers/net/appletalk/ |
| D | Kconfig | 87 box is stuck on an AppleTalk only network) or decapsulate (e.g. if
109 is stuck on an AppleTalk network (which hopefully contains a
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/ |
| D | qcom,pm8xxx-keypad.txt | 21 and the second interrupt specifies the key stuck interrupt.
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | asb100.rst | 67 be read-only or otherwise stuck at 0x00.
|
| D | w83781d.rst | 332 and 4 is ignored/stuck, on AMD boards sensor 4 is the CPU and sensor 2 is
|
| /kernel/linux/linux-5.10/arch/powerpc/platforms/powermac/ |
| D | smp.c | 375 goto stuck; in smp_psurge_kick_cpu()
389 stuck: in smp_psurge_kick_cpu()
|
| /kernel/linux/linux-5.10/Documentation/i2c/ |
| D | gpio-fault-injection.rst | 48 there are I2C client devices which detect a stuck SDA on their side and release
50 device deglitching and monitoring the I2C bus. It could also detect a stuck SDA
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | botching-up-ioctls.rst | 113 now we're stuck forever with some arcane semantics in both the kernel and
116 * If you can't make a given codepath restartable make a stuck task at least
222 be stuck with a given ioctl essentially forever. You can try to deprecate
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | imx6qdl-sr-som.dtsi | 60 * some rare issues where the PHY gets stuck in an inconsistent and
|
| /kernel/linux/linux-5.10/tools/virtio/virtio-trace/ |
| D | README | 108 If a host does not open these, trace data get stuck in buffers of virtio. Then,
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/3com/ |
| D | vortex.rst | 233 decides that the transmitter has become stuck and needs to be reset.
259 get stuck on the 10base2 port and a driver reload was necessary to
|
| /kernel/linux/linux-5.10/Documentation/input/devices/ |
| D | atarikbd.rst | 194 major controller faults (ROM checksum and RAM test) and such things as stuck
195 keys. Any keys down at power-up are presumed to be stuck, and their BREAK
236 ikbd will then scan the key matrix for any stuck (closed) keys. Any keys found
|
| /kernel/linux/linux-5.10/drivers/usb/gadget/udc/ |
| D | net2280.c | 2600 int stuck = 0; in handle_ep_small() local
2640 req->td_dma && stuck++ > 5) { in handle_ep_small()
2646 ep->ep.name, stuck, in handle_ep_small()
2651 stuck = 0; in handle_ep_small()
2655 stuck = 0; in handle_ep_small()
|
| /kernel/linux/linux-5.10/Documentation/livepatch/ |
| D | livepatch.rst | 148 are stuck in the initial patch state.
171 transition gets stuck for a long time because of a blocking task. Administrator
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/nfs/ |
| D | nfs-rdma.rst | 28 If you get stuck, you can ask questions on the
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/myricom/myri10ge/ |
| D | myri10ge.c | 187 int stuck; member
3357 ss->stuck = 1; in myri10ge_check_slice()
3431 if (ss->stuck) { in myri10ge_watchdog()
3435 ss->stuck = 0; in myri10ge_watchdog()
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | sysrq.rst | 205 Sometimes SysRq seems to get 'stuck' after using it, what can I do?
|