Messages in this thread | | | From | Randy Dunlap <> | Subject | Re: [RFC PATCH v3 02/16] cxl/acpi: Add an acpi_cxl module for the CXL interconnect | Date | Mon, 11 Jan 2021 23:08:26 -0800 |
| |
On 1/11/21 2:51 PM, Ben Widawsky wrote: > diff --git a/drivers/cxl/Kconfig b/drivers/cxl/Kconfig > new file mode 100644 > index 000000000000..68da926ba5b1 > --- /dev/null > +++ b/drivers/cxl/Kconfig > @@ -0,0 +1,36 @@ > +# SPDX-License-Identifier: GPL-2.0-only > +menuconfig CXL_BUS > + tristate "CXL (Compute Express Link) Devices Support" > + help > + CXL is a bus that is electrically compatible with PCI-E, but layers > + three protocols on that signalling (CXL.io, CXL.cache, and CXL.mem). > + The CXL.cache protocol allows devices to hold cachelines locally, the > + CXL.mem protocol allows devices to be fully coherent memory targets, > + the CXL.io protocol is equivalent to PCI-E. Say 'y' to enable support > + for the configuration and management of devices supporting these > + protocols. > + > +if CXL_BUS > + > +config CXL_BUS_PROVIDER > + tristate > + > +config CXL_ACPI > + tristate "CXL ACPI: Platform Support" > + depends on ACPI > + default CXL_BUS > + select CXL_BUS_PROVIDER > + help > + Say 'y/m' to enable a driver (named "cxl_acpi.ko" when built > + as a module) that will enable support for CXL.mem endpoint > + devices. In general, CXL Platform Support is a prerequisite > + for any CXL device driver that wants to claim ownership of a > + component register space. By default platform firmware assumes > + Linux is unaware of CXL capabilities and requires explicit > + opt-in. This platform component also mediates resources > + described by the CEDT (CXL Early Discovery Table). See > + Chapter 9.14.1 CXL Early Discovery Table (CEDT) in the CXL 2.0 > + specification. > + > + If unsure say 'm'
End above sentence with a '.', please.
> +endif
-- ~Randy
| |