From: James Clark <james.clark@arm.com>
To: coresight@lists.linaro.org, catalin.marinas@arm.com,
linux-arm-kernel@lists.infradead.org
Cc: suzuki.poulose@arm.com, mathieu.poirier@linaro.org,
mike.leach@linaro.org, leo.yan@linaro.org, broonie@kernel.org,
linux-kernel@vger.kernel.org, James Clark <james.clark@arm.com>,
Will Deacon <will@kernel.org>
Subject: [PATCH 1/1] arm64: defconfig: Add Coresight as module
Date: Wed, 21 Sep 2022 15:05:35 +0100 [thread overview]
Message-ID: <20220921140535.152627-2-james.clark@arm.com> (raw)
In-Reply-To: <20220921140535.152627-1-james.clark@arm.com>
Add Coresight to defconfig so that build errors are caught.
CONFIG_CORESIGHT_SOURCE_ETM4X is excluded because it depends on
CONFIG_PID_IN_CONTEXTIDR which has a performance cost.
Signed-off-by: James Clark <james.clark@arm.com>
---
arch/arm64/configs/defconfig | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index ef3467092ded..c183914ab999 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -1340,4 +1340,13 @@ CONFIG_DEBUG_FS=y
# CONFIG_SCHED_DEBUG is not set
# CONFIG_DEBUG_PREEMPT is not set
# CONFIG_FTRACE is not set
+CONFIG_CORESIGHT=m
+CONFIG_CORESIGHT_LINK_AND_SINK_TMC=m
+CONFIG_CORESIGHT_CATU=m
+CONFIG_CORESIGHT_SINK_TPIU=m
+CONFIG_CORESIGHT_SINK_ETBV10=m
+CONFIG_CORESIGHT_STM=m
+CONFIG_CORESIGHT_CPU_DEBUG=m
+CONFIG_CORESIGHT_CTI=m
+CONFIG_CORESIGHT_CTI_INTEGRATION_REGS=y
CONFIG_MEMTEST=y
--
2.28.0
next prev parent reply other threads:[~2022-09-21 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 14:05 [PATCH 0/1] " James Clark
2022-09-21 14:05 ` James Clark [this message]
2022-09-21 15:26 ` [PATCH 1/1] " Mark Brown
2022-09-21 16:46 ` Mathieu Poirier
2022-09-22 9:04 ` James Clark
2022-09-22 9:26 ` Suzuki K Poulose
2022-09-21 15:08 ` [PATCH 0/1] " Catalin Marinas
2022-09-22 9:34 ` James Clark
2022-09-22 10:52 ` Catalin Marinas
2022-09-22 13:06 ` James Clark
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=20220921140535.152627-2-james.clark@arm.com \
--to=james.clark@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=coresight@lists.linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.com \
--cc=will@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: 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
all inboxes | Powered by JetHome®