| /linux-6.12.1/Documentation/translations/zh_CN/PCI/ |
| 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 …]
|
| D | pci.rst | 4 :Original: Documentation/PCI/pci.rst
17 如何写Linux PCI驱动
23 PCI的世界是巨大的，而且充满了（大多数是不愉快的）惊喜。由于每个CPU架构实现了不同
24 的芯片组，并且PCI设备有不同的要求（呃，“特性”），结果是Linux内核中的PCI支持并不
25 像人们希望的那样简单。这篇短文试图向所有潜在的驱动程序作者介绍PCI设备驱动程序的
37 请将有关Linux PCI API的问题/评论/补丁发送到“Linux PCI”
41 PCI驱动的结构体
43 PCI驱动通过pci_register_driver()在系统中“发现”PCI设备。实际上，它是反过来的。
44 当PCI通用代码发现一个新设备时，具有匹配“描述”的驱动程序将被通知。下面是这方面的细
47 pci_register_driver()将大部分探测设备的工作留给了PCI层，并支持设备的在线插入/移
[all …]
|
| 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 …]
|
| 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 …]
|
| D | msi-howto.rst | 5 :Original: Documentation/PCI/msi-howto.rst
35 MSI能力首次在PCI 2.2中规定，后来在PCI 3.0中得到增强，允许对每个中断进行单独屏蔽。
36 MSI-X功能也随着PCI 3.0被引入。它比MSI支持每个设备更多的中断，并允许独立配置中断。
46 基于针脚的PCI中断通常在几个设备之间共享。为了支持这一点，内核必须调用每个与中断相
50 之前，中断就已经到达了（这在PCI-PCI桥后面的设备中变得更有可能）。为了确保所有的数
51 据已经到达内存中，中断处理程序必须在引发中断的设备上读取一个寄存器。PCI事务排序规
55 PCI设备每个功能只能支持一个基于引脚的中断。通常情况下，驱动程序必须查询设备以找出
65 PCI设备被初始化为使用基于引脚的中断。设备驱动程序必须将设备设置为使用MSI或MSI-X。
79 大部分沉重的工作是在PCI层为驱动程序完成的。驱动程序只需要请求PCI层为这个设备设置
87 它为一个PCI设备分配最多至max_vecs的中断向量。它返回分配的向量数量或一个负的错误。
[all …]
|
| 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-6.12.1/Documentation/PCI/endpoint/ |
| D | pci-endpoint.rst | 5 This document is a guide to use the PCI Endpoint Framework in order to create
12 Linux has a comprehensive PCI subsystem to support PCI controllers that
13 operates in Root Complex mode. The subsystem has capability to scan PCI bus,
14 assign memory resources and IRQ resources, load PCI driver (based on
18 However the PCI controller IP integrated in some SoCs is capable of operating
19 either in Root Complex mode or Endpoint mode. PCI Endpoint Framework will
24 PCI Endpoint Core
27 The PCI Endpoint Core layer comprises 3 components: the Endpoint Controller
31 PCI Endpoint Controller(EPC) Library
38 APIs for the PCI controller Driver
[all …]
|
| 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 …]
|
| 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-6.12.1/Documentation/PCI/ |
| D | pciebus-howto.rst | 5 The PCI Express Port Bus Driver Guide HOWTO
14 This guide describes the basics of the PCI Express Port Bus driver
16 register/unregister with the PCI Express Port Bus Driver.
19 What is the PCI Express Port Bus Driver
22 A PCI Express Port is a logical PCI-PCI Bridge structure. There
23 are two types of PCI Express Port: the Root Port and the Switch
24 Port. The Root Port originates a PCI Express link from a PCI Express
25 Root Complex and the Switch Port connects PCI Express links to
26 internal logical PCI buses. The Switch Port, which has its secondary
30 PCI Express link from the PCI Express Switch.
[all …]
|
| 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 …]
|
| 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-6.12.1/drivers/pci/ |
| D | Kconfig | 3 # PCI configuration
6 # select this to offer the PCI prompt
10 # select this to unconditionally force on PCI support
14 select PCI
16 # select this to provide a generic PCI iomap,
17 # without PCI itself having to be defined
21 menuconfig PCI config
22 bool "PCI support"
25 This option enables support for the PCI local bus, including
26 support for PCI-X and the foundations for PCI Express support.
[all …]
|
| /linux-6.12.1/Documentation/scsi/ |
| 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 …]
|
| 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-6.12.1/drivers/pci/hotplug/ |
| D | Kconfig | 3 # PCI Hotplug support
7 bool "Support for PCI Hotplug"
8 depends on PCI && SYSFS
11 Say Y here if you have a motherboard with a PCI Hotplug controller.
12 This allows you to add and remove PCI cards while the machine is
22 tristate "Compaq PCI Hotplug driver"
25 Say Y here if you have a motherboard with a Compaq PCI Hotplug
37 Say Y here if you have a Compaq server that has a PCI Hotplug
38 controller. This will allow the PCI Hotplug driver to store the PCI
44 tristate "IBM PCI Hotplug driver"
[all …]
|
| /linux-6.12.1/drivers/comedi/ |
| 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-6.12.1/drivers/pci/pcie/ |
| D | Kconfig | 3 # PCI Express Port Bus Configuration
6 bool "PCI Express Port Bus support"
9 This enables PCI Express Port Bus support. Users can then enable
17 bool "PCI Express Hotplug driver"
29 bool "PCI Express Advanced Error Reporting support"
33 This enables PCI Express Root Port Advanced Error Reporting
35 Port will be handled by PCI Express AER driver.
38 tristate "PCI Express error injection support"
42 This enables PCI Express Root Port Advanced Error Reporting
53 bool "PCI Express CXL RAS support"
[all …]
|
| /linux-6.12.1/drivers/isdn/hardware/mISDN/ |
| 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-6.12.1/drivers/net/can/sja1000/ |
| 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-6.12.1/drivers/media/pci/mantis/ |
| 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-6.12.1/drivers/net/wireless/realtek/rtw89/ |
| D | Kconfig | 42 tristate "Realtek 8851BE PCI wireless network (Wi-Fi 6) adapter"
43 depends on PCI
53 tristate "Realtek 8852AE PCI wireless network (Wi-Fi 6) adapter"
54 depends on PCI
64 tristate "Realtek 8852BE PCI wireless network (Wi-Fi 6) adapter"
65 depends on PCI
76 tristate "Realtek 8852BE-VT PCI wireless network (Wi-Fi 6) adapter"
77 depends on PCI
88 tristate "Realtek 8852CE PCI wireless network (Wi-Fi 6E) adapter"
89 depends on PCI
[all …]
|
| /linux-6.12.1/drivers/pci/endpoint/functions/ |
| 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-6.12.1/Documentation/virt/hyperv/ |
| 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-6.12.1/Documentation/arch/arm/ |
| 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 …]
|