Commit | Line | Data |
---|---|---|
4cdadfd5 DW |
1 | # SPDX-License-Identifier: GPL-2.0-only |
2 | menuconfig CXL_BUS | |
3 | tristate "CXL (Compute Express Link) Devices Support" | |
4 | depends on PCI | |
5 | help | |
6 | CXL is a bus that is electrically compatible with PCI Express, but | |
7 | layers three protocols on that signalling (CXL.io, CXL.cache, and | |
8 | CXL.mem). The CXL.cache protocol allows devices to hold cachelines | |
9 | locally, the CXL.mem protocol allows devices to be fully coherent | |
10 | memory targets, the CXL.io protocol is equivalent to PCI Express. | |
11 | Say 'y' to enable support for the configuration and management of | |
12 | devices supporting these protocols. | |
13 | ||
14 | if CXL_BUS | |
15 | ||
16 | config CXL_MEM | |
17 | tristate "CXL.mem: Memory Devices" | |
18 | help | |
19 | The CXL.mem protocol allows a device to act as a provider of | |
20 | "System RAM" and/or "Persistent Memory" that is fully coherent | |
21 | as if the memory was attached to the typical CPU memory | |
22 | controller. | |
23 | ||
21e9f767 BW |
24 | Say 'y/m' to enable a driver that will attach to CXL.mem devices for |
25 | configuration and management primarily via the mailbox interface. See | |
26 | Chapter 2.3 Type 3 CXL Device in the CXL 2.0 specification for more | |
27 | details. | |
4cdadfd5 DW |
28 | |
29 | If unsure say 'm'. | |
13237183 BW |
30 | |
31 | config CXL_MEM_RAW_COMMANDS | |
32 | bool "RAW Command Interface for Memory Devices" | |
33 | depends on CXL_MEM | |
34 | help | |
35 | Enable CXL RAW command interface. | |
36 | ||
37 | The CXL driver ioctl interface may assign a kernel ioctl command | |
38 | number for each specification defined opcode. At any given point in | |
39 | time the number of opcodes that the specification defines and a device | |
40 | may implement may exceed the kernel's set of associated ioctl function | |
41 | numbers. The mismatch is either by omission, specification is too new, | |
42 | or by design. When prototyping new hardware, or developing / debugging | |
43 | the driver it is useful to be able to submit any possible command to | |
44 | the hardware, even commands that may crash the kernel due to their | |
45 | potential impact to memory currently in use by the kernel. | |
46 | ||
47 | If developing CXL hardware or the driver say Y, otherwise say N. | |
4cdadfd5 | 48 | endif |