Home
last modified time | relevance | path

Searched refs:PF (Results 1 – 29 of 29) sorted by relevance

/linux-4.4.14/tools/testing/selftests/x86/
Dtest_FCOMI.c18 PF = 1 << 2, enumerator
20 ARITH = CF | PF | ZF,
110 if ((res_fcomi_nan_1 & ARITH) != (ZF|CF|PF)) { in test_qnan()
139 if ((res_fcomi_nan_1 & ARITH) != (ZF|CF|PF)) { in testu_qnan()
170 if ((res_fcomi_nan_1 & ARITH) != (ZF|CF|PF)) { in testu_snan()
253 if ((res_fcomi_nan_1 & ARITH) != (ZF|CF|PF)) { in testp_qnan()
281 if ((res_fcomi_nan_1 & ARITH) != (ZF|CF|PF)) { in testup_qnan()
315 err |= test(CF|ZF|PF); in main()
316 err |= test_qnan(CF|ZF|PF); in main()
317 err |= testu_qnan(CF|ZF|PF); in main()
[all …]
Dtest_FCMOV.c43 PF = 1 << 2, enumerator
82 err |= !(fcmovb(PF) == 1.0); err |= !(fcmovnb(PF) != 1.0); in main()
83 err |= !(fcmove(PF) == 1.0); err |= !(fcmovne(PF) != 1.0); in main()
84 err |= !(fcmovbe(PF) == 1.0); err |= !(fcmovnbe(PF) != 1.0); in main()
85 err |= !(fcmovu(PF) != 1.0); err |= !(fcmovnu(PF) == 1.0); in main()
/linux-4.4.14/drivers/pinctrl/freescale/
Dpinctrl-imx27.c30 #define PF 5 macro
183 MX27_PAD_NFRB = PAD_ID(PF, 0),
184 MX27_PAD_NFCLE = PAD_ID(PF, 1),
185 MX27_PAD_NFWP_B = PAD_ID(PF, 2),
186 MX27_PAD_NFCE_B = PAD_ID(PF, 3),
187 MX27_PAD_NFALE = PAD_ID(PF, 4),
188 MX27_PAD_NFRE_B = PAD_ID(PF, 5),
189 MX27_PAD_NFWE_B = PAD_ID(PF, 6),
190 MX27_PAD_PC_POE = PAD_ID(PF, 7),
191 MX27_PAD_PC_RW_B = PAD_ID(PF, 8),
[all …]
Dpinctrl-imx21.c25 #define PF 5 macro
149 MX21_PAD_NFRB = PAD_ID(PF, 0),
150 MX21_PAD_NFCE = PAD_ID(PF, 1),
151 MX21_PAD_NFWP = PAD_ID(PF, 2),
152 MX21_PAD_NFCLE = PAD_ID(PF, 3),
153 MX21_PAD_NFALE = PAD_ID(PF, 4),
154 MX21_PAD_NFRE = PAD_ID(PF, 5),
155 MX21_PAD_NFWE = PAD_ID(PF, 6),
156 MX21_PAD_NFIO0 = PAD_ID(PF, 7),
157 MX21_PAD_NFIO1 = PAD_ID(PF, 8),
[all …]
/linux-4.4.14/Documentation/ABI/testing/
Ddebugfs-driver-genwqe10 Only available for PF.
16 Only available for PF.
22 Only available for PF.
28 Only available for PF.
35 Only available for PF.
41 Only available for PF.
47 Only available for PF.
53 Only available for PF.
79 Only available for PF.
84 Description: Dump job timeout register values for PF and VFs.
[all …]
Dsysfs-bus-pci237 function (PF) can support. Typically, this is the value reported
238 in the PF's SR-IOV extended capability structure's TotalVFs
250 Functions (VFs) on the physical function (PF). A read of this
251 file will return the number of VFs that are enabled on this PF.
255 of VFs that should be enabled on the PF; the value written
/linux-4.4.14/arch/m68k/68000/
Dm68VZ328.c80 PFSEL |= PF(5); /* select pin as I/O */ in init_hardware()
81 PFDIR |= PF(5); /* select pin as output */ in init_hardware()
82 PFDATA &= ~PF(5); /* set pin low */ in init_hardware()
85 PFDATA |= PF(5); in init_hardware()
87 PFDATA &= ~PF(5); in init_hardware()
/linux-4.4.14/Documentation/PCI/
Dpci-iov-howto.txt15 devices. The physical device is referred to as Physical Function (PF)
17 Allocation of the VF can be dynamically controlled by the PF via
19 not enabled and the PF behaves as traditional PCIe device. Once it's
31 In the first method, the device driver (PF driver) will control the
33 If the hardware has SR-IOV capability, loading its PF driver would
34 enable it and all VFs associated with the PF. Some PF drivers require
37 enable and disable the VFs associated with a PCIe PF. This method
38 enables per-PF, VF enable/disable values versus the first method,
/linux-4.4.14/drivers/staging/unisys/Documentation/ABI/
Dsysfs-platform-visorchipset74 PF device is being recovered in another guest.
76 Some SR-IOV devices have problems when the PF is reset without
77 first disabling all VFs attached to that PF. s-Par handles this
79 the script will disable the device. When the PF is recovered,
93 PF device is being recovered in another guest.
95 Some SR-IOV devices have problems when the PF is reset without
96 first disabling all VFs attached to that PF. s-Par handles this
98 the script will disable the device. When the PF is recovered,
/linux-4.4.14/arch/m68k/include/asm/
DMC68328.h559 #define PF(x) (1 << (x)) macro
560 #define PF_A(x) PF((x) - 24) /* This is Port F specific only */
562 #define PF_A24 PF(0) /* Use A24 as PF(0) */
563 #define PF_A25 PF(1) /* Use A25 as PF(1) */
564 #define PF_A26 PF(2) /* Use A26 as PF(2) */
565 #define PF_A27 PF(3) /* Use A27 as PF(3) */
566 #define PF_A28 PF(4) /* Use A28 as PF(4) */
567 #define PF_A29 PF(5) /* Use A29 as PF(5) */
568 #define PF_A30 PF(6) /* Use A30 as PF(6) */
569 #define PF_A31 PF(7) /* Use A31 as PF(7) */
DMC68EZ328.h471 #define PF(x) (1 << (x)) macro
DMC68VZ328.h481 #define PF(x) (1 << (x)) macro
/linux-4.4.14/Documentation/vm/
Dsoft-dirty.txt22 modify a page at some virtual address the #PF occurs and the kernel sets
26 soft-dirty bits clear, the #PF-s that occur after that are processed fast.
31 While in most cases tracking memory changes by #PF-s is more than enough
/linux-4.4.14/arch/blackfin/mach-bf533/
DKconfig71 int "PF Interrupt A"
74 int "PF Interrupt B"
/linux-4.4.14/drivers/tty/
Dn_gsm.c290 #define PF 0x10 macro
469 switch (control & ~PF) { in gsm_print_packet()
507 if (control & PF) in gsm_print_packet()
755 if (msg->ctrl == UI || msg->ctrl == (UI|PF)) in __gsm_data_queue()
1481 gsm_command(dlci->gsm, dlci->addr, SABM|PF); in gsm_dlci_t1()
1489 gsm_command(dlci->gsm, dlci->addr, DISC|PF); in gsm_dlci_t1()
1514 gsm_command(dlci->gsm, dlci->addr, SABM|PF); in gsm_dlci_begin_open()
1536 gsm_command(dlci->gsm, dlci->addr, DISC|PF); in gsm_dlci_begin_close()
1750 if ((gsm->control & ~PF) == UI) in gsm_queue()
1777 case SABM|PF: in gsm_queue()
[all …]
/linux-4.4.14/Documentation/networking/
Di40e.txt81 the hardware and not transmitted. An interrupt is sent to the PF driver
84 When a spoofed packet is detected the PF driver will send the following
Digb.txt98 the hardware and not transmitted. An interrupt is sent to the PF driver
101 When a spoofed packet is detected the PF driver will send the following
Dixgbe.txt290 the hardware and not transmitted. An interrupt is sent to the PF driver
293 When a spoofed packet is detected the PF driver will send the following
/linux-4.4.14/Documentation/s390/
D3270.txt215 Some of the Program Function (PF) and Program Attention (PA) keys are
228 No PF key is preassigned to cause a job suspension, but you may cause a
230 assign this function to a PF key. To make PF7 cause job suspension,
245 PF11 rotates forward. You may assign the backward function to any PF
258 Have a command you issue frequently? Assign it to a PF or PA key! Use
/linux-4.4.14/arch/blackfin/mach-bf518/
DKconfig25 PF{1,2,3,4,5,6} <-> PWM_{AH,AL,BH,BL,CH,CL}
30 PF{11,12,13,14} <-> PWM_{AH,AL,BH,BL}
/linux-4.4.14/Documentation/powerpc/
Dpci_iov_resource_on_powernv.txt155 The PCIe SR-IOV feature allows a single Physical Function (PF) to
156 support several Virtual Functions (VFs). Registers in the PF's SR-IOV
163 software uses VF BAR registers in the *PF* SR-IOV Capability to
167 When a VF BAR in the PF SR-IOV Capability is programmed, it sets the
169 PF SR-IOV Capability is programmed to enable eight VFs, and it has a
/linux-4.4.14/sound/soc/blackfin/
DKconfig113 int "PF pin for AD73311L Chip Select"
/linux-4.4.14/arch/x86/kernel/
Duprobes.c597 COND(7a, 7b, XF(PF)) \
/linux-4.4.14/drivers/isdn/hisax/
Disdnl2.c449 u_char PF; in get_PollFlagFree() local
451 PF = get_PollFlag(st, skb); in get_PollFlagFree()
453 return (PF); in get_PollFlagFree()
/linux-4.4.14/drivers/isdn/mISDN/
Dlayer2.c657 u_char PF; in get_PollFlagFree() local
659 PF = get_PollFlag(l2, skb); in get_PollFlagFree()
661 return PF; in get_PollFlagFree()
/linux-4.4.14/Documentation/virtual/kvm/
Dmmu.txt355 (user write faults generate a #PF)
367 directly inject #PF to guest due to failed permission check.
Dtimekeeping.txt248 bit 6 = periodic interrupt flag (PF)
/linux-4.4.14/arch/x86/kvm/
Dtrace.h270 EXS(DF), EXS(TS), EXS(NP), EXS(SS), EXS(GP), EXS(PF), \
/linux-4.4.14/Documentation/filesystems/
Dcoda.txt1501 55..44.. ZZAAPPFFIILLEE