Home
last modified time | relevance | path

Searched full:accurate (Results 1 – 25 of 434) sorted by relevance

12345678910>>...18

/Linux-v5.15/arch/x86/math-emu/
DREADME74 a value of pi which is accurate to more than 128 bits. As a consequence,
75 the reduced argument is accurate to more than 64 bits for arguments up
76 to a few pi, and accurate to more than 64 bits for most arguments,
78 80486, which uses a value of pi which is accurate to 66 bits.
243 accurate to 64 bits can result in a relative accuracy in cos() of
273 for pi which is accurate to more than 128 bits precision. As a
299 pi/2) the emulator is more accurate than an 80486 FPU. For very large
300 arguments, the emulator is far more accurate.
317 results which are in error (i.e. less accurate than the best possible
/Linux-v5.15/include/linux/platform_data/
Ddavinci_asp.h48 * and makes clock more accurate (FS is not symmetrical and the
67 * ACCURATE CLOCK APPROACH:
/Linux-v5.15/arch/sh/kernel/
Dunwinder.c10 * the most accurate unwinder being the currently active one.
26 * construct more accurate stack traces.
/Linux-v5.15/scripts/ksymoops/
DREADME5 other utilities in order to give more accurate Oops debugging.
/Linux-v5.15/include/linux/
Dgetcpu.h14 If you want 100% accurate information pass NULL instead. */
Ddevfreq_cooling.h24 * This function provides more accurate data to the
/Linux-v5.15/arch/powerpc/include/asm/
Daccounting.h9 /* Stuff for accurate time accounting */
/Linux-v5.15/Documentation/networking/
Dxfrm_sync.rst15 the processing of the SA as accurate as possible if it has access to it.
18 These patches add ability to sync and have accurate lifetime byte (to
/Linux-v5.15/Documentation/hwmon/
Dtmp102.rst23 sensor is accurate to 0.5 degree over the range of -25 to +85 C, and to 1.0
Dtmp108.rst26 The sensor is accurate to 0.75C over the range of -25 to +85 C, and to 1.0
Dpc87360.rst82 measurable around 3000 accurate
95 * highest accurate speed: sqrt(clock*100)
/Linux-v5.15/arch/arm64/include/asm/
Dasm-prototypes.h28 * this prototype is not entirely accurate.
/Linux-v5.15/Documentation/vm/damon/
Dindex.rst10 - *accurate* (the monitoring output is useful enough for DRAM level memory
/Linux-v5.15/arch/sh/include/uapi/asm/
Dcpu-features.h11 * reasonably accurate.
/Linux-v5.15/arch/arm64/lib/
Dstrlen.S116 loop with the accurate NUL check. */
137 /* The fast check failed, so do the slower, accurate NUL check. */
/Linux-v5.15/Documentation/accounting/
Dpsi.rst13 Without an accurate measure of such contention, users are forced to
22 Having an accurate measure of productivity losses caused by resource
/Linux-v5.15/drivers/thermal/ti-soc-thermal/
DKconfig32 this generation are not accurate, nor they are very close to
/Linux-v5.15/kernel/bpf/
Dbpf_lru_list.h67 * have to be very accurate. Hence, no protection is used. in bpf_lru_node_set_ref()
/Linux-v5.15/Documentation/sound/soc/
Dclocking.rst43 audio clocks as it usually gives more accurate sample rates than the CPU.
/Linux-v5.15/include/uapi/linux/
Dprctl.h47 /* Get/set whether we use statistical process timing or accurate timestamp
53 # define PR_TIMING_TIMESTAMP 1 /* Accurate timestamp based
/Linux-v5.15/tools/include/uapi/linux/
Dprctl.h47 /* Get/set whether we use statistical process timing or accurate timestamp
53 # define PR_TIMING_TIMESTAMP 1 /* Accurate timestamp based
/Linux-v5.15/drivers/gpu/drm/omapdrm/
Domap_irq.c107 * interrupts will have to stay on to keep the count accurate.
137 * interrupts will have to stay on to keep the count accurate.
/Linux-v5.15/Documentation/translations/
Dindex.rst49 Translations try to be as accurate as possible but it is not possible to map
/Linux-v5.15/Documentation/devicetree/bindings/serial/
Dbrcm,bcm7271-uart.yaml17 enhancements for more accurate high speed baud rates and support
/Linux-v5.15/drivers/iio/accel/
Dbmc150-accel.h18 * but unfortunately this information is not always accurate. There are some

12345678910>>...18