~hc/RK356X_SDK_RELEASE.git

..	..	@@ -1,11 +1,13 @@
	1	+# SPDX-License-Identifier: GPL-2.0-only
1	2	config NVME_CORE
2	3	tristate
	4	+ select BLK_DEV_INTEGRITY_T10 if BLK_DEV_INTEGRITY
3	5
4	6	config BLK_DEV_NVME
5	7	tristate "NVM Express block device"
6	8	depends on PCI && BLOCK
7	9	select NVME_CORE
8		- ---help---
	10	+ help
9	11	The NVM Express driver is for solid state drives directly
10	12	connected to the PCI or PCI Express bus. If you know you
11	13	don't have one of these, it is safe to answer N.
..	..	@@ -16,11 +18,19 @@
16	18	config NVME_MULTIPATH
17	19	bool "NVMe multipath support"
18	20	depends on NVME_CORE
19		- ---help---
	21	+ help
20	22	This option enables support for multipath access to NVMe
21	23	subsystems. If this option is enabled only a single
22	24	/dev/nvmeXnY device will show up for each NVMe namespaces,
23	25	even if it is accessible through multiple controllers.
	26	+
	27	+config NVME_HWMON
	28	+ bool "NVMe hardware monitoring"
	29	+ depends on (NVME_CORE=y && HWMON=y) \|\| (NVME_CORE=m && HWMON)
	30	+ help
	31	+ This provides support for NVMe hardware monitoring. If enabled,
	32	+ a hardware monitoring device will be created for each NVMe drive
	33	+ in the system.
24	34
25	35	config NVME_FABRICS
26	36	tristate
..	..	@@ -57,3 +67,21 @@
57	67	from https://github.com/linux-nvme/nvme-cli.
58	68
59	69	If unsure, say N.
	70	+
	71	+config NVME_TCP
	72	+ tristate "NVM Express over Fabrics TCP host driver"
	73	+ depends on INET
	74	+ depends on BLOCK
	75	+ select NVME_CORE
	76	+ select NVME_FABRICS
	77	+ select CRYPTO
	78	+ select CRYPTO_CRC32C
	79	+ help
	80	+ This provides support for the NVMe over Fabrics protocol using
	81	+ the TCP transport. This allows you to use remote block devices
	82	+ exported using the NVMe protocol set.
	83	+
	84	+ To configure a NVMe over Fabrics controller use the nvme-cli tool
	85	+ from https://github.com/linux-nvme/nvme-cli.
	86	+
	87	+ If unsure, say N.