Lines Matching +full:non +full:- +full:pci

30 .Nm pci ,
78 .Nd PCI bus interface
197 set of functions are used for managing PCI devices.
208 function is used to read data from the PCI configuration
221 to the PCI configuration
232 function is used to modify the value of a register in the PCI-express
251 function is used to read the value of a register in the PCI-express
264 to a register in the PCI-express capability register set of device
275 .Fn pci
282 of a PCI device, given its
292 Note that in case the system has multiple PCI domains,
297 .Bd -literal -offset indent
305 of a PCI device, given its
321 of a PCI device, given its
331 function is used to locate the first instance of a PCI capability
351 function is used to locate the next instance of a PCI capability
374 function is used to locate the first instance of a PCI-express
390 PCI-express device,
395 function is used to locate the next instance of a PCI-express
449 function walks up the PCI device hierarchy to locate the PCI-express root
464 .Bl -hang -width ".Dv PCI_ID_RID"
469 This is needed by some interrupt controllers to route MSI and MSI-X interrupts.
482 is set to point at a read-only, null-terminated copy of the identifier
495 function is used to fetch the value of a single VPD read-only keyword
500 If the device supports VPD and provides a read-only value for the
504 is set to point at a read-only, null-terminated copy of the value,
521 device is not a PCI-express device,
535 pending flag in the PCI-express device status register.
557 is not a PCI-express device.
561 function enables PCI bus mastering for the device
594 The PCI bus will enable decoding automatically when a
606 PCI-express device.
609 device is not a PCI-express device,
616 PCI-express device.
619 device is not a PCI-express device,
625 sets the PCI-express maximum read request size for
635 device is not a PCI-express device,
647 The following power states are defined by PCI:
648 .Bl -hang -width ".Dv PCI_POWERSTATE_UNKNOWN"
654 Class-specific low-power state in which device context may or
659 Class-specific low-power state in which device context may or
683 to the PCI power state
705 supports PCI Single-Root I/O Virtualization
706 .Pq SR-IOV .
707 A driver that supports SR-IOV must implement the
717 still successfully attaches, but runs with SR-IOV disabled.
722 parameters are used to define what device-specific configuration parameters the
723 device driver accepts when SR-IOV is enabled for the Physical Function
738 will return an error and SR-IOV will not be available on the PF device.
741 The SR-IOV infrastructure takes ownership of the
764 function is used to advise the SR-IOV infrastructure that the driver for the
765 given device is attempting to detach and that all SR-IOV resources for the
788 functions can be used by a device driver to save and restore standard PCI
795 If the device is not in the fully-powered state
812 is not a PCI-express device or does not support Function Level Resets via
813 the PCI-express device control register,
830 busmastering is re-enabled and
853 .Pq MSI-X
854 are PCI capabilities that provide an alternate method for PCI
856 The legacy INTx interrupt is available to PCI devices as a
859 MSI and MSI-X interrupts are available to PCI devices as one or more
862 A driver must ask the PCI bus to allocate MSI or MSI-X interrupts
867 before it can use MSI or MSI-X
872 resource if MSI or MSI-X interrupts have been allocated,
873 and attempts to allocate MSI or MSI-X interrupts will fail if the
877 A driver is only allowed to use either MSI or MSI-X,
917 requests to allocate a non-power of two count of messages will fail.
921 function is used to release any allocated MSI or MSI-X messages back
923 If any MSI or MSI-X
935 function returns the maximum number of MSI-X messages supported by the
938 If the device does not support MSI-X,
947 containing the MSI-X Pending Bit Array (PBA) for device
954 If the device does not support MSI-X,
957 returns -1.
962 containing the MSI-X vector table for device
969 If the device does not support MSI-X,
972 returns -1.
978 MSI-X messages for the device
986 or if the system has a shortage of available MSI-X messages.
992 For MSI-X messages,
995 resource identifies the index in the MSI-X table of the
997 A resource ID of one maps to the first index of the MSI-X table;
1011 MSI-X does not require message counts that are powers of two.
1013 The BARs containing the MSI-X vector table and PBA must be
1028 to determine the pending status of the MSI-X message at table index
1031 this function returns a non-zero value;
1040 MSI-X messages are initially assigned to the first N table entries.
1060 The array maps directly to the MSI-X table in that the first entry in
1061 the array specifies the message used for the first entry in the MSI-X
1064 MSI-X table,
1067 that no message should be assigned to the corresponding MSI-X table entry,
1074 corresponding MSI-X table entry.
1079 each MSI-X table entry with a non-zero vector will have an associated
1084 MSI-X table entries that with a vector of zero will not have an
1091 are not used in the new distribution of messages in the MSI-X table,
1103 event handler is invoked every time a new PCI device is added to the system.
1104 This includes the creation of Virtual Functions via SR-IOV.
1108 event handler is invoked every time a PCI device is removed from the system.
1112 object of the relevant PCI device as
1119 .Xr pci 4 ,
1134 .%U https://docs.freebsd.org/en/books/developers-handbook/
1139 .%B PCI System Architecture
1141 .%I Addison-Wesley
1142 .%O ISBN 0-201-30974-2
1145 .An -nosplit
1151 The kernel PCI code has a number of references to
1153 These do not refer to the geographic location of PCI devices,
1154 but to the device number assigned by the combination of the PCI IDSEL
1156 This should be taken note of when working with the kernel PCI code.
1158 The PCI bus driver should allocate the MSI-X vector table and PBA internally