Home
last modified time | relevance | path

Searched refs:vary (Results 1 – 25 of 110) sorted by relevance

12345

/Linux-v5.4/drivers/usb/misc/
Dusbtest.c33 __u32 vary; member
50 __u32 vary; member
458 int vary, in simple_io() argument
493 if (vary) { in simple_io()
496 len += vary; in simple_io()
499 len = (vary < max) ? vary : max; in simple_io()
536 alloc_sglist(int nents, int max, int vary, struct usbtest_dev *dev, int pipe) in alloc_sglist() argument
577 if (vary) { in alloc_sglist()
578 size += vary; in alloc_sglist()
581 size = (vary < max) ? vary : max; in alloc_sglist()
[all …]
/Linux-v5.4/Documentation/driver-api/firmware/
Dintroduction.rst6 for functionality from userspace, the uses vary:
22 Which one you use vary depending on your requirements, the rule of thumb
/Linux-v5.4/Documentation/devicetree/bindings/spi/
Dnvidia,tegra114-spi.txt30 Tap values vary based on the platform design trace lengths from Tegra SPI
35 Tap values vary based on the platform design trace lengths from Tegra SPI
/Linux-v5.4/tools/usb/
Dtestusb.c47 unsigned vary; member
387 param.vary = 1024; in main()
429 if (parse_num(&param.vary, optarg)) in main()
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-platform-dell-smbios19 Tokens will vary from machine to machine, and
Dsysfs-bus-iio-magnetometer-hmc584313 Note: The effect of this configuration may vary
Dsysfs-class-fpga-manager21 though some steps may get skipped. Valid FPGA states will vary
/Linux-v5.4/arch/m68k/hp300/
DREADME.hp30010 combination seems to work for me. Your mileage may vary.
/Linux-v5.4/Documentation/devicetree/bindings/mtd/partitions/
Dredboot-fis.txt10 This block size will vary depending on flash but is typically
Dbrcm,bcm947xx-cfe-partitions.txt7 meanings can also vary so fixed partitioning can't be used.
/Linux-v5.4/Documentation/devicetree/bindings/input/
De3x0-button.txt15 Note: Interrupt numbers might vary depending on the FPGA configuration.
/Linux-v5.4/Documentation/devicetree/bindings/interrupt-controller/
Darm,nvic.txt5 vary in the number of interrupts and priority bits per interrupt.
/Linux-v5.4/Documentation/media/uapi/v4l/
Dpixfmt-tch-td08.rst25 Delta values may range from -128 to 127. Typically the values will vary through
Dpixfmt-z16.rst25 can vary and has to be negotiated with the device separately. Each pixel
Dpixfmt-tch-td16.rst26 Delta values may range from -32768 to 32767. Typically the values will vary
/Linux-v5.4/Documentation/scsi/
Dsym53c500_cs.txt21 for Tom Corner, and it works for me. Your mileage will probably vary.
/Linux-v5.4/Documentation/ABI/stable/
Dvdso23 ABI of those symbols is considered stable. It may vary across architectures,
/Linux-v5.4/Documentation/devicetree/bindings/net/wireless/
Dqcom,ath10k.txt62 as an array, the length can vary between
65 the length can vary between hw versions.
Dmarvell-8xxx.txt45 can vary between hw versions.
/Linux-v5.4/Documentation/misc-devices/
Dad525x_dpot.txt23 and may vary greatly on a part-by-part basis. For exact interpretation of
/Linux-v5.4/Documentation/hwmon/
Dina2xx.rst85 The actual programmed interval may vary from the desired value.
/Linux-v5.4/Documentation/virt/kvm/
Ds390-diag.txt30 The supported DIAGNOSE function codes vary by the userspace used. For
/Linux-v5.4/Documentation/devicetree/bindings/mailbox/
Dnvidia,tegra186-hsp.txt52 may vary by instance of the HSP block and SoC generation.
/Linux-v5.4/Documentation/devicetree/bindings/phy/
Dqcom-qusb2-phy.txt33 tuning parameter that may vary for different boards of same SOC.
/Linux-v5.4/Documentation/media/uapi/mediactl/
Dmedia-ioc-device-info.rst110 vary across reboots or device unplug/replug.

12345