pci.9 - OpenGrok cross reference for /freebsd/share/man/man9/pci.9

Lines Matching +full:count +full:- +full:width
84 .Fn pci_alloc_msi "device_t dev" "int *count"
86 .Fn pci_alloc_msix "device_t dev" "int *count"
144 .Fn pci_read_config "device_t dev" "int reg" "int width"
148 .Fn pci_remap_msix "device_t dev" "int count" "const u_int *vectors"
158 .Fn pci_write_config "device_t dev" "int reg" "uint32_t val" "int width"
165 .Fa "int width"
172 .Fn pcie_read_config "device_t dev" "int reg" "int width"
176 .Fn pcie_write_config "device_t dev" "int reg" "uint32_t val" "int width"
214 .Fa width
227 .Fa width
232 function is used to modify the value of a register in the PCI-express
238 .Fa width
251 function is used to read the value of a register in the PCI-express
257 .Fa width
264 to a register in the PCI-express capability register set of device
269 .Fa width
297 .Bd -literal -offset indent
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.
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,
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
701 supports PCI Single-Root I/O Virtualization
702 .Pq SR-IOV .
703 A driver that supports SR-IOV must implement the
713 still successfully attaches, but runs with SR-IOV disabled.
718 parameters are used to define what device-specific configuration parameters the
719 device driver accepts when SR-IOV is enabled for the Physical Function
734 will return an error and SR-IOV will not be available on the PF device.
737 The SR-IOV infrastructure takes ownership of the
760 function is used to advise the SR-IOV infrastructure that the driver for the
761 given device is attempting to detach and that all SR-IOV resources for the
791 If the device is not in the fully-powered state
808 is not a PCI-express device or does not support Function Level Resets via
809 the PCI-express device control register,
826 busmastering is re-enabled and
849 .Pq MSI-X
855 MSI and MSI-X interrupts are available to PCI devices as one or more
858 A driver must ask the PCI bus to allocate MSI or MSI-X interrupts
863 before it can use MSI or MSI-X
868 resource if MSI or MSI-X interrupts have been allocated,
869 and attempts to allocate MSI or MSI-X interrupts will fail if the
873 A driver is only allowed to use either MSI or MSI-X,
889 .Fa *count
900 .Fa *count
913 requests to allocate a non-power of two count of messages will fail.
917 function is used to release any allocated MSI or MSI-X messages back
919 If any MSI or MSI-X
931 function returns the maximum number of MSI-X messages supported by the
934 If the device does not support MSI-X,
943 containing the MSI-X Pending Bit Array (PBA) for device
950 If the device does not support MSI-X,
953 returns -1.
958 containing the MSI-X vector table for device
965 If the device does not support MSI-X,
968 returns -1.
973 .Fa *count
974 MSI-X messages for the device
982 or if the system has a shortage of available MSI-X messages.
984 .Fa *count
988 For MSI-X messages,
991 resource identifies the index in the MSI-X table of the
993 A resource ID of one maps to the first index of the MSI-X table;
998 .Fa *count
1000 .Fa *count
1007 MSI-X does not require message counts that are powers of two.
1009 The BARs containing the MSI-X vector table and PBA must be
1024 to determine the pending status of the MSI-X message at table index
1027 this function returns a non-zero value;
1036 MSI-X messages are initially assigned to the first N table entries.
1054 .Fa count
1056 The array maps directly to the MSI-X table in that the first entry in
1057 the array specifies the message used for the first entry in the MSI-X
1060 MSI-X table,
1063 that no message should be assigned to the corresponding MSI-X table entry,
1066 where N is the count returned from the previous call to
1070 corresponding MSI-X table entry.
1075 each MSI-X table entry with a non-zero vector will have an associated
1080 MSI-X table entries that with a vector of zero will not have an
1087 are not used in the new distribution of messages in the MSI-X table,
1100 This includes the creation of Virtual Functions via SR-IOV.
1130 .%U https://docs.freebsd.org/en/books/developers-handbook/
1137 .%I Addison-Wesley
1138 .%O ISBN 0-201-30974-2
1141 .An -nosplit
1154 The PCI bus driver should allocate the MSI-X vector table and PBA internally