linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: arnd@arndb.de, gregkh@linuxfoundation.org, mpe@ellerman.id.au,
	andrew.donnellan@au1.ibm.com, alastair@au1.ibm.com
Subject: [PATCH v2 10/13] ocxl: Add Makefile and Kconfig
Date: Tue, 23 Jan 2018 12:31:45 +0100	[thread overview]
Message-ID: <20180123113148.6024-11-fbarrat@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180123113148.6024-1-fbarrat@linux.vnet.ibm.com>

OCXL_BASE triggers the platform support needed by the driver.

Signed-off-by: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
Signed-off-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
---
 drivers/misc/Kconfig       |  1 +
 drivers/misc/Makefile      |  1 +
 drivers/misc/ocxl/Kconfig  | 31 +++++++++++++++++++++++++++++++
 drivers/misc/ocxl/Makefile | 11 +++++++++++
 4 files changed, 44 insertions(+)
 create mode 100644 drivers/misc/ocxl/Kconfig
 create mode 100644 drivers/misc/ocxl/Makefile

diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index f1a5c2357b14..0534f338c84a 100644
--- a/drivers/misc/Kconfig
+++ b/drivers/misc/Kconfig
@@ -508,4 +508,5 @@ source "drivers/misc/mic/Kconfig"
 source "drivers/misc/genwqe/Kconfig"
 source "drivers/misc/echo/Kconfig"
 source "drivers/misc/cxl/Kconfig"
+source "drivers/misc/ocxl/Kconfig"
 endmenu
diff --git a/drivers/misc/Makefile b/drivers/misc/Makefile
index 5ca5f64df478..73326d54e246 100644
--- a/drivers/misc/Makefile
+++ b/drivers/misc/Makefile
@@ -55,6 +55,7 @@ obj-$(CONFIG_CXL_BASE)		+= cxl/
 obj-$(CONFIG_ASPEED_LPC_CTRL)	+= aspeed-lpc-ctrl.o
 obj-$(CONFIG_ASPEED_LPC_SNOOP)	+= aspeed-lpc-snoop.o
 obj-$(CONFIG_PCI_ENDPOINT_TEST)	+= pci_endpoint_test.o
+obj-$(CONFIG_OCXL)		+= ocxl/
 
 lkdtm-$(CONFIG_LKDTM)		+= lkdtm_core.o
 lkdtm-$(CONFIG_LKDTM)		+= lkdtm_bugs.o
diff --git a/drivers/misc/ocxl/Kconfig b/drivers/misc/ocxl/Kconfig
new file mode 100644
index 000000000000..4bbdb0d3c8ee
--- /dev/null
+++ b/drivers/misc/ocxl/Kconfig
@@ -0,0 +1,31 @@
+#
+# Open Coherent Accelerator (OCXL) compatible devices
+#
+
+config OCXL_BASE
+	bool
+	default n
+	select PPC_COPRO_BASE
+
+config OCXL
+	tristate "OpenCAPI coherent accelerator support"
+	depends on PPC_POWERNV && PCI && EEH
+	select OCXL_BASE
+	default m
+	help
+	  Select this option to enable the ocxl driver for Open
+	  Coherent Accelerator Processor Interface (OpenCAPI) devices.
+
+	  OpenCAPI allows FPGA and ASIC accelerators to be coherently
+	  attached to a CPU over an OpenCAPI link.
+
+	  The ocxl driver enables userspace programs to access these
+	  accelerators through devices in /dev/ocxl/.
+
+	  For more information, see http://opencapi.org.
+
+	  This is not to be confused with the support for IBM CAPI
+	  accelerators (CONFIG_CXL), which are PCI-based instead of a
+	  dedicated OpenCAPI link, and don't follow the same protocol.
+
+	  If unsure, say N.
diff --git a/drivers/misc/ocxl/Makefile b/drivers/misc/ocxl/Makefile
new file mode 100644
index 000000000000..5229dcda8297
--- /dev/null
+++ b/drivers/misc/ocxl/Makefile
@@ -0,0 +1,11 @@
+# SPDX-License-Identifier: GPL-2.0+
+ccflags-$(CONFIG_PPC_WERROR)	+= -Werror
+
+ocxl-y				+= main.o pci.o config.o file.o pasid.o
+ocxl-y				+= link.o context.o afu_irq.o sysfs.o trace.o
+obj-$(CONFIG_OCXL)		+= ocxl.o
+
+# For tracepoints to include our trace.h from tracepoint infrastructure:
+CFLAGS_trace.o := -I$(src)
+
+# ccflags-y += -DDEBUG
-- 
2.14.1

  parent reply	other threads:[~2018-01-23 11:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23 11:31 [PATCH v2 00/13] New driver to support OpenCAPI devices on POWER9 Frederic Barrat
2018-01-23 11:31 ` [PATCH v2 01/13] powerpc/powernv: Introduce new PHB type for opencapi links Frederic Barrat
2018-01-29  4:13   ` [v2, " Michael Ellerman
2018-01-23 11:31 ` [PATCH v2 02/13] powerpc/powernv: Set correct configuration space size for opencapi devices Frederic Barrat
2018-01-23 11:31 ` [PATCH v2 03/13] powerpc/powernv: Add opal calls for opencapi Frederic Barrat
2018-01-23 11:31 ` [PATCH v2 04/13] powerpc/powernv: Add platform-specific services " Frederic Barrat
2018-01-23 11:31 ` [PATCH v2 05/13] powerpc/powernv: Capture actag information for the device Frederic Barrat
2018-01-23 11:31 ` [PATCH v2 06/13] ocxl: Driver code for 'generic' opencapi devices Frederic Barrat
2018-01-23 11:31 ` [PATCH v2 07/13] ocxl: Add AFU interrupt support Frederic Barrat
2018-01-25 13:07   ` Greg KH
2018-01-25 23:51     ` Andrew Donnellan
2018-01-23 11:31 ` [PATCH v2 08/13] ocxl: Add a kernel API for other opencapi drivers Frederic Barrat
2018-01-23 11:31 ` [PATCH v2 09/13] ocxl: Add trace points Frederic Barrat
2018-01-23 11:31 ` Frederic Barrat [this message]
2018-01-23 11:31 ` [PATCH v2 11/13] cxl: Remove support for "Processing accelerators" class Frederic Barrat
2018-01-23 11:31 ` [PATCH v2 12/13] ocxl: Documentation Frederic Barrat
2018-01-25 13:17   ` Greg KH
2018-01-26 15:10     ` Frederic Barrat
2018-01-27  9:02       ` Michael Ellerman
2018-01-23 11:31 ` [PATCH v2 13/13] ocxl: add MAINTAINERS entry Frederic Barrat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180123113148.6024-11-fbarrat@linux.vnet.ibm.com \
    --to=fbarrat@linux.vnet.ibm.com \
    --cc=alastair@au1.ibm.com \
    --cc=andrew.donnellan@au1.ibm.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).