From: Souradeep Chowdhury <quic_schowdhu@quicinc.com> To: Andy Gross <agross@kernel.org>, Konrad Dybcio <konrad.dybcio@somainline.org>, Bjorn Andersson <andersson@kernel.org>, "Alex Elder" <elder@ieee.org> Cc: <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>, Sai Prakash Ranjan <quic_saipraka@quicinc.com>, Sibi Sankar <quic_sibis@quicinc.com>, "Rajendra Nayak" <quic_rjendra@quicinc.com>, <vkoul@kernel.org>, Souradeep Chowdhury <quic_schowdhu@quicinc.com> Subject: [PATCH V3 0/3] Add QAD, Cti-trigger and Bootconfig support for Data Capture and Compare(DCC) Date: Mon, 30 Jan 2023 10:43:54 +0530 [thread overview] Message-ID: <cover.1675054375.git.quic_schowdhu@quicinc.com> (raw) 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
WARNING: multiple messages have this Message-ID (diff)
From: Souradeep Chowdhury <quic_schowdhu@quicinc.com> To: Andy Gross <agross@kernel.org>, Konrad Dybcio <konrad.dybcio@somainline.org>, Bjorn Andersson <andersson@kernel.org>, "Alex Elder" <elder@ieee.org> Cc: <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>, Sai Prakash Ranjan <quic_saipraka@quicinc.com>, Sibi Sankar <quic_sibis@quicinc.com>, "Rajendra Nayak" <quic_rjendra@quicinc.com>, <vkoul@kernel.org>, Souradeep Chowdhury <quic_schowdhu@quicinc.com> Subject: [PATCH V3 0/3] Add QAD, Cti-trigger and Bootconfig support for Data Capture and Compare(DCC) Date: Mon, 30 Jan 2023 10:43:54 +0530 [thread overview] Message-ID: <cover.1675054375.git.quic_schowdhu@quicinc.com> (raw) 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 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-01-30 5:14 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-30 5:13 Souradeep Chowdhury [this message] 2023-01-30 5:13 ` [PATCH V3 0/3] Add QAD, Cti-trigger and Bootconfig support for Data Capture and Compare(DCC) Souradeep Chowdhury 2023-01-30 5:13 ` [PATCH V3 1/3] soc: qcom: dcc: Add bootconfig support for DCC Souradeep Chowdhury 2023-01-30 5:13 ` Souradeep Chowdhury 2023-01-30 5:13 ` [PATCH V3 2/3] soc: qcom: dcc: Add CTI-trigger " Souradeep Chowdhury 2023-01-30 5:13 ` Souradeep Chowdhury 2023-01-30 5:13 ` [PATCH V3 3/3] soc: qcom: dcc: Add QAD " Souradeep Chowdhury 2023-01-30 5:13 ` Souradeep Chowdhury
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=cover.1675054375.git.quic_schowdhu@quicinc.com \ --to=quic_schowdhu@quicinc.com \ --cc=agross@kernel.org \ --cc=andersson@kernel.org \ --cc=elder@ieee.org \ --cc=konrad.dybcio@somainline.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=quic_rjendra@quicinc.com \ --cc=quic_saipraka@quicinc.com \ --cc=quic_sibis@quicinc.com \ --cc=vkoul@kernel.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.