Lines Matching refs:service

8 and provides information on how to enable the service drivers to
31 and handled by corresponding service drivers.
38 services. To maintain a clean and simple solution each service
39 may have its own software service driver. In this case several
40 service drivers will compete for a single PCI-PCI Bridge device.
41 For example, if the PCI Express Root Port native hotplug service
43 kernel therefore does not load other service drivers for that Root
44 Port. In other words, it is impossible to have multiple service
48 To enable multiple service drivers running simultaneously requires
50 PCI Express Ports and distributes all provided service requests
51 to the corresponding service drivers as required. Some key
54 	- Allow multiple service drivers to run simultaneously on
57 	- Allow service drivers implemented in an independent
60 	- Allow one service driver to run on multiple PCI-PCI Bridge
64 	  device to requested service drivers.
78 All service drivers are PCI device drivers. As discussed above, it is
79 impossible to load any service driver once the kernel has loaded the
81 Model requires some minimal changes on existing service drivers that
82 imposes no impact on the functionality of existing service drivers.
84 A service driver is required to use the two APIs shown below to
85 register its service with the PCI Express Port Bus driver (see
86 section 5.2.1 & 5.2.2). It is important that a service driver
90 the PCI Express Port Bus driver from loading a service driver.
97 service driver should always calls pcie_port_service_register at
98 module init. Note that after service driver being loaded, calls
107 pci_unregister_driver. It's always called by service driver when a
112 Below is sample service driver code to initialize the port service
134 Below is a sample code for registering/unregistering a service
160 Since all service drivers of a PCI-PCI Bridge Port device are
170 INTx emulation mode. Since service drivers of the same PCI-PCI Bridge
171 port share the same physical device, if an individual service driver
173 behavior. For example, two service drivers run simultaneously on the
174 same physical Root Port. Both service drivers call pci_enable_msi to
175 request MSI based interrupts. A service driver may not know whether
176 any other service drivers have run on this Root Port. If either one
177 of them calls pci_disable_msi, it puts the other service driver
180 To avoid this situation all service drivers are not permitted to
183 transparent to service drivers. Service drivers need to know only
185 is passed in when the PCI Express Port Bus driver probes each service
193 call pci_enable_msix to request MSI-X interrupts. All service drivers
196 mode and this should be transparent to service drivers. Any attempt
197 by service driver to call pci_enable_msix/pci_disable_msix may
207 that all service drivers will be well behaved and not overwrite
208 other service driver's configuration settings.
212 Each service driver runs its PCI config operations on its own
215 between PME and AER. This patch assumes that all service drivers
216 will be well behaved and not overwrite other service driver's