[V3,0/3] Add QAD, Cti-trigger and Bootconfig support for Data Capture and Compare(DCC)

Message

Souradeep Chowdhury Jan. 30, 2023, 5:13 a.m. UTC

This patch adds the Bootconfig, QAD and CTI-Trigger support for DCC.

1.Bootconfig

Bootconfig parser has been added to DCC driver so that the register addresses
can be configured during boot-time. This is used to debug crashes that can happen
during boot-time. The expected format of a bootconfig is as follows:-

dcc_config {
	link_list_<The list number to configure> {
		id = <The list number to configure>
		items =  <Address as same format as dcc separated by '_'>,
	}
}

Example:

dcc_config {
	link_list_6 {
		id = 6
		items = R_0x1781005c_1_apb,
			R_0x1782005c_1_apb
	}
	link_list_5 {
		id = 5
		items = R_0x1784005c_1_apb
	}
}

2.QAD

QAD can be enabled as a part of debugfs file under each individual list folder.
QAD is used to specify the access control for DCC configurations, on enabling
it the access control to dcc configuration space is restricted.  On setting the
QAD value, the list gets locked out for a particular component and cannot be
used by the rest.

3.CTI-trigger

CTI trigger is used to enable the Cross trigger interface for DCC. On enabling
CTI trigger the dcc software trigger can be done by writing to CTI trig-out.
Also the hwtrigger debugfs file is created which needs to be disabled for enabling
CTI-trigger. Hwtrigger needs to be disabled for components to be able to write to
CTI-trig-out.

Changes in V3

*Fixed the module build error in V2 of the patch

Souradeep Chowdhury (3):
  soc: qcom: dcc: Add bootconfig support for DCC
  soc: qcom: dcc: Add CTI-trigger support for DCC
  soc: qcom: dcc: Add QAD support for DCC

 Documentation/ABI/testing/debugfs-driver-dcc |  24 +++
 drivers/soc/qcom/Kconfig                     |   3 +-
 drivers/soc/qcom/dcc.c                       | 290 ++++++++++++++++++++++++++-
 3 files changed, 309 insertions(+), 8 deletions(-)

--
2.7.4