| /linux/Documentation/translations/zh_CN/PCI/ |
| H A D | pciebus-howto.rst | 5 :Original: Documentation/PCI/pciebus-howto.rst
18 PCI Express端口总线驱动指南
27 本指南介绍了PCI Express端口总线驱动程序的基本知识，并提供了如何使服务驱
28 动程序在PCI Express端口总线驱动程序中注册/取消注册的介绍。
31 什么是PCI Express端口总线驱动程序
34 一个PCI Express端口是一个逻辑的PCI-PCI桥结构。有两种类型的PCI Express端
35 口：根端口和交换端口。根端口从PCI Express根综合体发起一个PCI Express链接，
36 交换端口将PCI Express链接连接到内部逻辑PCI总线。交换机端口，其二级总线代表
38 路由总线桥接到代表来自PCI Express交换机的下游PCI Express链接的总线。
40 一个PCI Express端口可以提供多达四个不同的功能，在本文中被称为服务，这取决于
[all …]
|
| H A D | acpi-info.rst | 4 :Original: Documentation/PCI/acpi-info.rst
14 PCI主桥的ACPI注意事项
20 例如，没有标准的硬件机制来枚举PCI主桥，所以ACPI命名空间必须描述每个主桥、访问它
21 下面的PCI配置空间的方法、主桥转发到PCI的地址空间窗口（使用_CRS）以及传统的INTx
24 在主桥下面的PCI设备，通常不需要通过ACPI描述。操作系统可以通过标准的PCI枚举机制来
27 来描述这些连接，这种情况下ACPI可以描述PCI设备。
29 ACPI资源描述是通过ACPI命名空间中设备的_CRS对象完成的[2]。_CRS就像一个通用的PCI BAR：
42 PCI主桥是PNP0A03或PNP0A08设备。它们的_CRS应该描述它们所消耗的所有地址空间。这包括它
43 们转发到PCI总线上的所有窗口，以及不转发到PCI的主桥本身的寄存器。主桥的寄存器包括次要/下
69 型配置访问方法（ECAM）。主桥消耗ECAM内存地址空间并将内存访问转换为PCI配置访问。该规范
[all …]
|
| H A D | sysfs-pci.rst | 4 :Original: Documentation/PCI/sysfs-pci.rst
15 通过sysfs访问PCI设备资源
18 sysfs，通常挂载在/sys，在支持它的平台上提供对PCI资源的访问。例如，一个特定的总线可能看起
41 最上面的元素描述了PCI域和总线号码。在这种情况下，域号是0000，总线号是17（两个值都是十六进制）。
48 class PCI级别 (ascii, ro)
49 config PCI配置空间 (binary, rw)
50 device PCI设备 (ascii, ro)
55 resource PCI资源主机地址 (ascii, ro)
56 resource0..N PCI资源N，如果存在的话 (binary, mmap, rw\ [1]_)
57 resource0_wc..N_wc PCI WC映射资源N，如果可预取的话 (binary, mmap)
[all …]
|
| H A D | pci-iov-howto.rst | 5 :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/scsi/ |
| H A D | aic7xxx.rst | 27 aic7850 10 PCI/32 10MHz 8Bit 3
28 aic7855 10 PCI/32 10MHz 8Bit 3
29 aic7856 10 PCI/32 10MHz 8Bit 3
30 aic7859 10 PCI/32 20MHz 8Bit 3
31 aic7860 10 PCI/32 20MHz 8Bit 3
32 aic7870 10 PCI/32 10MHz 16Bit 16
33 aic7880 10 PCI/32 20MHz 16Bit 16
34 aic7890 20 PCI/32 40MHz 16Bit 16 3 4 5 6 7 8
35 aic7891 20 PCI/64 40MHz 16Bit 16 3 4 5 6 7 8
36 aic7892 20 PCI/64-66 80MHz 16Bit 16 3 4 5 6 7 8
[all …]
|
| H A D | advansys.rst | 9 (8-bit transfer) SCSI Host Adapters for the ISA, EISA, VL, and PCI
11 transfer) SCSI Host Adapters for the PCI bus.
27 - ABP902/3902 - Bus-Master PCI (16 CDB)
28 - ABP3905 - Bus-Master PCI (16 CDB)
29 - ABP915 - Bus-Master PCI (16 CDB)
30 - ABP920 - Bus-Master PCI (16 CDB)
31 - ABP3922 - Bus-Master PCI (16 CDB)
32 - ABP3925 - Bus-Master PCI (16 CDB)
33 - ABP930 - Bus-Master PCI (16 CDB)
34 - ABP930U - Bus-Master PCI Ultra (16 CDB)
[all …]
|
| /linux/Documentation/PCI/endpoint/ |
| H A D | pci-vntb-function.rst | 4 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 |
34 | | | PCI EP NTB |<------>| |
38 | PCI BUS | <-----> | PCI EP BUS | | Virtual PCI |
39 | | PCI | | | BUS |
[all …]
|
| H A D | pci-test-function.rst | 4 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/drivers/comedi/ |
| H A D | Kconfig | 427 tristate "Intelligent Instruments PCI-20001C carrier support"
430 Enable support for Intelligent Instruments PCI-20001C carrier
431 PCI-20001, PCI-20006 and PCI-20341
567 tristate "Comedi PCI drivers"
568 depends on PCI
570 Enable support for comedi PCI drivers.
578 tristate "Generic PCI based 8255 digital i/o board support"
581 Enable support for PCI based 8255 digital i/o boards. This driver
582 provides a PCI wrapper around the generic 8255 driver.
585 ADlink - PCI-7224, PCI-7248, and PCI-7296
[all …]
|
| /linux/drivers/isdn/hardware/mISDN/ |
| H A D | Kconfig | 8 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 D | Kconfig | 10 tristate "EMS CPC-PCI, CPC-PCIe and CPC-104P Card"
11 depends on PCI
13 This driver is for the one, two or four channel CPC-PCI,
26 depends on PCI
35 tristate "Kvaser PCIcanx and Kvaser PCIcan PCI Cards"
36 depends on PCI
42 tristate "PEAK PCAN-PCI/PCIe/miniPCI Cards"
43 depends on PCI
45 This driver is for the PCAN-PCI/PCIe/miniPCI cards
71 tristate "PLX90xx PCI-bridge based Cards"
[all …]
|
| /linux/drivers/media/pci/mantis/ |
| H A D | Kconfig | 3 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/Documentation/PCI/ |
| H A D | sysfs-pci.rst | 4 Accessing PCI device resources through sysfs
7 sysfs, usually mounted at /sys, provides access to PCI resources on platforms
30 The topmost element describes the PCI domain and bus number. In this case,
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)
47 resource0..N PCI resource N, if present (binary, mmap, rw\ [1]_)
48 resource0_wc..N_wc PCI WC map resource N, if prefetchable (binary, mmap)
49 revision PCI revision (ascii, ro)
[all …]
|
| H A D | pci.rst | 4 How To Write Linux PCI Drivers
10 The world of PCI is vast and full of (mostly unpleasant) surprises.
11 Since each CPU architecture implements different chip-sets and PCI devices
12 have different requirements (erm, "features"), the result is the PCI support
15 PCI device drivers.
25 Please send questions/comments/patches about Linux PCI API to the
26 "Linux PCI" <linux-pci@atrey.karlin.mff.cuni.cz> mailing list.
29 Structure of PCI drivers
31 PCI drivers "discover" PCI devices in a system via pci_register_driver().
32 Actually, it's the other way around. When the PCI generic code discovers
[all …]
|
| /linux/drivers/pci/endpoint/functions/ |
| H A D | Kconfig | 3 # 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 D | vpci.rst | 3 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
35 Hyper-V provides full PCI functionality for a vPCI device when
38 APIs for accessing PCI config space and for other integration
39 with Linux. But the initial detection of the PCI device and
40 its integration with the Linux PCI subsystem must use Hyper-V
47 vPCI device by fabricating a PCI bus topology and creating all
48 the normal PCI device data structures in Linux that would
49 exist if the PCI device were discovered via ACPI on a bare-
[all …]
|
| /linux/Documentation/arch/arm/ |
| H A D | ixp4xx.rst | 31 - PCI interface
67 3a. Limited inbound PCI window
69 The IXP4xx family allows for up to 256MB of memory but the PCI interface
70 can only expose 64MB of that memory to the PCI bus. This means that if
71 you are running with > 64MB, all PCI buffers outside of the accessible
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
[all …]
|
| /linux/Documentation/power/ |
| H A D | pci.rst | 2 PCI Power Management
7 An overview of concepts and the Linux kernel's interfaces related to PCI power
11 This document only covers the aspects of power management specific to PCI
18 1. Hardware and Platform Support for PCI Power Management
19 2. PCI Subsystem and Device Power Management
20 3. PCI Device Drivers and Power Management
24 1. Hardware and Platform Support for PCI Power Management
41 PCI devices may be put into low-power states in two ways, by using the device
42 capabilities introduced by the PCI Bus Power Management Interface Specification,
44 approach, that is referred to as the native PCI power management (native PCI PM)
[all …]
|
| /linux/Documentation/arch/powerpc/ |
| H A D | eeh-pci-error-recovery.rst | 2 PCI Bus EEH Error Recovery
12 The IBM POWER-based pSeries and iSeries computers include PCI bus
14 reporting a large variety of PCI bus error conditions. These features
16 hardware features allow PCI bus errors to be cleared and a PCI
20 This is in contrast to traditional PCI error handling, where the
21 PCI chip is wired directly to the CPU, and an error would cause
27 reliable and robust by protecting it from PCI errors, and giving
28 the OS the ability to "reboot"/recover individual PCI devices.
30 Future systems from other vendors, based on the PCI-E specification,
37 as PCI cards dying from heat, humidity, dust, vibration and bad
[all …]
|
| /linux/Documentation/devicetree/bindings/pci/ |
| H A D | ralink,rt3883-pci.txt | 1 * Mediatek/Ralink RT3883 PCI controller
29 interrupt controller and the PCI host bridge.
48 b) PCI host bridge:
63 - bus-range: PCI bus numbers covered
65 - ranges: specifies the ranges for the PCI memory and I/O regions
68 - interrupt-map: standard PCI properties to define the mapping of the
69 PCI interface to interrupt numbers.
71 The PCI host bridge node might have additional sub-nodes representing
72 the onboard PCI devices/PCI slots. Each such sub-node must have the
80 If a given sub-node represents a PCI bridge it must have following
[all …]
|
| /linux/sound/soc/amd/acp/ |
| H A D | Kconfig | 11 depends on X86 && PCI
36 tristate "AMD ACP PCI Driver Support"
37 depends on X86 && PCI
41 This options enables generic PCI driver for ACP device.
50 depends on X86 && PCI
61 depends on X86 && PCI
69 depends on X86 && PCI
82 depends on X86 && PCI
95 depends on X86 && PCI && I2C
110 depends on X86 && PCI && I2C
[all …]
|
| /linux/drivers/net/ethernet/dec/tulip/ |
| H A D | Kconfig | 8 depends on (PCI || EISA || CARDBUS)
10 This selects the "Tulip" family of EISA/PCI network cards.
15 tristate "Early DECchip Tulip (dc2104x) PCI support"
16 depends on PCI
21 21040 (Tulip series) chips. Some LinkSys PCI cards are
22 of this type. (If your card is NOT SMC EtherPower 10/100 PCI
43 tristate "DECchip Tulip (dc2114x) PCI support"
44 depends on PCI
49 21140 (Tulip series) chips. Some LinkSys PCI cards are
50 of this type. (If your card is NOT SMC EtherPower 10/100 PCI
[all …]
|
| /linux/drivers/ata/ |
| H A D | Kconfig | 111 depends on PCI
318 depends on PCI
325 depends on PCI
334 depends on PCI
367 depends on PCI
385 depends on PCI
394 depends on PCI
418 depends on PCI
459 depends on PCI || ARCH_DOVE || ARCH_MV78XX0 || \
465 Currently supports 88SX[56]0[48][01] PCI(-X) chips,
[all …]
|
| /linux/drivers/pci/endpoint/ |
| H A D | Kconfig | 3 # PCI Endpoint Support
6 menu "PCI Endpoint"
9 bool "PCI Endpoint Support"
12 Enable this configuration option to support configurable PCI
13 endpoint. This should be enabled if the platform has a PCI
23 bool "PCI Endpoint Configfs Support"
|
| /linux/arch/mips/bcm47xx/ |
| H A D | Kconfig | 12 select SSB_PCIHOST if PCI
13 select SSB_B43_PCI_BRIDGE if PCI
14 select SSB_DRIVER_PCICORE if PCI
15 select SSB_PCICORE_HOSTMODE if PCI
31 select BCMA_DRIVER_PCI if PCI
32 select BCMA_DRIVER_PCI_HOSTMODE if PCI
|