/linux-4.1.27/drivers/usb/misc/ |
D | usbtest.c | 29 unsigned vary; member 414 int vary, in simple_io() argument 449 if (vary) { in simple_io() 452 len += vary; in simple_io() 455 len = (vary < max) ? vary : max; in simple_io() 492 alloc_sglist(int nents, int max, int vary, struct usbtest_dev *dev, int pipe) in alloc_sglist() argument 533 if (vary) { in alloc_sglist() 534 size += vary; in alloc_sglist() 537 size = (vary < max) ? vary : max; in alloc_sglist() 1711 unsigned count, unsigned length, unsigned vary, unsigned offset) in ctrl_out() argument [all …]
|
/linux-4.1.27/tools/usb/ |
D | testusb.c | 60 unsigned vary; member 398 param.vary = 512; in main() 440 if (parse_num(¶m.vary, optarg)) in main()
|
/linux-4.1.27/Documentation/devicetree/bindings/net/wireless/ |
D | qcom,ath10k.txt | 11 length can vary between hw versions
|
/linux-4.1.27/arch/m68k/hp300/ |
D | README.hp300 | 10 combination seems to work for me. Your mileage may vary.
|
/linux-4.1.27/Documentation/devicetree/bindings/input/ |
D | e3x0-button.txt | 17 Note: Interrupt numbers might vary depending on the FPGA configuration.
|
/linux-4.1.27/Documentation/scsi/ |
D | sym53c500_cs.txt | 21 for Tom Corner, and it works for me. Your mileage will probably vary.
|
D | ChangeLog.sym53c8xx | 74 frequency may vary depending on board design and thus,
|
/linux-4.1.27/Documentation/ABI/stable/ |
D | vdso | 22 ABI of those symbols is considered stable. It may vary across architectures,
|
D | sysfs-class-tpm | 105 value will vary depending on TPM chip version. For TPM 1.1 and
|
/linux-4.1.27/Documentation/misc-devices/ |
D | ad525x_dpot.txt | 23 and may vary greatly on a part-by-part basis. For exact interpretation of
|
D | apds990x.txt | 23 might vary quite much depending the spectrum of the light source.
|
D | eeprom | 52 industry-standard devices may vary by manufacturer.
|
/linux-4.1.27/Documentation/hwmon/ |
D | ina2xx | 64 The actual programmed interval may vary from the desired value.
|
D | sysfs-interface | 12 Note that motherboards vary widely in the connections to sensor chips.
|
/linux-4.1.27/Documentation/virtual/kvm/ |
D | s390-diag.txt | 30 The supported DIAGNOSE function codes vary by the userspace used. For
|
/linux-4.1.27/drivers/scsi/aic7xxx/ |
D | Kconfig.aic79xx | 23 vary this number based on device behavior. For devices with a
|
D | Kconfig.aic7xxx | 28 vary this number based on device behavior. For devices with a
|
/linux-4.1.27/Documentation/devicetree/bindings/video/ |
D | ti,omap-dss.txt | 13 the encoder modules vary.
|
/linux-4.1.27/Documentation/x86/ |
D | tlb.txt | 30 sizes of the flush will vary greatly depending on the workload as
|
/linux-4.1.27/Documentation/ |
D | printk-formats.txt | 79 resource_size_t) which can vary based on build options, regardless of 86 For printing a dma_addr_t type which can vary based on build options,
|
D | Changes | 54 The gcc version requirements may vary depending on the type of CPU in your
|
D | unaligned-memory-access.txt | 46 The effects of performing an unaligned memory access vary from architecture
|
D | svga.txt | 32 mode list displayed may vary as the kernel version changes, because the
|
D | xillybus.txt | 85 Since the communication requirements may vary significantly from one FPGA
|
D | kernel-parameters.txt | 409 CPU-intensive style benchmark, and it can vary highly in
|
/linux-4.1.27/Documentation/cpu-freq/ |
D | boost.txt | 36 single thread performance can vary. By explicitly disabling the boost
|
/linux-4.1.27/Documentation/ABI/testing/ |
D | sysfs-firmware-dmi | 25 is doing. Machine to machine experiences will vary.
|
D | sysfs-class-net | 29 Values vary based on the lower-level protocol used by the
|
D | sysfs-bus-coresight-devices-etm3x | 33 the access type register may vary on the version of the trace
|
D | sysfs-bus-iio | 557 to be enabled where p is how many it supports (which may vary 612 vary depending on the exact set requested. So if you want to be
|
/linux-4.1.27/Documentation/video4linux/ |
D | radiotrack.txt | 13 vary... I make no guarantees, claims or warranties to the suitability or
|
D | v4l2-controls.txt | 211 specific, so the contents of the menu will vary from device to device.
|
/linux-4.1.27/Documentation/i2c/busses/ |
D | i2c-piix4 | 87 The line may vary for different chipsets. Please consult the driver source
|
/linux-4.1.27/Documentation/devicetree/bindings/c6x/ |
D | dscr.txt | 5 function for SoC control or status. Details vary considerably among from SoC
|
/linux-4.1.27/tools/perf/Documentation/ |
D | perf-diff.txt | 25 could vary. So perf diff is based on the comparison of the files and
|
/linux-4.1.27/Documentation/gpio/ |
D | gpio.txt | 41 The exact capabilities of GPIOs vary between systems. Common options:
|
D | gpio-legacy.txt | 28 The exact capabilities of GPIOs vary between systems. Common options:
|
/linux-4.1.27/Documentation/networking/ |
D | vortex.txt | 365 - The contents of your report will vary a lot depending upon the 420 (The above may vary, depending upon which Linux distribution you use).
|
D | regulatory.txt | 149 Your implementation may vary (read EEPROM cache instead, for example).
|
D | ixgbe.txt | 38 the same Speed setting via ethtool. Results may vary if you mix speed settings.
|
D | ixgb.txt | 214 # several network benchmark tests, your mileage may vary
|
D | scaling.txt | 170 to the same CPU is CPU load imbalance if flows vary in packet rate.
|
D | can.txt | 954 These hardware filter capabilities vary from controller to
|
/linux-4.1.27/Documentation/input/ |
D | iforce-protocol.txt | 228 The amount of RAM may vary, I encountered values from 200 to 1000 bytes. Below
|
D | joystick-api.txt | 76 Hats vary from one joystick type to another. Some can be moved in 8
|
D | xpad.txt | 55 play first person shooters with a pad. Your mileage may vary.
|
D | input.txt | 121 However, because the devices vary wildly, you might happen to have a
|
/linux-4.1.27/Documentation/power/regulator/ |
D | consumer.txt | 102 change the current limit to vary the backlight brightness, USB drivers may want
|
/linux-4.1.27/Documentation/blockdev/ |
D | cciss.txt | 156 certain amount of time (which can vary depending on the command).
|
/linux-4.1.27/Documentation/arm64/ |
D | booting.txt | 109 end of the kernel image. The amount of space required will vary
|
/linux-4.1.27/Documentation/prctl/ |
D | seccomp_filter.txt | 158 the system call numbers may vary based on the specific invocation. If
|
/linux-4.1.27/Documentation/sound/alsa/ |
D | compress_offload.txt | 36 may vary from frame-to-frame. As a result, it is not possible to
|
/linux-4.1.27/arch/xtensa/ |
D | Kconfig | 265 vary. The frequency can be determined, however, by measuring
|
/linux-4.1.27/Documentation/device-mapper/ |
D | cache.txt | 213 As the default policy could vary between kernels, if you are relying on
|
D | thin-provisioning.txt | 72 The amount of metadata you need will vary according to how many blocks
|
/linux-4.1.27/arch/arm/mm/ |
D | Kconfig | 726 The exception vector can vary depending on the platform 753 ARM946E-S case, it can vary from 0KB to 1MB.
|
/linux-4.1.27/drivers/acpi/ |
D | Kconfig | 399 registers. Since the addresses and layout of these registers vary
|
/linux-4.1.27/drivers/net/irda/ |
D | Kconfig | 378 available capabilities may vary from one PXA2xx target to
|
/linux-4.1.27/Documentation/trace/ |
D | events.txt | 114 the fields prefixed with 'common_'. The other fields vary between
|
/linux-4.1.27/Documentation/laptops/ |
D | thinkpad-acpi.txt | 819 and the sounds vary from model to model. Here is the behavior on the 924 Often fan and temperature values vary between 925 readings. Since temperatures don't change vary fast, you can take
|
/linux-4.1.27/drivers/regulator/ |
D | Kconfig | 461 The regulators available on Palmas series chips vary depending
|
/linux-4.1.27/Documentation/cgroups/ |
D | unified-hierarchy.txt | 43 possible to vary the granularity depending on the specific controller.
|
/linux-4.1.27/drivers/scsi/ |
D | Kconfig | 693 performance improvement: your mileage may vary... 1412 performance improvement: your mileage may vary...
|
/linux-4.1.27/Documentation/filesystems/cifs/ |
D | README | 419 from the server). These inode numbers will vary after
|
/linux-4.1.27/Documentation/cdrom/ |
D | cdrom-standard.tex | 96 ejection. Undoubtedly, the capabilities of the different drives vary,
|
/linux-4.1.27/Documentation/devicetree/ |
D | booting-without-of.txt | 1017 format of this field may vary depending on whether or not the
|
/linux-4.1.27/Documentation/filesystems/ |
D | proc.txt | 854 impact of those factors will vary from system to system.
|