Home
last modified time | relevance | path

Searched refs:PCI (Results 1 – 25 of 916) sorted by relevance

12345678910>>...37

/linux/Documentation/translations/zh_CN/PCI/
H A Dpciebus-howto.rst34 一个PCI Express端口是一个逻辑的PCI-PCI桥结构。有两种类型的PCI Express端
35 口：根端口和交换端口。根端口从PCI Express根综合体发起一个PCI Express链接，
36 交换端口将PCI Express链接连接到内部逻辑PCI总线。交换机端口，其二级总线代表
38 路由总线桥接到代表来自PCI Express交换机的下游PCI Express链接的总线。
49 PCI Express端口是一个具有多个不同服务的PCI-PCI桥设备。为了保持一个干净和简
51 竞争一个PCI-PCI桥设备。例如，如果PCI Express根端口的本机热拔插服务驱动程序
52 首先被加载，它就会要求一个PCI-PCI桥根端口。因此，内核不会为该根端口加载其他服
54 PCI-PCI桥设备上。
60 - 允许在一个PCI-PCI桥接端口设备上同时运行多个服务驱动。
64 - 允许一个服务驱动程序在多个PCI-PCI桥接端口设备上运行。
[all …]
H A Dpci.rst17 如何写Linux PCI驱动
24 的芯片组，并且PCI设备有不同的要求（呃，“特性”），结果是Linux内核中的PCI支持并不
37 请将有关Linux PCI API的问题/评论/补丁发送到“Linux PCI”
41 PCI驱动的结构体
43 PCI驱动通过pci_register_driver()在系统中“发现”PCI设备。实际上，它是反过来的。
74 如果没有配置PCI子系统（没有设置 ``CONFIG_PCI`` ），下面描述的大多数PCI函数被定
150 PCI设备被多个驱动程序控制的主要原因是一个PCI设备实现了几个不同的HW服务。例如，组合的
194 启用PCI设备
266 样，这包括所有PCI-X和PCIe兼容设备的驱动程序。许多64位“PCI”设备（在PCI-X之前）
327 PCI设备关闭
[all …]
H A Dacpi-info.rst4 :Original: Documentation/PCI/acpi-info.rst
14 PCI主桥的ACPI注意事项
21 下面的PCI配置空间的方法、主桥转发到PCI的地址空间窗口（使用_CRS）以及传统的INTx
24 在主桥下面的PCI设备，通常不需要通过ACPI描述。操作系统可以通过标准的PCI枚举机制来
27 来描述这些连接，这种情况下ACPI可以描述PCI设备。
43 们转发到PCI总线上的所有窗口，以及不转发到PCI的主桥本身的寄存器。主桥的寄存器包括次要/下
115 [6] PCI Firmware 3.2, sec 4.1.2:
122 [7] PCI Express 4.0, sec 7.2.2:
126 [8] PCI Firmware 3.2, sec 4.1.2:
127 MCFG表是一个ACPI表，用于沟通的基础地址对应的非热的可移动的PCI段组范围内的PCI段组在
[all …]
H A Dsysfs-pci.rst4 :Original: Documentation/PCI/sysfs-pci.rst
15 通过sysfs访问PCI设备资源
18 sysfs，通常挂载在/sys，在支持它的平台上提供对PCI资源的访问。例如，一个特定的总线可能看起
48 class PCI级别 (ascii, ro)
49 config PCI配置空间 (binary, rw)
50 device PCI设备 (ascii, ro)
55 resource PCI资源主机地址 (ascii, ro)
58 revision PCI修订版 (ascii, ro)
62 vendor PCI供应商 (ascii, ro)
93 设备将被从任何连接到它的驱动程序中移除。移除PCI根总线是不允许的。
[all …]
H A Dmsi-howto.rst5 :Original: Documentation/PCI/msi-howto.rst
35 MSI能力首次在PCI 2.2中规定，后来在PCI 3.0中得到增强，允许对每个中断进行单独屏蔽。
46 基于针脚的PCI中断通常在几个设备之间共享。为了支持这一点，内核必须调用每个与中断相
50 之前，中断就已经到达了（这在PCI-PCI桥后面的设备中变得更有可能）。为了确保所有的数
51 据已经到达内存中，中断处理程序必须在引发中断的设备上读取一个寄存器。PCI事务排序规
55 PCI设备每个功能只能支持一个基于引脚的中断。通常情况下，驱动程序必须查询设备以找出
79 大部分沉重的工作是在PCI层为驱动程序完成的。驱动程序只需要请求PCI层为这个设备设置
89 如果PCI核不能满足最小数量的向量，将返回-ENOSPC。
176 众所周知，一些PCI芯片组或设备不支持MSI。PCI协议栈提供了三种禁用MSI的方法:
197 一些PCI桥接器不能在总线之间正确地路由MSI。在这种情况下，必须在桥接器后面的所
[all …]
H A Dpci-iov-howto.rst5 :Original: Documentation/PCI/pci-iov-howto.rst
18 PCI Express I/O 虚拟化指南
31 单根I/O虚拟化（SR-IOV）是一种PCI Express扩展功能，它使一个物理设备显示为多个
34 现为传统的PCIe设备。一旦开启，每个VF的PCI配置空间都可以通过自己的总线、设备和
35 功能编号（路由ID）来访问。而且每个VF也有PCI内存空间，用于映射其寄存器集。VF设
36 备驱动程序对寄存器集进行操作，这样它就可以发挥功能，并作为一个真正的现有PCI设备
50 PCI SRIOV核心支持确保启用/禁用操作是有效的，以减少同一检查在多个驱动程序中的重
57 在内核中，VF被视为热插拔的PCI设备，所以它们应该能够以与真正的PCI设备相同的方式
58 工作。VF需要的设备驱动与普通PCI设备的驱动相同。
/linux/Documentation/PCI/endpoint/
H A Dpci-endpoint.rst12 Linux has a comprehensive PCI subsystem to support PCI controllers that
24 PCI Endpoint Core
38 APIs for the PCI controller Driver
42 by the PCI controller driver.
55 * stop: ops to stop the PCI link
139 Add a PCI endpoint function to a PCI endpoint controller. A PCIe device
144 Remove the PCI endpoint function from PCI endpoint controller.
154 the PCI LINK.
178 The PCI Function driver can then register the PCI EPF driver by using
183 The PCI Function driver can unregister the PCI EPF driver by using
[all …]
H A Dpci-vntb-function.rst4 PCI vNTB Function
9 The difference between PCI NTB function and PCI vNTB function is
11 PCI NTB function need at two endpoint instances and connect HOST1
14 PCI vNTB function only use one host and one endpoint(EP), use NTB
15 connect EP and PCI host
30 | PCI NTB | | | |
32 | Driver | | | PCI Virtual |
38 | PCI BUS | <-----> | PCI EP BUS | | Virtual PCI |
41 PCI RC PCI EP
56 It is same as PCI NTB Function driver
[all …]
H A Dpci-test-function.rst4 PCI Test Function
9 Traditionally PCI RC has always been validated by using standard
10 PCI cards like ethernet PCI cards or USB PCI cards or SATA PCI cards.
12 to configure a PCI controller that can operate in EP mode to work as
15 The PCI endpoint test device is a virtual device (defined in software)
17 for other PCI endpoint devices (to use the EP framework).
19 The PCI endpoint test device has the following registers:
54 This register reflects the status of the PCI endpoint device.
/linux/Documentation/PCI/
H A Dpciebus-howto.rst22 A PCI Express Port is a logical PCI-PCI Bridge structure. There
24 Port. The Root Port originates a PCI Express link from a PCI Express
30 PCI Express link from the PCI Express Switch.
45 Express Port is a PCI-PCI Bridge device with multiple distinct
48 service drivers will compete for a single PCI-PCI Bridge device.
50 driver is loaded first, it claims a PCI-PCI Bridge Root Port. The
53 drivers load and run on a PCI-PCI Bridge device simultaneously
63 a PCI-PCI Bridge Port device.
68 - Allow one service driver to run on multiple PCI-PCI Bridge
71 - Manage and distribute resources of a PCI-PCI Bridge Port
[all …]
H A Dsysfs-pci.rst4 Accessing PCI device resources through sysfs
39 class PCI class (ascii, ro)
40 config PCI config space (binary, rw)
41 device PCI device (ascii, ro)
46 resource PCI resource host addresses (ascii, ro)
49 revision PCI revision (ascii, ro)
50 rom PCI ROM resource, if present (binary, ro)
51 subsystem_device PCI subsystem device (ascii, ro)
52 subsystem_vendor PCI subsystem vendor (ascii, ro)
53 vendor PCI vendor (ascii, ro)
[all …]
H A Dpci.rst4 How To Write Linux PCI Drivers
15 PCI device drivers.
29 Structure of PCI drivers
31 PCI drivers "discover" PCI devices in a system via pci_register_driver().
197 Enable the PCI device
226 If the PCI device can use the PCI Memory-Write-Invalidate transaction,
287 Many 64-bit "PCI" devices (before PCI-X) and some PCI-X devices are
334 causes the PCI support to program CPU vector data into the PCI device
361 PCI device shutdown
537 The alternative is the traditional PCI device driver that walks PCI
[all …]
/linux/drivers/pci/
H A DKconfig3 # PCI configuration
14 select PCI
21 menuconfig PCI config
22 bool "PCI support"
26 support for PCI-X and the foundations for PCI Express support.
29 if PCI
33 depends on PCI
84 Say Y here if you want the PCI core to detect if PCI resource
119 PCI devices from a PCI backend to support PCI driver domains.
200 PCI devices from a PCI backend to support PCI driver domains.
[all …]
/linux/Documentation/scsi/
H A Daic7xxx.rst88 AHA-2940D aic7880 PCI/32
89 aHA-2940 A/T aic7880 PCI/32
90 AHA-2940D A/T aic7880 PCI/32
97 AHA-4944UW aic7880 PCI/32
98 AHA-2930UW aic7880 PCI/32
101 AHA-2940UW/CN aic7880 PCI/32
102 AHA-2940UDual aic7895 PCI/32
103 AHA-2940UWDual aic7895 PCI/32
104 AHA-3940UWD aic7895 PCI/32
136 2. DEC21050 PCI-PCI bridge with multiple controller chips on secondary bus
[all …]
/linux/drivers/pci/hotplug/
H A DKconfig3 # PCI Hotplug support
7 bool "Support for PCI Hotplug"
8 depends on PCI && SYSFS
22 tristate "Compaq PCI Hotplug driver"
38 controller. This will allow the PCI Hotplug driver to store the PCI
44 tristate "IBM PCI Hotplug driver"
56 bool "ACPI PCI Hotplug driver"
122 bool "SHPC PCI Hotplug driver"
135 PCI Hotplug
143 tristate "RPA PCI Hotplug driver"
[all …]
/linux/drivers/comedi/
H A DKconfig431 PCI-20001, PCI-20006 and PCI-20341
585 ADlink - PCI-7224, PCI-7248, and PCI-7296
806 PCI-1730, PCI-1733, PCI-1734, PCI-1735U, PCI-1736UP, PCI-1739U,
807 PCI-1750, PCI-1751, PCI-1752, PCI-1753/E, PCI-1754, PCI-1756,
972 PCI-DAS1602/12, PCI-DAS1200, PCI-DAS1200jr, PCI-DAS1000, PCI-DAS1001
984 series: PCI-DDA08/12, PCI-DDA04/12, PCI-DDA02/12, PCI-DDA08/16,
1047 PCI-6518, PCI-6519, PCI-6520, PCI-6521, PXI-6521, PCI-6528, PXI-6528
1099 PCI-MIO-16E-4, PCI-6014, PCI-6040E, PXI-6040E, PCI-6030E, PCI-6031E,
1100 PCI-6032E, PCI-6033E, PCI-6071E, PCI-6023E, PCI-6024E, PCI-6025E,
1101 PXI-6025E, PCI-6034E, PCI-6035E, PCI-6052E, PCI-6110, PCI-6111,
[all …]
/linux/drivers/pci/pcie/
H A DKconfig3 # PCI Express Port Bus Configuration
6 bool "PCI Express Port Bus support"
17 bool "PCI Express Hotplug driver"
35 Port will be handled by PCI Express AER driver.
38 tristate "PCI Express error injection support"
53 bool "PCI Express CXL RAS support"
62 # PCI Express ECRC
65 bool "PCI Express ECRC settings control"
74 # PCI Express ASPM
77 bool "PCI Express ASPM control" if EXPERT
[all …]
/linux/drivers/isdn/hardware/mISDN/
H A DKconfig8 tristate "Support for HFC PCI cards"
10 depends on PCI
13 HFC PCI chip.
17 depends on (PCI || CPM1) && HAS_IOPORT
44 tristate "Support for AVM FRITZ!CARD PCI"
46 depends on PCI && HAS_IOPORT
49 Enable support for AVMs FRITZ!CARD PCI cards
54 depends on PCI && HAS_IOPORT
63 depends on PCI && HAS_IOPORT
72 depends on PCI && HAS_IOPORT
[all …]
/linux/drivers/net/can/sja1000/
H A DKconfig10 tristate "EMS CPC-PCI, CPC-PCIe and CPC-104P Card"
11 depends on PCI
26 depends on PCI
36 depends on PCI
42 tristate "PEAK PCAN-PCI/PCIe/miniPCI Cards"
43 depends on PCI
71 tristate "PLX90xx PCI-bridge based Cards"
72 depends on PCI
75 the PLX90xx PCI bridge.
78 - Adlink PCI-7841/cPCI-7841 SE card
[all …]
/linux/drivers/media/pci/mantis/
H A DKconfig3 tristate "Mantis/Hopper PCI bridge based devices"
4 depends on PCI && I2C && INPUT && RC_CORE && DVB_CORE
7 Support for PCI cards based on the Mantis and Hopper PCi bridge.
13 depends on MANTIS_CORE && DVB_CORE && PCI && I2C
25 Support for PCI cards based on the Mantis PCI bridge.
32 depends on MANTIS_CORE && DVB_CORE && PCI && I2C
36 Support for PCI cards based on the Hopper PCI bridge.
/linux/drivers/pci/endpoint/functions/
H A DKconfig3 # PCI Endpoint Functions
7 tristate "PCI Endpoint Test driver"
12 for PCI Endpoint.
17 tristate "PCI Endpoint NTB driver"
22 Bridge (NTB) driver for PCI Endpoint. NTB driver implements NTB
30 tristate "PCI Endpoint Virtual NTB driver"
37 between PCI Root Port and PCIe Endpoint.
42 tristate "PCI Endpoint driver for MHI bus"
45 Enable this configuration option to enable the PCI Endpoint
/linux/Documentation/virt/hyperv/
H A Dvpci.rst3 PCI pass-thru devices
5 In a Hyper-V guest VM, PCI pass-thru devices (also called
6 virtual PCI devices, or vPCI devices) are physical PCI devices
74 PCI Device Setup
101 them to the physical device PCI config space.
107 PCI subsystem code in Linux processes the BARs.
115 PCI Device Removal
125 a message, the Hyper-V virtual PCI driver in Linux
182 The Hyper-V virtual PCI driver implements the
286 PCI config space access in a CoCo VM
[all …]
/linux/drivers/net/wireless/realtek/rtw89/
H A DKconfig35 tristate "Realtek 8851BE PCI wireless network (Wi-Fi 6) adapter"
36 depends on PCI
46 tristate "Realtek 8852AE PCI wireless network (Wi-Fi 6) adapter"
47 depends on PCI
57 tristate "Realtek 8852BE PCI wireless network (Wi-Fi 6) adapter"
58 depends on PCI
68 tristate "Realtek 8852CE PCI wireless network (Wi-Fi 6E) adapter"
69 depends on PCI
79 tristate "Realtek 8922AE PCI wireless network (Wi-Fi 7) adapter"
80 depends on PCI
/linux/Documentation/arch/arm/
H A Dixp4xx.rst31 - PCI interface
67 3a. Limited inbound PCI window
74 3b. Limited outbound PCI window
76 IXP4xx provides two methods of accessing PCI memory space:
79 To access PCI via this space, we simply ioremap() the BAR
82 limits the system to just 64MB of PCI memory. This can be
86 configured to use indirect registers to access PCI This allows
88 The disadvantage of this is that every PCI access requires
91 mmap() PCI devices in this case due to the indirect nature
92 of the PCI window.
[all …]
/linux/sound/soc/amd/acp/
H A DKconfig11 depends on X86 && PCI
32 tristate "AMD ACP PCI Driver Support"
33 depends on X86 && PCI
37 This options enables generic PCI driver for ACP device.
46 depends on X86 && PCI
57 depends on X86 && PCI
65 depends on X86 && PCI
78 depends on X86 && PCI
91 depends on X86 && PCI && I2C
106 depends on X86 && PCI && I2C
[all …]

12345678910>>...37