Home
last modified time | relevance | path

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

12345678910>>...15

/linux/arch/x86/math-emu/
H A 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/arch/sh/kernel/
H A Dunwinder.c10 * the most accurate unwinder being the currently active one.
26 * construct more accurate stack traces.
/linux/scripts/ksymoops/
H A DREADME5 other utilities in order to give more accurate Oops debugging.
/linux/arch/powerpc/include/asm/
H A Daccounting.h9 /* Stuff for accurate time accounting */
/linux/arch/arm64/lib/
H A Dstrlen.S116 loop with the accurate NUL check. */
137 /* The fast check failed, so do the slower, accurate NUL check. */
/linux/Documentation/accounting/
H A 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/arch/arm64/include/asm/
H A Dasm-prototypes.h28 * this prototype is not entirely accurate.
/linux/arch/sh/include/uapi/asm/
H A Dcpu-features.h11 * reasonably accurate.
/linux/arch/arm64/boot/dts/freescale/
H A Dimx8mp-phyboard-pollux-etml1010g3dra.dtso31 * engine can reach accurate pixel clock of exactly 72.4 MHz.
H A Dimx8mp-phyboard-pollux-ph128800t006.dtso31 * engine can reach accurate pixel clock of exactly 66.5 MHz.
H A Dimx8mp-phyboard-pollux-peb-av-10-ph128800t006.dtso32 * engine can reach accurate pixel clock of exactly 66.5 MHz.
H A Dimx8mp-phyboard-pollux-peb-av-10-etml1010g3dra.dtso32 * engine can reach accurate pixel clock of exactly 72.4 MHz.
/linux/drivers/gpu/drm/omapdrm/
H A Domap_irq.c108 * interrupts will have to stay on to keep the count accurate.
138 * interrupts will have to stay on to keep the count accurate.
/linux/drivers/thermal/ti-soc-thermal/
H A DKconfig32 this generation are not accurate, nor they are very close to
/linux/Documentation/hwmon/
H A Dpc87360.rst82 measurable around 3000 accurate
95 * highest accurate speed: sqrt(clock*100)
H A Dlm70.rst60 The TMP125 is less accurate and provides 10-bit temperature data
/linux/Documentation/devicetree/bindings/serial/
H A Dbrcm,bcm7271-uart.yaml17 enhancements for more accurate high speed baud rates and support
/linux/drivers/clk/sunxi-ng/
H A Dccu-sun6i-rtc.c154 /* Assume the calibrated 32k clock is accurate. */ in ccu_iosc_32k_recalc_rate()
173 /* Assume the calibrated 32k clock is accurate. */ in ccu_iosc_32k_recalc_accuracy()
/linux/include/linux/
H A Ddevfreq_cooling.h24 * This function provides more accurate data to the
/linux/drivers/iio/accel/
H A Dbmc150-accel.h19 * but unfortunately this information is not always accurate. There are some
/linux/drivers/power/supply/
H A Drn5t618_power.c49 * Formula seems accurate for battery current, but for USB current around 70mA
74 /* input current limit is not very accurate */
83 /* input current limit is not very accurate */
/linux/Documentation/devicetree/bindings/iio/adc/
H A Dti,am3359-adc.yaml53 and averaged to get more accurate value. This increases the time taken by
/linux/arch/sh/
H A DKconfig.debug72 Enabling this option will make stacktraces more accurate, at
/linux/tools/power/cpupower/man/
H A Dcpupower-idle-info.127 a very busy system, these statistics may not be accurate. They still provide a
/linux/Documentation/driver-api/thermal/
H A Dnouveau_thermal.rst86 [PWM_min, PWM_max] range, the reported fan speed (RPM) may not be accurate

12345678910>>...15