Lines Matching +full:resource +full:- +full:id

113 .Fn pci_get_id "device_t dev" "enum pci_id_type type" "uintptr_t *id"
223 function is used to modify the value of a register in the PCI-express
242 function is used to read the value of a register in the PCI-express
255 to a register in the PCI-express capability register set of device
288 .Bd -literal -offset indent
325 The capability to locate is specified by ID via
359 function is used to locate the first instance of a PCI-express
362 The extended capability to locate is specified by ID via
375 PCI-express device,
380 function is used to locate the next instance of a PCI-express
434 function walks up the PCI device hierarchy to locate the PCI-express root
449 .Bl -hang -width ".Dv PCI_ID_RID"
453 Read the MSI routing ID.
454 This is needed by some interrupt controllers to route MSI and MSI-X interrupts.
467 is set to point at a read-only, null-terminated copy of the identifier
480 function is used to fetch the value of a single VPD read-only keyword
485 If the device supports VPD and provides a read-only value for the
489 is set to point at a read-only, null-terminated copy of the value,
506 device is not a PCI-express device,
520 pending flag in the PCI-express device status register.
542 is not a PCI-express device.
573 argument specifies which resource is affected; this can be either
583 resource is activated via
591 PCI-express device.
594 device is not a PCI-express device,
601 PCI-express device.
604 device is not a PCI-express device,
610 sets the PCI-express maximum read request size for
620 device is not a PCI-express device,
633 .Bl -hang -width ".Dv PCI_POWERSTATE_UNKNOWN"
639 Class-specific low-power state in which device context may or
644 Class-specific low-power state in which device context may or
676 supports PCI Single-Root I/O Virtualization
677 .Pq SR-IOV .
678 A driver that supports SR-IOV must implement the
688 still successfully attaches, but runs with SR-IOV disabled.
693 parameters are used to define what device-specific configuration parameters the
694 device driver accepts when SR-IOV is enabled for the Physical Function
709 will return an error and SR-IOV will not be available on the PF device.
712 The SR-IOV infrastructure takes ownership of the
735 function is used to advise the SR-IOV infrastructure that the driver for the
736 given device is attempting to detach and that all SR-IOV resources for the
766 If the device is not in the fully-powered state
783 is not a PCI-express device or does not support Function Level Resets via
784 the PCI-express device control register,
801 busmastering is re-enabled and
824 .Pq MSI-X
829 resource with a resource ID of zero.
830 MSI and MSI-X interrupts are available to PCI devices as one or more
832 resources with resource IDs greater than zero.
833 A driver must ask the PCI bus to allocate MSI or MSI-X interrupts
838 before it can use MSI or MSI-X
843 resource if MSI or MSI-X interrupts have been allocated,
844 and attempts to allocate MSI or MSI-X interrupts will fail if the
847 resource.
848 A driver is only allowed to use either MSI or MSI-X,
882 resource IDs beginning with one.
888 requests to allocate a non-power of two count of messages will fail.
892 function is used to release any allocated MSI or MSI-X messages back
894 If any MSI or MSI-X
906 function returns the maximum number of MSI-X messages supported by the
909 If the device does not support MSI-X,
918 containing the MSI-X Pending Bit Array (PBA) for device
920 The returned value can be used as the resource ID with
925 If the device does not support MSI-X,
928 returns -1.
933 containing the MSI-X vector table for device
935 The returned value can be used as the resource ID with
940 If the device does not support MSI-X,
943 returns -1.
949 MSI-X messages for the device
957 or if the system has a shortage of available MSI-X messages.
963 For MSI-X messages,
964 the resource ID for each
966 resource identifies the index in the MSI-X table of the
968 A resource ID of one maps to the first index of the MSI-X table;
969 a resource ID two identifies the second index in the table, etc.
982 MSI-X does not require message counts that are powers of two.
984 The BARs containing the MSI-X vector table and PBA must be
999 to determine the pending status of the MSI-X message at table index
1002 this function returns a non-zero value;
1011 MSI-X messages are initially assigned to the first N table entries.
1031 The array maps directly to the MSI-X table in that the first entry in
1032 the array specifies the message used for the first entry in the MSI-X
1035 MSI-X table,
1038 that no message should be assigned to the corresponding MSI-X table entry,
1045 corresponding MSI-X table entry.
1050 each MSI-X table entry with a non-zero vector will have an associated
1052 resource whose resource ID corresponds to the table index as described
1055 MSI-X table entries that with a vector of zero will not have an
1058 resource.
1062 are not used in the new distribution of messages in the MSI-X table,
1075 This includes the creation of Virtual Functions via SR-IOV.
1105 .%U https://docs.freebsd.org/en/books/developers-handbook/
1112 .%I Addison-Wesley
1113 .%O ISBN 0-201-30974-2
1116 .An -nosplit
1129 The PCI bus driver should allocate the MSI-X vector table and PBA internally