Home
last modified time | relevance | path

Searched full:pci (Results 1 – 25 of 528) sorted by relevance

12345678910>>...22

/Documentation/driver-api/pci/
Dpci.rst1 PCI Support Library
4 .. kernel-doc:: drivers/pci/pci.c
7 .. kernel-doc:: drivers/pci/iomap.c
10 .. kernel-doc:: drivers/pci/devres.c
13 .. kernel-doc:: drivers/pci/pci-driver.c
16 .. kernel-doc:: drivers/pci/remove.c
19 .. kernel-doc:: drivers/pci/search.c
22 .. kernel-doc:: drivers/pci/msi/msi.c
25 .. kernel-doc:: drivers/pci/bus.c
28 .. kernel-doc:: drivers/pci/access.c
[all …]
/Documentation/PCI/endpoint/
Dpci-endpoint.rst5 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 …]
Dindex.rst4 PCI Endpoint Framework
10 pci-endpoint
11 pci-endpoint-cfs
12 pci-test-function
13 pci-test-howto
14 pci-ntb-function
15 pci-ntb-howto
16 pci-vntb-function
17 pci-vntb-howto
19 function/binding/pci-test
[all …]
Dpci-ntb-howto.rst4 PCI Non-Transparent Bridge (NTB) Endpoint Function (EPF) User Guide
9 This document is a guide to help users use pci-epf-ntb function driver
13 Documentation/PCI/endpoint/pci-ntb-function.rst
40 # ls /sys/bus/pci-epf/drivers
49 Creating pci-epf-ntb Device
52 PCI endpoint function device can be created using the configfs. To create
53 pci-epf-ntb device, the following commands can be used::
59 The "mkdir func1" above creates the pci-epf-ntb function device that will
62 The PCI endpoint framework populates the directory with the following
66 baseclass_code deviceid msi_interrupts pci-epf-ntb.0
[all …]
Dpci-vntb-howto.rst4 PCI Non-Transparent Bridge (NTB) Endpoint Function (EPF) User Guide
9 This document is a guide to help users use pci-epf-vntb function driver
13 Documentation/PCI/endpoint/pci-vntb-function.rst
36 # ls /sys/bus/pci-epf/drivers
45 Creating pci-epf-vntb Device
48 PCI endpoint function device can be created using the configfs. To create
49 pci-epf-vntb device, the following commands can be used::
55 The "mkdir func1" above creates the pci-epf-ntb function device that will
58 The PCI endpoint framework populates the directory with the following
62 baseclass_code deviceid msi_interrupts pci-epf-ntb.0
[all …]
/Documentation/PCI/
Dpciebus-howto.rst5 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 …]
Dpci.rst4 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 …]
/Documentation/devicetree/bindings/pinctrl/
Dmarvell,orion-pinctrl.txt24 mpp0 0 pcie(rstout), pci(req2), gpio
25 mpp1 1 gpio, pci(gnt2)
26 mpp2 2 gpio, pci(req3), pci-1(pme)
27 mpp3 3 gpio, pci(gnt3)
28 mpp4 4 gpio, pci(req4)
29 mpp5 5 gpio, pci(gnt4)
30 mpp6 6 gpio, pci(req5), pci-1(clk)
31 mpp7 7 gpio, pci(gnt5), pci-1(clk)
49 mpp0 0 pcie(rstout), pci(req2), gpio
50 mpp1 1 gpio, pci(gnt2)
[all …]
/Documentation/devicetree/bindings/pci/
Dralink,rt3883-pci.txt1 * Mediatek/Ralink RT3883 PCI controller
7 - compatible: must be "ralink,rt3883-pci"
29 interrupt controller and the PCI host bridge.
48 b) PCI host bridge:
61 - device_type: must be "pci"
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
[all …]
Dfsl,pci.txt1 * Bus Enumeration by Freescale PCI-X Agent
3 Typically any Freescale PCI-X bridge hardware strapped into Agent mode
5 all mezzanines to be PCI-X Agents, but one per system may still
8 The property defined below will allow a PCI-X bridge to be used for bus
12 - fsl,pci-agent-force-enum : There is no value associated with this
17 /* PCI-X bridge known to be PrPMC Monarch */
18 pci0: pci@ef008000 {
19 fsl,pci-agent-force-enum;
23 compatible = "fsl,mpc8540-pcix", "fsl,mpc8540-pci";
24 device_type = "pci";
Drenesas,pci-rcar-gen2.yaml4 $id: http://devicetree.org/schemas/pci/renesas,pci-rcar-gen2.yaml#
7 title: Renesas AHB to PCI bridge
23 - renesas,pci-r8a7742 # RZ/G1H
24 - renesas,pci-r8a7743 # RZ/G1M
25 - renesas,pci-r8a7744 # RZ/G1N
26 - renesas,pci-r8a7745 # RZ/G1E
27 - renesas,pci-r8a7790 # R-Car H2
28 - renesas,pci-r8a7791 # R-Car M2-W
29 - renesas,pci-r8a7793 # R-Car M2-N
30 - renesas,pci-r8a7794 # R-Car E2
[all …]
Dloongson.yaml4 $id: http://devicetree.org/schemas/pci/loongson.yaml#
7 title: Loongson PCI Host Controller
13 PCI host controller found on Loongson PCHs and SoCs.
16 - $ref: /schemas/pci/pci-host-bridge.yaml#
21 - loongson,ls2k-pci
22 - loongson,ls7a-pci
23 - loongson,rs780e-pci
50 compatible = "loongson,rs780e-pci";
51 device_type = "pci";
Dintel,ixp4xx-pci.yaml4 $id: http://devicetree.org/schemas/pci/intel,ixp4xx-pci.yaml#
7 title: Intel IXP4xx PCI controller
12 description: PCI host controller found in the Intel IXP4xx SoC series.
15 - $ref: /schemas/pci/pci-host-bridge.yaml#
21 - intel,ixp42x-pci
22 - intel,ixp43x-pci
32 - description: Main PCI interrupt
33 - description: PCI DMA interrupt 1
34 - description: PCI DMA interrupt 2
43 description: The DMA range tells the PCI host which addresses
[all …]
/Documentation/ABI/testing/
Dsysfs-driver-ccp1 What: /sys/bus/pci/devices/<BDF>/fused_part
6 The /sys/bus/pci/devices/<BDF>/fused_part file reports
11 What: /sys/bus/pci/devices/<BDF>/debug_lock_on
16 The /sys/bus/pci/devices/<BDF>/debug_lock_on reports
22 What: /sys/bus/pci/devices/<BDF>/tsme_status
27 The /sys/bus/pci/devices/<BDF>/tsme_status file reports
33 What: /sys/bus/pci/devices/<BDF>/anti_rollback_status
38 The /sys/bus/pci/devices/<BDF>/anti_rollback_status file reports
44 What: /sys/bus/pci/devices/<BDF>/rpmc_production_enabled
49 The /sys/bus/pci/devices/<BDF>/rpmc_production_enabled file reports
[all …]
Dsysfs-bus-pci1 What: /sys/bus/pci/drivers/.../bind
4 Contact: linux-pci@vger.kernel.org
11 found in /sys/bus/pci/devices/. For example::
13 # echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/bind
17 What: /sys/bus/pci/drivers/.../unbind
20 Contact: linux-pci@vger.kernel.org
27 found in /sys/bus/pci/devices/. For example::
29 # echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/unbind
33 What: /sys/bus/pci/drivers/.../new_id
36 Contact: linux-pci@vger.kernel.org
[all …]
Dsysfs-driver-qat_rl1 What: /sys/bus/pci/devices/<BDF>/qat_rl/sla_op
36 What: /sys/bus/pci/devices/<BDF>/qat_rl/rp
64 # echo 4 > /sys/bus/pci/devices/<BDF>/qat_rl/id
65 # cat /sys/bus/pci/devices/<BDF>/qat_rl/rp
69 # echo 0x5 > /sys/bus/pci/devices/<BDF>/qat_rl/rp
73 What: /sys/bus/pci/devices/<BDF>/qat_rl/id
94 # echo "add" > /sys/bus/pci/devices/<BDF>/qat_rl/sla_op
95 # cat /sys/bus/pci/devices/<BDF>/qat_rl/id
99 # echo 7 > /sys/bus/pci/devices/<BDF>/qat_rl/id
100 # echo "get" > /sys/bus/pci/devices/<BDF>/qat_rl/sla_op
[all …]
Dsysfs-driver-qat1 What: /sys/bus/pci/devices/<BDF>/qat/state
19 What: /sys/bus/pci/devices/<BDF>/qat/cfg_services
46 is in the `down` state (see /sys/bus/pci/devices/<BDF>/qat/state)
52 # cat /sys/bus/pci/devices/<BDF>/qat/state
54 # cat /sys/bus/pci/devices/<BDF>/qat/cfg_services
56 # echo down > /sys/bus/pci/devices/<BDF>/qat/state
57 # echo dc > /sys/bus/pci/devices/<BDF>/qat/cfg_services
58 # echo up > /sys/bus/pci/devices/<BDF>/qat/state
59 # cat /sys/bus/pci/devices/<BDF>/qat/cfg_services
64 What: /sys/bus/pci/devices/<BDF>/qat/pm_idle_enabled
[all …]
Dsysfs-bus-pci-devices-aer_stats12 What: /sys/bus/pci/devices/<dev>/aer_dev_correctable
15 Contact: linux-pci@vger.kernel.org, rajatja@google.com
17 PCI device using ERR_COR. Note that since multiple errors may
33 What: /sys/bus/pci/devices/<dev>/aer_dev_fatal
36 Contact: linux-pci@vger.kernel.org, rajatja@google.com
38 PCI device using ERR_FATAL. Note that since multiple errors may
63 What: /sys/bus/pci/devices/<dev>/aer_dev_nonfatal
66 Contact: linux-pci@vger.kernel.org, rajatja@google.com
68 PCI device using ERR_NONFATAL. Note that since multiple errors
99 (internally) the ERR_* messages for errors seen by the internal rootport PCI
[all …]
/Documentation/scsi/
Daic7xxx.rst27 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 …]
/Documentation/virt/hyperv/
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
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
46 drivers/pci/controller/pci-hyperv.c handles a newly introduced
47 vPCI device by fabricating a PCI bus topology and creating all
48 the normal PCI device data structures in Linux that would
[all …]
/Documentation/networking/devlink/
Diosm.rst73 $ devlink dev flash pci/0000:02:00.0 file <PSI_RAM_File_name>
78 $ devlink dev param set pci/0000:02:00.0 name erase_full_flash value true cmode runtime
82 $ devlink dev flash pci/0000:02:00.0 file <EBL_File_name>
89 $ devlink dev flash pci/0000:02:00.0 file <Secure_bin_file_name>
93 $ devlink dev flash pci/0000:02:00.0 file <Load_map_file_name>
128 $ devlink region new pci/0000:02:00.0/report.json
130 $ devlink region dump pci/0000:02:00.0/report.json snapshot 0
132 $ devlink region del pci/0000:02:00.0/report.json snapshot 0
134 $ devlink region new pci/0000:02:00.0/coredump.fcd
136 $ devlink region dump pci/0000:02:00.0/coredump.fcd snapshot 1
[all …]
Ddevlink-port.rst32 - This indicates an eswitch port representing a port of PCI
35 - This indicates an eswitch port representing a port of PCI
38 - This indicates an eswitch port representing a port of PCI
41 - This indicates a virtual port for the PCI virtual function.
60 PCI controllers
62 In most cases a PCI device has only one controller. A controller consists of
67 A PCI device connected to multiple CPUs or multiple PCI root complexes or a
70 An eswitch is on the PCI device which supports ports of multiple controllers.
79 | pci rc |=== | pf0 |______/________/ | pf1 |___/_______/ |
98 | pci rc |==| ------- ----/---- ---/----- ------- ---/--- ---/--- |
[all …]
/Documentation/arch/powerpc/
Deeh-pci-error-recovery.rst2 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 …]
/Documentation/devicetree/bindings/virtio/
Dpci-iommu.yaml4 $id: http://devicetree.org/schemas/virtio/pci-iommu.yaml#
7 title: virtio-iommu device using the virtio-pci transport
13 When virtio-iommu uses the PCI transport, its programming interface is
14 discovered dynamically by the PCI probing infrastructure. However the
16 masters. Therefore, the PCI root complex that hosts the virtio-iommu
25 # according to the PCI Bus Binding specification. Since PCI provides
30 - const: virtio,pci-iommu
37 PCI address of the IOMMU. As defined in the PCI Bus Binding
41 zero. See Documentation/devicetree/bindings/pci/pci.txt
60 device_type = "pci";
[all …]
/Documentation/networking/device_drivers/ethernet/amd/
Dpds_vfio_pci.rst5 PCI VFIO driver for the AMD/Pensando(R) DSC adapter family
8 AMD/Pensando Linux VFIO PCI Device Driver
14 The ``pds-vfio-pci`` module is a PCI driver that supports Live Migration
20 The pds-vfio-pci device is enabled via multiple configuration steps and
26 example assumes the pds_core and pds-vfio-pci modules are already
42 echo 1 > /sys/bus/pci/drivers/pds_core/$PF_BDF/sriov_numvfs
44 # Allow the VF to be bound to the pds-vfio-pci driver
45 echo "pds-vfio-pci" > /sys/class/pci_bus/$PF_BUS/device/$VF_BDF/driver_override
47 # Bind the VF to the pds-vfio-pci driver
48 echo "$VF_BDF" > /sys/bus/pci/drivers/pds-vfio-pci/bind
[all …]

12345678910>>...22