Home
last modified time | relevance | path

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

12345678

/linux-6.14.4/tools/perf/pmu-events/arch/x86/skylakex/
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-6.14.4/tools/perf/pmu-events/arch/x86/cascadelakex/
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-6.14.4/drivers/gpu/drm/amd/include/
Dkgd_pp_interface.h167 PP_SMC_POWER_PROFILE_UNKNOWN = -1,
237 * APU power is managed to system-level requirements through the PPT
247 * enum pp_power_limit_level - Used to query the power limits
255 PP_PWR_LIMIT_MIN = -1,
262 * enum pp_power_type - Used to specify the type of the requested power
275 XGMI_PLPD_NONE = -1,
283 PP_PM_POLICY_NONE = -1,
510 /* Driver attached timestamp (in ns) */
579 /* Driver attached timestamp (in ns) */
638 /* Driver attached timestamp (in ns) */
[all …]
/linux-6.14.4/drivers/bcma/
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-6.14.4/Documentation/PCI/
Dpcieaer-howto.rst1 .. SPDX-License-Identifier: GPL-2.0
8 :Authors: - T. Long Nguyen <[email protected]>
9 - Yanmin Zhang <[email protected]>
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-6.14.4/Documentation/devicetree/bindings/pci/
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 <[email protected]>
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 …]
Dstarfive,jh7110-pcie.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/starfive,jh7110-pcie.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: StarFive JH7110 PCIe host controller
10 - Kevin Xie <[email protected]>
13 - $ref: plda,xpressrich3-axi-common.yaml#
17 const: starfive,jh7110-pcie
23 reg-names:
28 - description: NOC bus clock
[all …]
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 <[email protected]>
11 - Gustavo Pimentel <[email protected]>
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 …]
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 <[email protected]>
11 - Gustavo Pimentel <[email protected]>
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 …]
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 <[email protected]>
11 - Gustavo Pimentel <[email protected]>
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-6.14.4/drivers/pci/controller/
DKconfig1 # 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 …]
/linux-6.14.4/Documentation/devicetree/bindings/net/wireless/
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 <[email protected]>
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-6.14.4/Documentation/devicetree/bindings/phy/
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-6.14.4/Documentation/devicetree/bindings/arm/bcm/
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 <[email protected]>
23 - enum:
24 - ubnt,unifi-switch8
25 - const: brcm,bcm53342
26 - const: brcm,hr2
/linux-6.14.4/drivers/net/can/sja1000/
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-6.14.4/Documentation/devicetree/bindings/net/bluetooth/
Dbrcm,bcm4377-bluetooth.yaml1 # 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 <[email protected]>
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 …]
/linux-6.14.4/Documentation/driver-api/
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 …]
/linux-6.14.4/Documentation/networking/
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-6.14.4/drivers/scsi/mpt3sas/
Dmpt3sas_base.h6 * Copyright (C) 2012-2014 LSI Corporation
7 * Copyright (C) 2013-2014 Avago Technologies
8 * (mailto: MPT-[email protected])
23 * LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT,
42 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
78 #define MPT3SAS_AUTHOR "Avago Technologies <MPT-[email protected]>"
100 #define MPT3SAS_TIMESYNC_MASK (0x7F) /* 0 - 6 bits */
183 pr_err("%s: " fmt, (ioc)->name, ##__VA_ARGS__)
185 pr_notice("%s: " fmt, (ioc)->name, ##__VA_ARGS__)
187 pr_warn("%s: " fmt, (ioc)->name, ##__VA_ARGS__)
[all …]
/linux-6.14.4/Documentation/PCI/endpoint/
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-6.14.4/drivers/scsi/mpt3sas/mpi/
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-6.14.4/drivers/usb/dwc3/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
22 Select this if you have ULPI type PHY attached to your DWC3
78 tristate "PCIe-based Platforms"
82 If you're using the DesignWare Core IP with a PCIe (but not HAPS
86 tristate "Synopsys PCIe-based HAPS Platforms"
90 If you're using the DesignWare Core IP with a Synopsys PCIe HAPS
189 or dual-role mode.
/linux-6.14.4/arch/arm64/boot/dts/freescale/
Dimx8mp-venice-gw82xx.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>
17 led-controller {
18 compatible = "gpio-leds";
19 pinctrl-names = "default";
20 pinctrl-0 = <&pinctrl_gpio_leds>;
22 led-0 {
26 default-state = "on";
[all …]
/linux-6.14.4/Documentation/ABI/testing/
Dsysfs-bus-pci4 Contact: linux-[email protected]
15 (Note: kernels before 2.6.28 may require echo -n).
20 Contact: linux-[email protected]
31 (Note: kernels before 2.6.28 may require echo -n).
36 Contact: linux-[email protected]
55 Contact: Chris Wright <chrisw@sous-sol.org>
72 Contact: Linux PCI developers <linux-[email protected]>
74 Writing a non-zero value to this attribute will
76 re-discover previously removed devices.
80 Contact: Linux PCI developers <linux-[email protected]>
[all …]
/linux-6.14.4/arch/powerpc/boot/dts/fsl/
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 …]

12345678