Searched +full:pcie +full:- +full:attached (Results 1 – 25 of 309) sorted by relevance
12345678910>>...13
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| D | uncore-io.json | 12 …PCIe card of any size (x16,x8,x4) that is plugged directly into one of the PCIe slots. Part0 could…
27 …PCIe card of any size (x16,x8,x4) that is plugged directly into one of the PCIe slots. Part0 could…
41 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 0-3",
51 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 0",
61 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 1",
71 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 2",
81 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 3",
91 "BriefDescription": "PCIe Completion Buffer Inserts; Port 0",
101 "BriefDescription": "PCIe Completion Buffer Inserts; Port 1",
111 "BriefDescription": "PCIe Completion Buffer Inserts; Port 2",
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/skylakex/ |
| D | uncore-io.json | 12 …PCIe card of any size (x16,x8,x4) that is plugged directly into one of the PCIe slots. Part0 could…
27 …PCIe card of any size (x16,x8,x4) that is plugged directly into one of the PCIe slots. Part0 could…
41 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 0-3",
51 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 0",
61 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 1",
71 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 2",
81 "BriefDescription": "PCIe Completion Buffer Inserts of completions with data: Part 3",
91 "BriefDescription": "PCIe Completion Buffer Inserts; Port 0",
101 "BriefDescription": "PCIe Completion Buffer Inserts; Port 1",
111 "BriefDescription": "PCIe Completion Buffer Inserts; Port 2",
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| D | uncore-other.json | 10 …"BriefDescription": "LLC misses - Uncacheable reads (from cpu) . Derived from unc_cha_tor_inserts.…
121 "ScaleUnit": "7.11E-06Bytes",
272 "BriefDescription": "Multi-socket cacheline Directory state lookups; Snoop Not Needed",
277 …"PublicDescription": "Counts transactions that looked into the multi-socket cacheline Directory st…
282 "BriefDescription": "Multi-socket cacheline Directory state lookups; Snoop Needed",
287 …"PublicDescription": "Counts transactions that looked into the multi-socket cacheline Directory s…
292 …"BriefDescription": "Multi-socket cacheline Directory state updates; Directory Updated memory writ…
297 …"PublicDescription": "Counts only multi-socket cacheline Directory state updates memory writes iss…
302 …"BriefDescription": "Multi-socket cacheline Directory state updates; Directory Updated memory writ…
307 …"PublicDescription": "Counts only multi-socket cacheline Directory state updates due to memory wri…
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/skylakex/ |
| D | uncore-other.json | 10 …"BriefDescription": "LLC misses - Uncacheable reads (from cpu) . Derived from unc_cha_tor_inserts.…
121 "ScaleUnit": "7.11E-06Bytes",
272 "BriefDescription": "Multi-socket cacheline Directory state lookups; Snoop Not Needed",
277 …"PublicDescription": "Counts transactions that looked into the multi-socket cacheline Directory st…
282 "BriefDescription": "Multi-socket cacheline Directory state lookups; Snoop Needed",
287 …"PublicDescription": "Counts transactions that looked into the multi-socket cacheline Directory s…
292 …"BriefDescription": "Multi-socket cacheline Directory state updates; Directory Updated memory writ…
297 …"PublicDescription": "Counts only multi-socket cacheline Directory state updates memory writes iss…
302 …"BriefDescription": "Multi-socket cacheline Directory state updates; Directory Updated memory writ…
307 …"PublicDescription": "Counts only multi-socket cacheline Directory state updates due to memory wri…
[all …]
|
| /kernel/linux/linux-5.10/drivers/bcma/ |
| D | Kconfig | 1 # 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 …]
|
| /kernel/linux/linux-6.6/drivers/bcma/ |
| D | Kconfig | 1 # 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 …]
|
| /kernel/linux/linux-6.6/Documentation/PCI/ |
| D | pcieaer-howto.rst | 1 .. 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 …]
|
| /kernel/linux/linux-5.10/drivers/pci/controller/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
7 bool "Marvell EBU PCIe controller"
15 tristate "Aardvark PCIe controller"
21 Add support for Aardvark 64bit PCIe Host Controller. This
26 bool "NWL PCIe Core"
31 NWL PCIe controller. The controller can act as Root Port
41 bool "NVIDIA Tegra PCIe controller"
46 Say Y here if you want support for the PCIe host controller found
50 bool "Renesas R-Car Gen2 Internal PCI controller"
54 Say Y here if you want internal PCI support on R-Car Gen2 SoC.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pci/ |
| D | baikal,bt1-pcie.yaml | 1 # 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 …]
|
| D | snps,dw-pcie-ep.yaml | 1 # 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 …]
|
| D | snps,dw-pcie.yaml | 1 # 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 …]
|
| D | snps,dw-pcie-common.yaml | 1 # 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 …]
|
| /kernel/linux/linux-6.6/drivers/pci/controller/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
7 tristate "Aardvark PCIe controller"
13 Add support for Aardvark 64bit PCIe Host Controller. This
18 tristate "Altera PCIe controller"
21 Say Y here if you want to enable PCIe controller support on Altera
25 tristate "Altera PCIe MSI feature"
29 Say Y here if you want PCIe MSI support for the Altera FPGA.
38 tristate "Apple PCIe controller"
44 Say Y here if you want to enable PCIe controller support on Apple
45 system-on-chips, like the Apple M1. This is required for the USB
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/phy/ |
| D | phy-miphy365x.txt | 5 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/phy/ |
| D | phy-miphy365x.txt | 5 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 …]
|
| /kernel/linux/linux-5.10/Documentation/PCI/ |
| D | pcieaer-howto.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 :Authors: - T. Long Nguyen <tom.l.nguyen@intel.com>
9 - Yanmin Zhang <yanmin.zhang@intel.com>
17 ----------------
26 -----------------------------------
41 - Gathers the comprehensive error information if errors occurred.
42 - Reports error to the users.
43 - Performs error recovery actions.
45 AER driver only attaches root ports which support PCI-Express AER
53 -------------------------------------------------------------
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,hr2.yaml | 1 # 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
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,hr2.yaml | 1 # 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
|
| /kernel/linux/linux-5.10/drivers/net/can/sja1000/ |
| D | Kconfig | 1 # 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 …]
|
| /kernel/linux/linux-6.6/drivers/net/can/sja1000/ |
| D | Kconfig | 1 # 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 …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/bluetooth/ |
| D | brcm,bcm4377-bluetooth.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/bluetooth/brcm,bcm4377-bluetooth.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Broadcom BCM4377 family PCIe Bluetooth Chips
10 - Sven Peter <sven@svenpeter.dev>
13 This binding describes Broadcom BCM4377 family PCIe-attached bluetooth chips
14 usually found in Apple machines. The Wi-Fi part of the chip is described in
15 bindings/net/wireless/brcm,bcm4329-fmac.yaml.
18 - $ref: bluetooth-controller.yaml#
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/ |
| D | men-chameleon-bus.rst | 31 ----------------------
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 …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | men-chameleon-bus.rst | 30 ----------------------
37 -----------------------------------------
39 The current implementation is limited to PCI and PCIe based carrier devices
43 - Multi-resource MCB devices like the VME Controller or M-Module carrier.
44 - MCB devices that need another MCB device, like SRAM for a DMA Controller's
46 - A per-carrier IRQ domain for carrier devices that have one (or more) IRQs
47 per MCB device like PCIe based carriers with MSI or MSI-X support.
54 - The MEN Chameleon Bus itself,
55 - drivers for MCB Carrier Devices and
56 - the parser for the Chameleon table.
[all …]
|
| /kernel/linux/linux-5.10/drivers/usb/dwc3/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
21 Select this if you have ULPI type PHY attached to your DWC3
77 tristate "PCIe-based Platforms"
81 If you're using the DesignWare Core IP with a PCIe (but not HAPS
85 tristate "Synopsys PCIe-based HAPS Platforms"
89 If you're using the DesignWare Core IP with a Synopsys PCIe HAPS
|
| /kernel/linux/linux-6.6/Documentation/networking/ |
| D | representors.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 used to control internal switching on SmartNICs. For the closely-related port
9 representors on physical (multi-port) switches, see
13 ----------
15 Since the mid-2010s, network cards have started offering more complex
16 virtualisation capabilities than the legacy SR-IOV approach (with its simple
17 MAC/VLAN-based switching model) can support. This led to a desire to offload
18 software-defined networks (such as OpenVSwitch) to these NICs to specify the
23 virtual switches and IOV devices. Just as each physical port of a Linux-
41 -----------
[all …]
|
12345678910>>...13