~hc/RK356X_SDK_RELEASE.git

..	..	@@ -1,3 +1,4 @@
	1	+# SPDX-License-Identifier: GPL-2.0-only
1	2	config STM
2	3	tristate "System Trace Module devices"
3	4	select CONFIGFS_FS
..	..	@@ -10,6 +11,35 @@
10	11	Say Y here to enable System Trace Module device support.
11	12
12	13	if STM
	14	+
	15	+config STM_PROTO_BASIC
	16	+ tristate "Basic STM framing protocol driver"
	17	+ default CONFIG_STM
	18	+ help
	19	+ This is a simple framing protocol for sending data over STM
	20	+ devices. This was the protocol that the STM framework used
	21	+ exclusively until the MIPI SyS-T support was added. Use this
	22	+ driver for compatibility with your existing STM setup.
	23	+
	24	+ The receiving side only needs to be able to decode the MIPI
	25	+ STP protocol in order to extract the data.
	26	+
	27	+ If you want to be able to use the basic protocol or want the
	28	+ backwards compatibility for your existing setup, say Y.
	29	+
	30	+config STM_PROTO_SYS_T
	31	+ tristate "MIPI SyS-T STM framing protocol driver"
	32	+ default CONFIG_STM
	33	+ help
	34	+ This is an implementation of MIPI SyS-T protocol to be used
	35	+ over the STP transport. In addition to the data payload, it
	36	+ also carries additional metadata for time correlation, better
	37	+ means of trace source identification, etc.
	38	+
	39	+ The receiving side must be able to decode this protocol in
	40	+ addition to the MIPI STP, in order to extract the data.
	41	+
	42	+ If you don't know what this is, say N.
13	43
14	44	config STM_DUMMY
15	45	tristate "Dummy STM driver"
..	..	@@ -41,7 +71,7 @@
41	71
42	72	config STM_SOURCE_FTRACE
43	73	tristate "Copy the output from kernel Ftrace to STM engine"
44		- depends on FUNCTION_TRACER
	74	+ depends on TRACING
45	75	help
46	76	This option can be used to copy the output from kernel Ftrace
47	77	to STM engine. Enabling this option will introduce a slight