Home
last modified time | relevance | path

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

12

/Linux-v4.19/tools/testing/selftests/x86/
Dtest_FCOMI.c19 PF = 1 << 2, enumerator
21 ARITH = CF | PF | ZF,
111 if ((res_fcomi_nan_1 & ARITH) != (ZF|CF|PF)) { in test_qnan()
140 if ((res_fcomi_nan_1 & ARITH) != (ZF|CF|PF)) { in testu_qnan()
171 if ((res_fcomi_nan_1 & ARITH) != (ZF|CF|PF)) { in testu_snan()
254 if ((res_fcomi_nan_1 & ARITH) != (ZF|CF|PF)) { in testp_qnan()
282 if ((res_fcomi_nan_1 & ARITH) != (ZF|CF|PF)) { in testup_qnan()
316 err |= test(CF|ZF|PF); in main()
317 err |= test_qnan(CF|ZF|PF); in main()
318 err |= testu_qnan(CF|ZF|PF); in main()
[all …]
Dtest_FCMOV.c44 PF = 1 << 2, enumerator
83 err |= !(fcmovb(PF) == 1.0); err |= !(fcmovnb(PF) != 1.0); in main()
84 err |= !(fcmove(PF) == 1.0); err |= !(fcmovne(PF) != 1.0); in main()
85 err |= !(fcmovbe(PF) == 1.0); err |= !(fcmovnbe(PF) != 1.0); in main()
86 err |= !(fcmovu(PF) != 1.0); err |= !(fcmovnu(PF) == 1.0); in main()
/Linux-v4.19/drivers/pinctrl/freescale/
Dpinctrl-imx27.c24 #define PF 5 macro
177 MX27_PAD_NFRB = PAD_ID(PF, 0),
178 MX27_PAD_NFCLE = PAD_ID(PF, 1),
179 MX27_PAD_NFWP_B = PAD_ID(PF, 2),
180 MX27_PAD_NFCE_B = PAD_ID(PF, 3),
181 MX27_PAD_NFALE = PAD_ID(PF, 4),
182 MX27_PAD_NFRE_B = PAD_ID(PF, 5),
183 MX27_PAD_NFWE_B = PAD_ID(PF, 6),
184 MX27_PAD_PC_POE = PAD_ID(PF, 7),
185 MX27_PAD_PC_RW_B = PAD_ID(PF, 8),
[all …]
Dpinctrl-imx21.c20 #define PF 5 macro
144 MX21_PAD_NFRB = PAD_ID(PF, 0),
145 MX21_PAD_NFCE = PAD_ID(PF, 1),
146 MX21_PAD_NFWP = PAD_ID(PF, 2),
147 MX21_PAD_NFCLE = PAD_ID(PF, 3),
148 MX21_PAD_NFALE = PAD_ID(PF, 4),
149 MX21_PAD_NFRE = PAD_ID(PF, 5),
150 MX21_PAD_NFWE = PAD_ID(PF, 6),
151 MX21_PAD_NFIO0 = PAD_ID(PF, 7),
152 MX21_PAD_NFIO1 = PAD_ID(PF, 8),
[all …]
/Linux-v4.19/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
309 This file is associated with the PF of a device that
325 affects only the VFs associated with a specific PF.
/Linux-v4.19/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-v4.19/drivers/staging/unisys/Documentation/ABI/
Dsysfs-platform-visorchipset60 PF device is being recovered in another guest.
62 Some SR-IOV devices have problems when the PF is reset without
63 first disabling all VFs attached to that PF. s-Par handles this
65 the script will disable the device. When the PF is recovered,
79 PF device is being recovered in another guest.
81 Some SR-IOV devices have problems when the PF is reset without
82 first disabling all VFs attached to that PF. s-Par handles this
84 the script will disable the device. When the PF is recovered,
/Linux-v4.19/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-v4.19/arch/m68k/include/asm/
DMC68328.h561 #define PF(x) (1 << (x)) macro
562 #define PF_A(x) PF((x) - 24) /* This is Port F specific only */
564 #define PF_A24 PF(0) /* Use A24 as PF(0) */
565 #define PF_A25 PF(1) /* Use A25 as PF(1) */
566 #define PF_A26 PF(2) /* Use A26 as PF(2) */
567 #define PF_A27 PF(3) /* Use A27 as PF(3) */
568 #define PF_A28 PF(4) /* Use A28 as PF(4) */
569 #define PF_A29 PF(5) /* Use A29 as PF(5) */
570 #define PF_A30 PF(6) /* Use A30 as PF(6) */
571 #define PF_A31 PF(7) /* Use A31 as PF(7) */
/Linux-v4.19/arch/arm/boot/dts/
Dsun8i-r16-nintendo-nes-classic.dts24 * UART0 is available on two ports: PB and PF, both are accessible.
25 * PF can also be used for the SD card so PB is preferred.
/Linux-v4.19/Documentation/admin-guide/mm/
Dsoft-dirty.rst26 modify a page at some virtual address the #PF occurs and the kernel sets
30 soft-dirty bits clear, the #PF-s that occur after that are processed fast.
35 While in most cases tracking memory changes by #PF-s is more than enough
/Linux-v4.19/drivers/net/ethernet/mellanox/mlx5/core/
DKconfig63 support in ConnectX NIC. MPFs is required for when multi-PF configuration
65 requesting PF.
74 enabled VFs and PF in two available modes:
/Linux-v4.19/drivers/tty/
Dn_gsm.c277 #define PF 0x10 macro
456 switch (control & ~PF) { in gsm_print_packet()
494 if (control & PF) in gsm_print_packet()
742 if (msg->ctrl == UI || msg->ctrl == (UI|PF)) in __gsm_data_queue()
1478 gsm_command(dlci->gsm, dlci->addr, SABM|PF); in gsm_dlci_t1()
1480 } else if (!dlci->addr && gsm->control == (DM | PF)) { in gsm_dlci_t1()
1494 gsm_command(dlci->gsm, dlci->addr, DISC|PF); in gsm_dlci_t1()
1519 gsm_command(dlci->gsm, dlci->addr, SABM|PF); in gsm_dlci_begin_open()
1541 gsm_command(dlci->gsm, dlci->addr, DISC|PF); in gsm_dlci_begin_close()
1753 if ((gsm->control & ~PF) == UI) in gsm_queue()
[all …]
/Linux-v4.19/net/netfilter/ipset/
Dip_set_hash_ipmac.c84 #define PF 4 macro
191 #undef PF
196 #define PF 6 macro
/Linux-v4.19/Documentation/networking/
Dnet_failover.rst100 PF=enp66s0f0
109 bridge fdb del $MAC dev $PF master
111 ip link set $PF vf $VF_NUM mac $ZERO_MAC
Dhinic.txt12 (PF).
25 19e5:1822 - HiNIC PF
58 Management (MGMT) - the PF to MGMT channel that uses API CMD for sending MGMT
Di40e.txt80 which VF. Note that 0 is the PF, so the VF identifier is offset by 1. For
153 the hardware and not transmitted. An interrupt is sent to the PF driver
156 When a spoofed packet is detected the PF driver will send the following
Di40evf.txt18 newer Physical Function (PF) driver compiled with CONFIG_PCI_IOV.
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
/Linux-v4.19/drivers/pci/
DKconfig71 tristate "PCI PF Stub driver"
76 require SR-IOV support, while at the same time the PF itself is
/Linux-v4.19/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-v4.19/Documentation/devicetree/bindings/pinctrl/
Dingenic,pinctrl.txt14 PD, for a total of 128 pins. The jz4780 contains 6 GPIO ports, PA to PF, for a
/Linux-v4.19/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-v4.19/Documentation/virtual/kvm/
Dcpuid.txt61 KVM_FEATURE_ASYNC_PF_VMEXIT || 10 || paravirtualized async PF VM exit

12