/linux-4.1.27/tools/perf/util/ |
D | stat.c | 10 delta = val - stats->mean; in update_stats() 11 stats->mean += delta / stats->n; in update_stats() 12 stats->M2 += delta*(val - stats->mean); in update_stats() 23 return stats->mean; in avg_stats()
|
D | stat.h | 8 double n, mean, M2; member 20 stats->mean = 0.0; in init_stats()
|
/linux-4.1.27/drivers/rtc/ |
D | rtc-88pm860x.c | 246 unsigned int sum, data, mean, vrtc_set; in calibrate_vrtc_work() local 256 mean = sum >> 4; in calibrate_vrtc_work() 258 dev_dbg(info->dev, "mean:%d, vrtc_set:%d\n", mean, vrtc_set); in calibrate_vrtc_work() 262 if ((mean + 200) < vrtc_set) { in calibrate_vrtc_work() 268 } else if ((mean - 200) > vrtc_set) { in calibrate_vrtc_work()
|
/linux-4.1.27/Documentation/filesystems/ |
D | gfs2-glocks.txt | 137 The statistics are divided into three pairs of mean and 138 variance, plus two counters. The mean/variance pairs are 144 Unlike the TCP/IP Illustrated case, the mean and variance are 147 The three pairs of mean/variance measure the following 164 has gone into the mean/variance calculations. The other counter 220 using the format mean/variance for each of the timing stats.
|
D | sysv-fs.txt | 196 Notation: We often speak of a "block" but mean a zone (the allocation unit)
|
D | hpfs.txt | 173 anybody know what does it mean? 176 What does "unbalanced tree" message mean?
|
D | xfs-self-describing-metadata.txt | 106 filesystem to find the owner of the block. Worse, the corruption could mean that
|
D | path-lookup.txt | 360 Dropping from rcu-walk to ref-walk mean that we have encountered a dentry where
|
D | ext2.txt | 81 which is decided when the filesystem is created. Smaller blocks mean
|
D | sharedsubtree.txt | 233 to mean the same thing, throughout this document.
|
D | xfs-delayed-logging-design.txt | 131 will result in a consistent filesystem. What it does mean is that as far as the
|
D | proc.txt | 1860 users. It doesn't mean that it hides a fact whether a process with a specific
|
/linux-4.1.27/fs/hfsplus/ |
D | Kconfig | 27 Linux. POSIX ACLs doesn't mean something under Mac OS X.
|
/linux-4.1.27/Documentation/cpu-freq/ |
D | boost.txt | 10 Reading or writing 1 does not mean that the system is boosting at this 67 not necessarily mean that it will occur every time even using the exact
|
D | cpufreq-stats.txt | 55 will mean this CPU spent <time> usertime units of time at <frequency>. Output
|
/linux-4.1.27/Documentation/arm/pxa/ |
D | mfp.txt | 42 mean it's dedicated for GPIO19, only as a hint that internally this pin 69 mean it is a GPIO signal, and by MFP<xxx> or pin xxx, we mean a physical 138 and on which edge(s). This, however, doesn't necessarily mean the
|
/linux-4.1.27/Documentation/parisc/ |
D | debugging | 24 than __PAGE_OFFSET (0x10000000) which mean a virtual address didn't
|
/linux-4.1.27/Documentation/ |
D | basic_profiling.txt | 41 a 0Hz CPU, APIC was not on. Be aware that idle=poll may mean a performance
|
D | volatile-considered-harmful.txt | 4 C programmers have often taken volatile to mean that the variable could be
|
D | binfmt_misc.txt | 21 Here is what the fields mean:
|
D | rtc.txt | 5 When Linux developers talk about a "Real Time Clock", they usually mean
|
D | Changes | 67 your kernel. This change does, however, mean that you need a recent
|
D | pinctrl.txt | 400 we usually mean a way of soldering or wiring the package into an electronic 792 is taken to mean different things than what the kernel does, the developer 794 into "GPIO mode". It appears that what hardware engineers mean with 879 of the GPIO register in case (B) especially. This doesn't mean that such
|
D | nommu-mmap.txt | 230 return -ENOSYS. This will be taken to mean that this operation just doesn't
|
D | ManagementStyle | 11 to do with reality. It started as a lark, but that doesn't mean that it
|
D | bcache.txt | 332 potentially be used for writeback. This doesn't mean this space isn't used
|
D | parport-lowlevel.txt | 177 doesn't necessarily mean that DMA will always be used when possible.
|
D | CodingStyle | 280 in the source, what does it mean?
|
D | kernel-parameters.txt | 2170 Note that mem_start is often overloaded to mean
|
/linux-4.1.27/Documentation/devicetree/bindings/ |
D | ABI.txt | 9 break on an older device tree, but that doesn't mean the binding is
|
/linux-4.1.27/Documentation/devicetree/bindings/watchdog/ |
D | atmel-wdt.txt | 31 watchdog reset time depends on mean CPU usage and will not reset at all
|
/linux-4.1.27/fs/jffs2/ |
D | Kconfig | 110 compressors can mean you cannot read existing file systems, 111 and enabling experimental compressors can mean that you
|
/linux-4.1.27/Documentation/sound/alsa/soc/ |
D | pops_clicks.txt | 49 is heard when the gain increase or decrease changes the mean audio signal
|
/linux-4.1.27/Documentation/input/ |
D | cs461x.txt | 14 4-button joystick; I mean the jstest utility. Also I've tried to
|
D | event-codes.txt | 117 to 1. Meaningful physical contact may mean any contact, or it may mean
|
D | iforce-protocol.txt | 162 ff 03 42 03 e8 CS would mean that the device has 1000 bytes of ram available.
|
D | joystick-api.txt | 140 necessarily a "real" error (check errno(3)); it can just mean there
|
D | input-programming.txt | 217 If you don't need absfuzz and absflat, you can set them to zero, which mean
|
/linux-4.1.27/arch/arm/include/debug/ |
D | tegra.S | 94 cmp \rv, #2 @ 2 and 3 mean DCC, UART
|
/linux-4.1.27/Documentation/video4linux/ |
D | cafe_ccic | 43 assumed to actually mean much of anything.
|
D | Zoran | 151 When you speak about NTSC, you usually mean the standard: CCIR - M using 155 When you talk about PAL, you usually mean: CCIR - B/G using the PAL 158 When you talk about SECAM, you mean: CCIR - L using the SECAM Colorsystem 402 1024 bits per block. 100% in the new driver mean 1:2 compression; the maximum
|
D | vivid.txt | 916 implement this, it would mean a lot of work to get this right. Since these
|
/linux-4.1.27/Documentation/sysctl/ |
D | README | 50 - knowledge of what all those values mean
|
D | vm.txt | 220 These are informational only. They do not mean that anything is wrong 670 Lower values mean lower latencies for initial faults, but at the same time
|
/linux-4.1.27/drivers/staging/iio/light/ |
D | tsl2x7x_core.c | 164 int mean; member 840 statP->mean = sample_sum / length; in tsl2x7x_prox_calculate() 843 tmp = data[i] - statP->mean; in tsl2x7x_prox_calculate() 896 chip->tsl2x7x_settings.prox_thres_high = (calP->max << 1) - calP->mean; in tsl2x7x_prox_cal() 899 calP->min, calP->mean, calP->max); in tsl2x7x_prox_cal()
|
/linux-4.1.27/fs/squashfs/ |
D | Kconfig | 204 the filesystem. Increasing this amount may mean SquashFS 206 of extra system memory. Decreasing this amount will mean
|
/linux-4.1.27/Documentation/video4linux/bttv/ |
D | README | 49 only bt878-based cards can have a subsystem ID (which does not mean
|
/linux-4.1.27/Documentation/vm/ |
D | page_owner.txt | 57 Although it doesn't mean that they have the right owner information,
|
D | transhuge.txt | 370 on any tail page, would mean having to split all hugepages upfront in
|
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/ |
D | Suspend.txt | 129 will mean that the CRC data block will take more memory, but will
|
D | Overview.txt | 64 This does mean that to find the status of any given SoC, a number
|
/linux-4.1.27/tools/perf/ |
D | builtin-kvm.c | 449 COMPARE_EVENT_KEY(mean, stats.mean); 458 DEF_SORT_NAME_KEY(time, mean),
|
/linux-4.1.27/drivers/media/usb/uvc/ |
D | uvc_video.c | 612 u32 mean; in uvc_video_clock_update() local 668 mean = (x1 + x2) / 2; in uvc_video_clock_update() 669 if (mean - (1024 << 16) > sof) in uvc_video_clock_update() 671 else if (sof > mean + (1024 << 16)) in uvc_video_clock_update()
|
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/ |
D | rockchip,pinctrl.txt | 61 The MUX 0 means gpio and MUX 1 to N mean the specific device function.
|
/linux-4.1.27/Documentation/networking/ |
D | tlan.txt | 48 debug messages, where x is a bit field where the bits mean
|
D | ipvs-sysctl.txt | 106 that this strategy is always disabled, 1 and 2 mean automatic
|
D | rds.txt | 34 The fact that IPv4 addresses are used does not mean the underlying
|
D | phy.txt | 161 phy_prepare_link(). This will mean that phydev->state is entirely yours to
|
D | filter.txt | 10 mean the very same mechanism of filtering in the Linux kernel. 919 BPF_MISC operations in eBPF, the class 7 is used as BPF_ALU64 to mean
|
D | arcnet-hardware.txt | 350 Vojtech Pavlik <vojtech@suse.cz> tells me this is what they mean:
|
/linux-4.1.27/Documentation/usb/ |
D | mass-storage.txt | 77 reader). It does *not* mean that the entire gadget can be 111 Note that this may mean that if the device is powered from USB and
|
D | usbmon.txt | 242 events contain no data, so if this call returns zero, it does not mean that
|
D | power-management.txt | 179 values mean never to autosuspend. You can write a 411 Autoresume attempts also can fail, although failure would mean that
|
/linux-4.1.27/Documentation/hwmon/ |
D | submitting-patches | 51 * Running your patch or driver file(s) through checkpatch does not mean its
|
D | lm90 | 269 two transactions will typically mean twice as much delay waiting for
|
D | w83781d | 267 AS99127F rev.2 direct from Winbond. The other codes mean ATT and DVC,
|
/linux-4.1.27/Documentation/x86/ |
D | pat.txt | 109 -- in the above table mean "Not suggested usage for the API". Some of the --'s
|
/linux-4.1.27/drivers/staging/i2o/ |
D | README.ioctl | 150 A return value of 0 does not mean that the value was actually 187 A return value of 0 does not mean that the value was actually
|
/linux-4.1.27/Documentation/i2c/ |
D | fault-codes | 86 of a transfer didn't get an ACK. While it might just mean
|
D | slave-interface | 96 'val'. Important: This does not mean that the previous byte has been acked, it
|
/linux-4.1.27/Documentation/locking/ |
D | mutex-design.txt | 149 for the largest lock in the kernel. Larger structure sizes mean more
|
/linux-4.1.27/Documentation/ABI/testing/ |
D | sysfs-devices-edac | 110 mean a Chipkill with x4 DRAM.
|
D | sysfs-class-mtd | 156 interpreted to mean simply "one or more bit errors were
|
D | sysfs-power | 33 "suspend-to-RAM", "power-on suspend" and "suspend-to-idle" mean.
|
/linux-4.1.27/arch/arm/plat-samsung/ |
D | Kconfig | 294 corruption over suspend and resume. A smaller value will mean that
|
/linux-4.1.27/drivers/iio/light/ |
D | Kconfig | 160 The driver provides raw and mean adc readings along with the current
|
/linux-4.1.27/Documentation/acpi/apei/ |
D | einj.txt | 18 It doesn't necessarily mean that EINJ is not supported if those above
|
/linux-4.1.27/drivers/block/paride/ |
D | Transition-notes | 64 mean that (2) was already not true.
|
/linux-4.1.27/Documentation/serial/ |
D | rocket.txt | 127 for 0x100, it will occupy 0x100 to 0x143. This would mean that you
|
/linux-4.1.27/arch/frv/kernel/ |
D | head.S | 332 # - for the FR451 this'll mean that the window through which the kernel is
|
/linux-4.1.27/fs/ |
D | Kconfig.binfmt | 11 because it is portable (this does *not* mean that you will be able
|
/linux-4.1.27/Documentation/scsi/ |
D | scsi_eh.txt | 150 Note that this does not mean lower layers are quiescent. If a LLDD 342 Note that both offline and ready status mean that the sdev is
|
D | ChangeLog.megaraid | 277 generic device model, neither of which is what you mean here.
|
D | tmscsim.txt | 289 0..7 mean 10, 8.0, 6.7, 5.7, 5.0, 4.0, 3.1 and 2 MHz resp. Default is
|
/linux-4.1.27/Documentation/arm/ |
D | cluster-pm-race-avoidance.txt | 172 from the basic model definition: CPU_UP does not mean that the 173 CPU is coherent yet, but it does mean that it is safe to resume
|
/linux-4.1.27/Documentation/sound/oss/ |
D | Opti | 136 The numeric parameters mean:
|
D | README.OSS | 265 Jazz16. Note that SB compatibility in DOS/Windows does _NOT_ mean anything
|
/linux-4.1.27/Documentation/power/ |
D | power_supply_class.txt | 114 of charge when battery became full/empty". It also could mean "value of
|
D | runtime_pm.txt | 89 core regards the device as suspended, which need not mean that it has been 90 put into a low power state. It is supposed to mean, however, that the 803 The term "autosuspend" is an historical remnant. It doesn't mean that the
|
D | devices.txt | 633 Some busses define rules about what different suspend states mean. PCI
|
/linux-4.1.27/arch/cris/arch-v10/ |
D | README.mm | 93 The MMU can map all 4 GB in user mode, but doing that would mean that a
|
/linux-4.1.27/fs/affs/ |
D | Changes | 4 then, 3.1 doesn't mean 'perfectly stable', too.)
|
/linux-4.1.27/arch/powerpc/platforms/ |
D | Kconfig | 222 mean that extra synchronization instructions are required near
|
/linux-4.1.27/drivers/media/usb/pwc/ |
D | philips.txt | 148 The square brackets mean that both the type and the serialnumber are
|
/linux-4.1.27/Documentation/timers/ |
D | timekeeping.txt | 129 i.e. after 64 bits. Since this is a nanosecond value this will mean it wraps
|
D | NO_HZ.txt | 180 However, the drawbacks listed above mean that adaptive ticks should not
|
/linux-4.1.27/Documentation/powerpc/ |
D | hvcs.txt | 202 NOTE: Just because there is a device node present doesn't mean that there 450 doesn't mean someone else didn't log into the console with the HMC console
|
D | pci_iov_resource_on_powernv.txt | 97 but that would mean using a completely different address allocation
|
/linux-4.1.27/Documentation/driver-model/ |
D | porting.txt | 442 though, that this will likely mean fixing up all the drivers that
|
/linux-4.1.27/arch/m68k/fpsp040/ |
D | round.S | 279 | bit of the mantissa (msb in d1) unless this would mean the exponent
|
/linux-4.1.27/drivers/mtd/nand/ |
D | Kconfig | 206 selected to save power. This will mean there is a small delay
|
/linux-4.1.27/Documentation/devicetree/bindings/thermal/ |
D | thermal.txt | 56 single unsigned integers, where larger numbers mean greater heat
|
/linux-4.1.27/Documentation/kdump/ |
D | kdump.txt | 276 This would mean:
|
/linux-4.1.27/lib/ |
D | Kconfig.debug | 1770 memtest=0, mean disabled; -- default 1771 memtest=1, mean do 1 test pattern; 1773 memtest=17, mean do 17 test patterns.
|
/linux-4.1.27/Documentation/cdrom/ |
D | ide-cd | 197 this does _not_ mean that the driver has successfully detected
|
/linux-4.1.27/drivers/net/usb/ |
D | Kconfig | 395 that may mean not being able to talk to Win32 systems or more
|
/linux-4.1.27/Documentation/filesystems/cifs/ |
D | README | 344 timeouts mean better the cache coherency, but increased number 345 of calls to the server. Longer timeouts mean reduced number
|
/linux-4.1.27/tools/perf/Documentation/ |
D | perf-script-python.txt | 181 mean either that the record step recorded event types that it wasn't
|
/linux-4.1.27/Documentation/sound/alsa/ |
D | HD-Audio.txt | 166 listed in the known preset model (white-)list. But, this doesn't mean
|
/linux-4.1.27/Documentation/gpio/ |
D | gpio-legacy.txt | 613 becomes available. That may mean the device should not be registered until
|
/linux-4.1.27/Documentation/m68k/ |
D | kernel-options.txt | 624 0 means turn off tagged queuing support, all other values > 0 mean
|
/linux-4.1.27/drivers/staging/speakup/ |
D | spkguide.txt | 102 administrator. This will mean that you will hear some, but not all, of 1079 screen. Speakup uses the term "Window", to mean a user defined area of
|
/linux-4.1.27/Documentation/trace/ |
D | ftrace.txt | 1105 interrupts were enabled in the mean time or shortly after this
|
/linux-4.1.27/Documentation/virtual/uml/ |
D | UserModeLinux-HOWTO.txt | 3077 arch/um/include/user_util.h). These mean that it went into a write,
|