Home
last modified time | relevance | path

Searched full:vary (Results 1 – 25 of 329) sorted by relevance

12345678910>>...14

/Linux-v6.1/tools/perf/pmu-events/arch/x86/amdzen1/
Dfloating-point.json81 …floating-point Ops that have retired. The number of events logged per cycle can vary from 0 to 8.",
88 …ng-point Ops that have retired. The number of events logged per cycle can vary from 0 to 8. Divide…
95 …ng-point Ops that have retired. The number of events logged per cycle can vary from 0 to 8. Multip…
102 …ng-point Ops that have retired. The number of events logged per cycle can vary from 0 to 8. Add/su…
109 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This …
116 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This …
123 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This …
130 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This …
137 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This …
144 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This …
[all …]
Dcore.json11 … interrupts, microcode assists, etc.). The number of events logged per cycle can vary from 0 to 4."
123 …branch instructions retired per cycle. The number of events logged per cycle can vary from 0 to 3."
/Linux-v6.1/tools/perf/pmu-events/arch/x86/amdzen2/
Dfloating-point.json40 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This …
46 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This …
53 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This …
59 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This …
65 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This …
Dcore.json11 … interrupts, microcode assists, etc.). The number of events logged per cycle can vary from 0 to 8."
128 …se-branch instructions retired per cycle. The number of events logged per cycle can vary from 0-8."
/Linux-v6.1/Documentation/devicetree/bindings/phy/
Dqcom,qusb2-phy.yaml96 tuning parameter that may vary for different boards of same SOC.
105 tuning parameter that may vary for different boards of same SOC.
114 tuning parameter that may vary for different boards of same SOC.
155 threshold and may vary for different boards of same SOC.
/Linux-v6.1/tools/perf/pmu-events/arch/x86/amdzen3/
Dfloating-point.json40 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This …
46 …umber of retired SSE/AVX FLOPs. The number of events logged per cycle can vary from 0 to 64. This …
52 …umber of retired SSE/AVX FLOPs. The number of events logged per cycle can vary from 0 to 64. This …
58 …umber of retired SSE/AVX FLOPs. The number of events logged per cycle can vary from 0 to 64. This …
64 …umber of retired SSE/AVX FLOPs. The number of events logged per cycle can vary from 0 to 64. This …
/Linux-v6.1/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-v6.1/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-v6.1/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-v6.1/drivers/i3c/master/mipi-i3c-hci/
Dxfer_mode_rate.h20 * Presence and definitions for indexes beyond these ones may vary.
45 * rates may vary slightly and are also specified in the Data Transfer
/Linux-v6.1/tools/usb/
Dtestusb.c47 unsigned vary; member
395 param.vary = 1024; in main()
436 case 'v': /* vary packet size by ... */ in main()
437 if (parse_num(&param.vary, optarg)) in main()
457 "\t-v vary default 1024\n", in main()
/Linux-v6.1/Documentation/ABI/testing/
Dsysfs-platform-dell-smbios19 Tokens will vary from machine to machine, and
Dsysfs-bus-iio-magnetometer-hmc584318 The effect of this configuration may vary
/Linux-v6.1/arch/m68k/hp300/
DREADME.hp30010 combination seems to work for me. Your mileage may vary.
/Linux-v6.1/drivers/net/wireless/ath/ath9k/
Dcommon-spectral.h59 /* WARNING: don't actually use this struct! MAC may vary the amount of
88 /* WARNING: don't actually use this struct! MAC may vary the amount of
/Linux-v6.1/Documentation/devicetree/bindings/input/
De3x0-button.txt15 Note: Interrupt numbers might vary depending on the FPGA configuration.
/Linux-v6.1/include/linux/spi/
Dad7877.h4 /* Touchscreen characteristics vary between boards and models. The
/Linux-v6.1/Documentation/devicetree/bindings/interrupt-controller/
Darm,nvic.txt5 vary in the number of interrupts and priority bits per interrupt.
/Linux-v6.1/Documentation/devicetree/bindings/mtd/partitions/
Dredboot-fis.yaml13 This block size will vary depending on flash but is typically
/Linux-v6.1/usr/
Dinitramfs_data.S17 The above example is for i386 - the parameters vary from architectures.
/Linux-v6.1/Documentation/devicetree/bindings/hwmon/
Damd,sbrmi.yaml31 socket 0 and 70h for socket 1, but it could vary based on hardware
Damd,sbtsi.yaml32 0 and 90h for socket 1, but it could vary based on hardware address
/Linux-v6.1/Documentation/scsi/
Dsym53c500_cs.rst27 for Tom Corner, and it works for me. Your mileage will probably vary.
/Linux-v6.1/Documentation/ABI/stable/
Dvdso29 ABI of those symbols is considered stable. It may vary across architectures,
/Linux-v6.1/Documentation/hwmon/
Dsbtsi_temp.rst19 98h for socket 0 and 90h for socket 1, but it could vary based on hardware

12345678910>>...14