Home
last modified time | relevance | path

Searched refs:accuracy (Results 1 – 71 of 71) sorted by relevance

/linux-4.4.14/Documentation/devicetree/bindings/clock/
Dfixed-clock.txt13 - clock-accuracy : accuracy of clock in ppb (parts per billion).
22 clock-accuracy = <100>;
Dat91-clock.txt105 - clock-accuracy : define the internal RC oscillator accuracy.
111 clock-accuracy = <50000000>;
177 - clock-accuracy : define the internal RC oscillator accuracy.
185 clock-accuracy = <50000000>;
/linux-4.4.14/drivers/clk/at91/
Dclk-slow.c54 unsigned long accuracy; member
197 return osc->accuracy; in clk_slow_rc_osc_recalc_accuracy()
239 unsigned long accuracy, in at91_clk_register_slow_rc_osc() argument
262 osc->accuracy = accuracy; in at91_clk_register_slow_rc_osc()
277 u32 accuracy = 0; in of_at91sam9x5_clk_slow_rc_osc_setup() local
283 of_property_read_u32(np, "clock-accuracy", &accuracy); in of_at91sam9x5_clk_slow_rc_osc_setup()
286 clk = at91_clk_register_slow_rc_osc(sckcr, name, frequency, accuracy, in of_at91sam9x5_clk_slow_rc_osc_setup()
Dclk-main.c50 unsigned long accuracy; member
285 return osc->accuracy; in clk_main_rc_osc_recalc_accuracy()
300 u32 frequency, u32 accuracy) in at91_clk_register_main_rc_osc() argument
324 osc->accuracy = accuracy; in at91_clk_register_main_rc_osc()
348 u32 accuracy = 0; in of_at91sam9x5_clk_main_rc_osc_setup() local
353 of_property_read_u32(np, "clock-accuracy", &accuracy); in of_at91sam9x5_clk_main_rc_osc_setup()
360 accuracy); in of_at91sam9x5_clk_main_rc_osc_setup()
/linux-4.4.14/drivers/clk/
Dclk-fixed-rate.c118 u32 accuracy = 0; in of_fixed_clk_setup() local
123 of_property_read_u32(node, "clock-accuracy", &accuracy); in of_fixed_clk_setup()
129 accuracy); in of_fixed_clk_setup()
Dclk-asm9260.c274 u32 accuracy = 0; in asm9260_acc_init() local
284 accuracy = clk_get_accuracy(__clk_lookup(ref_clk)); in asm9260_acc_init()
286 ref_clk, 0, rate, accuracy); in asm9260_acc_init()
Dclk.c65 unsigned long accuracy; member
410 return core->accuracy; in __clk_get_accuracy()
943 parent_accuracy = core->parent->accuracy; in __clk_recalc_accuracies()
946 core->accuracy = core->ops->recalc_accuracy(core->hw, in __clk_recalc_accuracies()
949 core->accuracy = parent_accuracy; in __clk_recalc_accuracies()
957 unsigned long accuracy; in clk_core_get_accuracy() local
963 accuracy = __clk_get_accuracy(core); in clk_core_get_accuracy()
966 return accuracy; in clk_core_get_accuracy()
2127 (u32 *)&core->accuracy); in clk_debug_create_one()
2406 core->accuracy = core->ops->recalc_accuracy(core->hw, in __clk_init()
[all …]
/linux-4.4.14/arch/x86/math-emu/
DREADME72 based upon getting good accuracy with reasonable speed.
228 The accuracy of the emulator is in almost all cases equal to or better
237 The following table compares the emulator accuracy for the sqrt(),
240 would be 64 bits. The reduced Turbo C accuracy of cos() and tan() for
243 accurate to 64 bits can result in a relative accuracy in cos() of
260 ** The accuracy for exp() and log() is low because the FPU (emulator)
274 consequence, the accuracy of these functions for large arguments has
276 FPU). There is also now no degradation of accuracy for fcos and fptan
278 definition of accuracy has changed slightly from that used for the
303 Prior to version 1.20 of the emulator, the accuracy of the results for
[all …]
/linux-4.4.14/Documentation/hwmon/
Dshtc136 2. high or low accuracy. High accuracy is used by default and using it is
Dtc7415 and +- 2 degrees centigrade accuracy.
Dpc8736065 readings more range or accuracy. Usually, users have to learn how it works,
71 slowest accuracy highest
81 * accuracy around 3000 RPM: 3000^2/clock
84 RPM as the lowest acceptable accuracy.
Dadt741032 -55°C to +150°C. It has a high accuracy of +/-0.5°C and can be operated at a
46 a better accuracy (0.25°C instead of 0.50°C.)
Dgl518sm40 degrees, with a accuracy of +/-3 degrees.
47 give the readings more range or accuracy. Not all RPM values can
Dds62021 to +125. Between 0 and 70 degree Celsius, accuracy is 0.5 Kelvin. The value
Demc210322 the readings more range or accuracy. Not all RPM values can accurately be
Dw83l786ng35 or 128 for fan 1/2) to give the readings more range or accuracy.
Dsmsc47m147 the readings more range or accuracy. Not all RPM values can accurately be
Dthmc5038 accuracy. An alarm is issued (usually to a connected LM78) when the
Dlm8044 the readings more range or accuracy. Not all RPM values can accurately be
Dlm8741 the readings more range or accuracy. Not all RPM values can accurately be
Dlm7844 the readings more range or accuracy. Not all RPM values can accurately be
Dlm6375 The LM96163 is an enhanced version of LM63 with improved temperature accuracy
Dlm7570 set and read to half-degree accuracy.
Dlm8376 accuracy is guaranteed to 3.0 degrees (see the datasheet for more
Dvia686a49 the readings more range or accuracy. Not all RPM values can accurately be
Dsis559576 the readings more range or accuracy. Not all RPM values can accurately be
Dds1621111 Please refer to the device datasheets for accuracy at other temperatures.
Dw83791d76 32, 64 or 128 for all fans) to give the readings more range or accuracy.
Dw83792d61 128) to give the readings more range or accuracy.
Dnct677570 16, 32, 64 or 128) to give the readings more range or accuracy; the other chips
Dw83627ehf74 128) to give the readings more range or accuracy. The driver sets the most
Dlm90163 * Better external channel accuracy
Dit87176 accuracy. With a divider of 2, the lowest representable value is around
Dw83781d96 the readings more range or accuracy. Not all RPM values can accurately
/linux-4.4.14/drivers/staging/clocking-wizard/
DTODO8 - maximize accuracy before divisions
/linux-4.4.14/drivers/staging/iio/Documentation/
Dsysfs-bus-iio-light-tsl258320 It is used in the process of calibrating the device accuracy.
/linux-4.4.14/arch/arm/boot/dts/
Dalphascale-asm9260.dtsi33 clock-accuracy = <30000>;
Dat91sam9n12.dtsi113 clock-accuracy = <50000000>;
409 clock-accuracy = <50000000>;
Dsama5d2.dtsi321 clock-accuracy = <100000000>;
940 clock-accuracy = <250000000>;
Dat91sam9x5.dtsi121 clock-accuracy = <50000000>;
409 clock-accuracy = <50000000>;
Dsama5d3.dtsi924 clock-accuracy = <50000000>;
1300 clock-accuracy = <50000000>;
Dat91sam9rl.dtsi1061 clock-accuracy = <50000000>;
Dsama5d4.dtsi403 clock-accuracy = <100000000>;
1317 clock-accuracy = <250000000>;
Dat91sam9260.dtsi128 clock-accuracy = <50000000>;
Dat91sam9g45.dtsi1241 clock-accuracy = <50000000>;
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Dlpc32xx-mlc.txt12 accuracy:)
/linux-4.4.14/Documentation/devicetree/bindings/power/
Dltc2941.txt16 This determines the range and accuracy of the gauge. The value is programmed
/linux-4.4.14/Documentation/timers/
Dtimekeeping.txt45 When the wall-clock accuracy of the clock source isn't satisfactory, there
124 between accuracy compared to the clock source, you may sacrifice accuracy
134 jiffy frequency for the architecture. This will affect scheduling accuracy
/linux-4.4.14/Documentation/sound/alsa/
Dtimestamping.txt71 accuracy. It can also request the delay-to-analog be included in the
87 The audio timestamp accuracy can be returned to user-space, so that
110 The accuracy is reported in nanosecond units (using an unsigned 32-bit
180 shows how compensating for the delay exposes a 1ms accuracy (due to
/linux-4.4.14/drivers/xen/
Defi.c55 tc->accuracy = efi_data(op).u.get_time.accuracy; in xen_efi_get_time()
/linux-4.4.14/include/sound/
Dpcm.h320 u32 accuracy; /* up to 4.29s, will be packed in separate field */ member
323 static inline void snd_pcm_pack_audio_tstamp_report(__u32 *data, __u32 *accuracy, in snd_pcm_pack_audio_tstamp_report() argument
336 *accuracy = report->accuracy; in snd_pcm_pack_audio_tstamp_report()
/linux-4.4.14/drivers/char/
Defirtc.c357 cap.resolution, cap.accuracy, cap.sets_to_zero); in efi_rtc_proc_show()
/linux-4.4.14/Documentation/thermal/
Dcpu-cooling-api.txt140 platform specifics, and this can then impact the accuracy of a model
194 potential complexity in implementation, the importance and accuracy of
/linux-4.4.14/include/xen/interface/
Dplatform.h148 uint32_t accuracy; member
/linux-4.4.14/Documentation/arm/nwfpe/
DTODO26 seem to promise extreme accuracy (in the order of 99.8%) and reasonable speed.
/linux-4.4.14/drivers/hwmon/
Dacpi_power_meter.c78 u64 accuracy; member
454 unsigned int acc = resource->caps.accuracy; in show_accuracy()
/linux-4.4.14/include/net/bluetooth/
Dmgmt.h439 __le16 accuracy; member
Dhci.h1216 __le16 accuracy; member
/linux-4.4.14/Documentation/scsi/
DFlashPoint.txt98 for the FlashPoint. Rumors of varying accuracy had been circulating
/linux-4.4.14/kernel/trace/
DKconfig178 sections, with microsecond accuracy.
202 sections, with microsecond accuracy.
/linux-4.4.14/sound/soc/intel/skylake/
Dskl-pcm.c863 audio_tstamp_report->accuracy = 42; /* 24MHzWallClk == 42ns resolution */ in skl_get_time_info()
/linux-4.4.14/include/linux/
Defi.h158 u32 accuracy; member
/linux-4.4.14/sound/pci/hda/
Dhda_controller.c362 audio_tstamp_report->accuracy = 42; /* 24 MHz WallClock == 42ns resolution */ in azx_get_time_info()
/linux-4.4.14/arch/m68k/fpsp040/
Dsetox.S107 | the value -log2/64 to 88 bits of accuracy.
/linux-4.4.14/Documentation/DocBook/
Dkernel-api.xml.db742 API-clk-get-accuracy
/linux-4.4.14/Documentation/mtd/
Dnand_ecc.txt563 million iterations in order not to lose too much accuracy. This one
/linux-4.4.14/Documentation/
DSubmittingPatches93 generating it with diff(1), to ensure accuracy.
/linux-4.4.14/net/bluetooth/
Dhci_event.c816 conn->clock_accuracy = le16_to_cpu(rp->accuracy); in hci_cc_read_clock()
Dmgmt.c5938 rp.accuracy = cpu_to_le16(conn->clock_accuracy); in clock_info_cmd_complete()
/linux-4.4.14/arch/m68k/ifpsp060/src/
Dfpsp.S7086 # c) To fully preserve accuracy, the polynomial is #
8120 # Note 2. In Step 2 of lognp1, in order to preserved accuracy, #
Dfplsp.S6763 # approximate the value -log2/64 to 88 bits of accuracy. #