Home
last modified time | relevance | path

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

12345678910>>...12

/linux/tools/perf/pmu-events/arch/x86/amdzen1/
H A 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 …]
H A 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/tools/perf/pmu-events/arch/x86/amdzen2/
H A 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 …
H A 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/tools/perf/pmu-events/arch/x86/amdzen3/
H A 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/Documentation/driver-api/firmware/
H A Dintroduction.rst6 for functionality from userspace, the uses vary:
22 Which one you use vary depending on your requirements, the rule of thumb
/linux/arch/arm64/boot/dts/qcom/
H A Dmsm8916-samsung-j3-common.dtsi44 /* GPIO pins vary depending on model variant */
48 /* GPIO pins vary depending on model variant */
/linux/drivers/i3c/master/mipi-i3c-hci/
H A 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/tools/usb/
H A 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/drivers/net/wireless/ath/ath9k/
H A 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/Documentation/ABI/testing/
H A Dsysfs-platform-dell-smbios19 Tokens will vary from machine to machine, and
H A Dsysfs-bus-iio-magnetometer-hmc584318 The effect of this configuration may vary
/linux/arch/m68k/hp300/
H A DREADME.hp30010 combination seems to work for me. Your mileage may vary.
/linux/Documentation/devicetree/bindings/input/
H A De3x0-button.txt15 Note: Interrupt numbers might vary depending on the FPGA configuration.
/linux/include/linux/spi/
H A Dad7877.h4 /* Touchscreen characteristics vary between boards and models. The
/linux/drivers/gpu/drm/amd/display/dc/
H A Ddm_pp_smu.h128 * FCLK will vary with DPM, but never below requested hard min
188 * UCLK will vary with DPM, but never below requested hard min
/linux/arch/powerpc/tools/
H A Dgcc-check-fpatchable-function-entry.sh10 # Output from -fpatchable-function-entry can only vary on ppc64 elfv2, so this
/linux/Documentation/devicetree/bindings/interrupt-controller/
H A Darm,nvic.txt5 vary in the number of interrupts and priority bits per interrupt.
/linux/usr/
H A Dinitramfs_data.S17 The above example is for i386 - the parameters vary from architectures.
/linux/Documentation/scsi/
H A Dsym53c500_cs.rst27 for Tom Corner, and it works for me. Your mileage will probably vary.
/linux/Documentation/devicetree/bindings/mtd/partitions/
H A Dredboot-fis.yaml13 This block size will vary depending on flash but is typically
/linux/Documentation/devicetree/bindings/hwmon/
H A Damd,sbrmi.yaml31 socket 0 and 70h for socket 1, but it could vary based on hardware
H A Damd,sbtsi.yaml32 0 and 90h for socket 1, but it could vary based on hardware address
/linux/drivers/net/phy/
H A Dopen_alliance_helpers.h31 * bits may vary, but generally:
/linux/Documentation/devicetree/bindings/net/wireless/
H A Dqcom,ath10k.yaml99 can vary between hardware versions.
110 Pre-calibration data as a byte array. The length can vary between

12345678910>>...12