Home
last modified time | relevance | path

Searched +full:pcie +full:- +full:attached (Results 1 – 25 of 132) sorted by relevance

123456

/linux/tools/perf/pmu-events/arch/x86/skylakex/
H A Duncore-io.json13PCIe card of any size (x16,x8,x4) that is plugged directly into one of the PCIe slots. Part0 could…
29PCIe card of any size (x16,x8,x4) that is plugged directly into one of the PCIe slots. Part0 could…
44 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 0-3",
55 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 0",
66 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 1",
77 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 2",
88 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 3",
99 "BriefDescription": "PCIe Completion Buffer Inserts; Port 0",
111 "BriefDescription": "PCIe Completion Buffer Inserts; Port 1",
123 "BriefDescription": "PCIe Completion Buffer Inserts; Port 2",
[all …]
/linux/tools/perf/pmu-events/arch/x86/cascadelakex/
H A Duncore-io.json13PCIe card of any size (x16,x8,x4) that is plugged directly into one of the PCIe slots. Part0 could…
29PCIe card of any size (x16,x8,x4) that is plugged directly into one of the PCIe slots. Part0 could…
44 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 0-3",
55 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 0",
66 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 1",
77 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 2",
88 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 3",
99 "BriefDescription": "PCIe Completion Buffer Inserts; Port 0",
111 "BriefDescription": "PCIe Completion Buffer Inserts; Port 1",
123 "BriefDescription": "PCIe Completion Buffer Inserts; Port 2",
[all …]
/linux/drivers/bcma/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
16 # Support for Block-I/O. SELECT this from the driver that needs it.
26 bool "Support for BCMA on PCI-host bus"
46 BCMA bus may have many versions of PCIe core. This driver
48 1) PCIe core working in clientmode
49 2) PCIe Gen 2 clientmode core
51 In general PCIe (Gen 2) clientmode core is required on PCIe
54 This driver is also prerequisite for a hostmode PCIe core
67 Driver for the Broadcom MIPS core attached to Broadcom specific
78 bool "ChipCommon-attached serial flash support"
[all …]
/linux/Documentation/devicetree/bindings/pci/
H A Dbaikal,bt1-pcie.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/baikal,bt1-pcie.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Baikal-T1 PCIe Root Port Controller
10 - Serge Semin <fancer.lancer@gmail.com>
13 Embedded into Baikal-T1 SoC Root Complex controller with a single port
14 activated. It's based on the DWC RC PCIe v4.60a IP-core, which is configured
18 performed by software. There four in- and four outbound iATU regions
19 which can be used to emit all required TLP types on the PCIe bus.
[all …]
H A Dsnps,dw-pcie-ep.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie-ep.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Synopsys DesignWare PCIe endpoint interface
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
14 Synopsys DesignWare PCIe host controller endpoint
16 # Please create a separate DT-schema for your DWC PCIe Endpoint controller
17 # and make sure it's assigned with the vendor-specific compatible string.
[all …]
H A Dsnps,dw-pcie.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Synopsys DesignWare PCIe interface
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
14 Synopsys DesignWare PCIe host controller
16 # Please create a separate DT-schema for your DWC PCIe Root Port controller
17 # and make sure it's assigned with the vendor-specific compatible string.
[all …]
H A Dsnps,dw-pcie-common.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Synopsys DWC PCIe RP/EP controller
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
14 Generic Synopsys DesignWare PCIe Root Port and Endpoint controller
22 DWC PCIe CSR space is normally accessed over the dedicated Data Bus
23 Interface - DBI. In accordance with the reference manual the register
[all …]
/linux/drivers/pci/controller/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
11 tristate "Aardvark PCIe controller"
18 Add support for Aardvark 64bit PCIe Host Controller. This
23 tristate "Altera PCIe controller"
26 Say Y here if you want to enable PCIe controller support on Altera
30 tristate "Altera PCIe MSI feature"
35 Say Y here if you want PCIe MSI support for the Altera FPGA.
44 tristate "Apple PCIe controller"
51 Say Y here if you want to enable PCIe controller support on Apple
52 system-on-chips, like the Apple M1. This is required for the USB
[all …]
/linux/Documentation/PCI/
H A Dpcieaer-howto.rst1 .. SPDX-License-Identifier: GPL-2.0
8 :Authors: - T. Long Nguyen <tom.l.nguyen@intel.com>
9 - Yanmin Zhang <yanmin.zhang@intel.com>
17 ----------------
19 This guide describes the basics of the PCI Express (PCIe) Advanced Error
22 the PCIe AER driver.
25 What is the PCIe AER Driver?
26 ----------------------------
28 PCIe error signaling can occur on the PCIe link itself
29 or on behalf of transactions initiated on the link. PCIe
[all …]
/linux/Documentation/devicetree/bindings/net/wireless/
H A Dqcom,ath12k-wsi.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/net/wireless/qcom,ath12k-wsi.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Qualcomm Technologies ath12k wireless devices (PCIe) with WSI interface
11 - Jeff Johnson <jjohnson@kernel.org>
14 Qualcomm Technologies IEEE 802.11be PCIe devices with WSI interface.
23 multiple WSI-supported devices together, forming a WSI group.
28 +-------+ +-------+ +-------+
31 +----->| wsi |------->| wsi |------->| wsi |-----+
[all …]
/linux/Documentation/devicetree/bindings/phy/
H A Dphy-miphy365x.txt5 for SATA and PCIe.
8 - compatible : Should be "st,miphy365x-phy"
9 - st,syscfg : Phandle / integer array property. Phandle of sysconfig group
11 an entry for each port sub-node, specifying the control
14 Required nodes : A sub-node is required for each channel the controller
16 'reg' and 'reg-names' properties are used inside these
21 - #phy-cells : Should be 1 (See second example)
23 - PHY_TYPE_SATA
24 - PHY_TYPE_PCI
25 - reg : Address and length of register sets for each device in
[all …]
/linux/Documentation/devicetree/bindings/arm/bcm/
H A Dbrcm,hr2.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 A9 ARM CPUs, DDR2/DDR3 memory, PCIe GEN-2, USB 2.0 and USB 3.0, serial and NAND
13 flash and a PCIe attached integrated switching engine.
16 - Florian Fainelli <f.fainelli@gmail.com>
23 - enum:
24 - ubnt,unifi-switch8
25 - const: brcm,bcm53342
26 - const: brcm,hr2
/linux/drivers/net/can/sja1000/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
10 tristate "EMS CPC-PCI, CPC-PCIe and CPC-104P Card"
13 This driver is for the one, two or four channel CPC-PCI,
14 CPC-PCIe and CPC-104P cards from EMS Dr. Thomas Wuensche
15 (http://www.ems-wuensche.de).
18 tristate "EMS CPC-CARD Card"
21 This driver is for the one or two channel CPC-CARD cards from
22 EMS Dr. Thomas Wuensche (http://www.ems-wuensche.de).
25 tristate "Fintek F81601 PCIE to 2 CAN Controller"
28 This driver adds support for Fintek F81601 PCIE to 2 CAN
[all …]
/linux/Documentation/driver-api/
H A Dmen-chameleon-bus.rst31 ----------------------
38 -----------------------------------------
40 The current implementation is limited to PCI and PCIe based carrier devices
44 - Multi-resource MCB devices like the VME Controller or M-Module carrier.
45 - MCB devices that need another MCB device, like SRAM for a DMA Controller's
47 - A per-carrier IRQ domain for carrier devices that have one (or more) IRQs
48 per MCB device like PCIe based carriers with MSI or MSI-X support.
55 - The MEN Chameleon Bus itself,
56 - drivers for MCB Carrier Devices and
57 - the parser for the Chameleon table.
[all …]
H A Dxillybus.rst10 - Introduction
11 -- Background
12 -- Xillybus Overview
14 - Usage
15 -- User interface
16 -- Synchronization
17 -- Seekable pipes
19 - Internals
20 -- Source code organization
21 -- Pipe attributes
[all …]
/linux/Documentation/networking/
H A Drepresentors.rst1 .. SPDX-License-Identifier: GPL-2.0
9 used to control internal switching on SmartNICs. For the closely-related port
10 representors on physical (multi-port) switches, see
14 ----------
16 Since the mid-2010s, network cards have started offering more complex
17 virtualisation capabilities than the legacy SR-IOV approach (with its simple
18 MAC/VLAN-based switching model) can support. This led to a desire to offload
19 software-defined networks (such as OpenVSwitch) to these NICs to specify the
24 virtual switches and IOV devices. Just as each physical port of a Linux-
42 -----------
[all …]
/linux/Documentation/PCI/endpoint/
H A Dpci-ntb-howto.rst1 .. SPDX-License-Identifier: GPL-2.0
4 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
19 ---------------------------
27 2900000.pcie-ep 2910000.pcie-ep
32 2900000.pcie-ep 2910000.pcie-ep
36 -------------------------
40 # ls /sys/bus/pci-epf/drivers
49 Creating pci-epf-ntb Device
[all …]
/linux/drivers/scsi/mpt3sas/mpi/
H A Dmpi2_pci.h2 * Copyright 2000-2020 Broadcom Inc. All rights reserved.
6 * Title: MPI PCIe Attached Devices structures and definitions.
17 * ---------------
20 * -------- -------- ------------------------------------------------------
21 * 03-16-15 02.00.00 Initial version.
22 * 02-17-16 02.00.01 Removed AHCI support.
24 * 07-01-16 02.00.02 Added MPI26_NVME_FLAGS_FORCE_ADMIN_ERR_RESP to
26 * 07-22-18 02.00.03 Updted flags field for NVME Encapsulated req
27 * 12-17-18 02.00.04 Added MPI26_PCIE_DEVINFO_SCSI
29 * --------------------------------------------------------------------------
[all …]
/linux/Documentation/ABI/testing/
H A Dsysfs-bus-pci4 Contact: linux-pci@vger.kernel.org
15 (Note: kernels before 2.6.28 may require echo -n).
20 Contact: linux-pci@vger.kernel.org
31 (Note: kernels before 2.6.28 may require echo -n).
36 Contact: linux-pci@vger.kernel.org
55 Contact: Chris Wright <chrisw@sous-sol.org>
72 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
74 Writing a non-zero value to this attribute will
76 re-discover previously removed devices.
80 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
[all …]
/linux/arch/powerpc/boot/dts/fsl/
H A Dt104xd4rdb.dtsi36 reserved-memory {
37 #address-cells = <2>;
38 #size-cells = <2>;
41 bman_fbpr: bman-fbpr {
45 qman_fqd: qman-fqd {
49 qman_pfdr: qman-pfdr {
62 #address-cells = <1>;
63 #size-cells = <1>;
64 compatible = "cfi-flash";
66 bank-width = <2>;
[all …]
/linux/drivers/pci/controller/mobiveil/
H A Dpcie-mobiveil-host.c1 // SPDX-License-Identifier: GPL-2.0
3 * PCIe host controller driver for Mobiveil PCIe Host controller
6 * Copyright 2019-2020 NXP
15 #include <linux/irqchip/irq-msi-lib.h>
26 #include "pcie-mobiveil.h"
36 * attached to RC in mobiveil_pcie_valid_device()
38 if ((bus->primary == to_pci_host_bridge(bus->bridge)->busnr) && (PCI_SLOT(devfn) > 0)) in mobiveil_pcie_valid_device()
45 * mobiveil_pcie_map_bus - routine to get the configuration base of either
51 struct mobiveil_pcie *pcie = bus->sysdata; in mobiveil_pcie_map_bus() local
52 struct mobiveil_root_port *rp = &pcie->rp; in mobiveil_pcie_map_bus()
[all …]
/linux/Documentation/devicetree/bindings/bus/
H A Dbrcm,bus-axi.txt5 - compatible : brcm,bus-axi
7 - reg : iomem address range of chipcommon core
13 them manually through device tree. Use an interrupt-map to specify the
17 The top-level axi bus may contain children representing attached cores
25 compatible = "brcm,bus-axi";
28 #address-cells = <1>;
29 #size-cells = <1>;
30 #interrupt-cells = <1>;
31 interrupt-map-mask = <0x000fffff 0xffff>;
32 interrupt-map =
[all …]
/linux/drivers/pci/controller/cadence/
H A Dpcie-cadence.h1 /* SPDX-License-Identifier: GPL-2.0 */
3 // Cadence PCIe controller driver.
4 // Author: Cyrille Pitchen <cyrille.pitchen@free-electrons.com>
11 #include <linux/pci-epf.h>
117 (((aperture) - 2) << ((bar) * 8))
145 /* Region r Outbound AXI to PCIe Address Translation Register 0 */
150 (((nbits) - 1) & CDNS_PCIE_AT_OB_REGION_PCI_ADDR0_NBITS_MASK)
158 /* Region r Outbound AXI to PCIe Address Translation Register 1 */
162 /* Region r Outbound PCIe Descriptor Register 0 */
178 /* Region r Outbound PCIe Descriptor Register 1 */
[all …]
/linux/arch/arm64/boot/dts/freescale/
H A Dimx8mp-venice-gw71xx.dtsi1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
6 #include <dt-bindings/gpio/gpio.h>
7 #include <dt-bindings/leds/common.h>
8 #include <dt-bindings/phy/phy-imx8-pcie.h>
12 compatible = "gpio-usb-b-connector", "usb-b-connector";
13 pinctrl-names = "default";
14 pinctrl-0 = <&pinctrl_usbcon1>;
16 label = "Type-C";
17 id-gpios = <&gpio3 21 GPIO_ACTIVE_HIGH>;
21 remote-endpoint = <&usb3_dwc>;
[all …]
/linux/Documentation/devicetree/bindings/net/dsa/
H A Dmscc,ocelot.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR MIT)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Vladimir Oltean <vladimir.oltean@nxp.com>
11 - Claudiu Manoil <claudiu.manoil@nxp.com>
12 - Alexandre Belloni <alexandre.belloni@bootlin.com>
13 - UNGLinuxDriver@microchip.com
16 There are multiple switches which are either part of the Ocelot-1 family, or
19 SPI or PCIe. The present DSA binding shall be used when the host controlling
21 (which is attached to an Ethernet port of the host), rather than through
[all …]

123456