From: Andrew Donnellan <ajd@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: [PATCH] powerpc/configs: Add debug config fragment
Date: Thu, 1 Aug 2019 14:58:55 +1000 [thread overview]
Message-ID: <20190801045855.5822-1-ajd@linux.ibm.com> (raw)
Add a debug config fragment that we can use to put useful debug options
into.
Currently we only define a target for powernv[_be]_debug_defconfig, and the
only option included is to enable debugfs SCOM access.
Suggested-by: Michael Ellerman <mpe@ellerman.id.au>
Signed-off-by: Andrew Donnellan <ajd@linux.ibm.com>
---
arch/powerpc/Makefile | 8 ++++++++
arch/powerpc/configs/debug.config | 1 +
2 files changed, 9 insertions(+)
create mode 100644 arch/powerpc/configs/debug.config
diff --git a/arch/powerpc/Makefile b/arch/powerpc/Makefile
index c345b79414a9..aff022592d89 100644
--- a/arch/powerpc/Makefile
+++ b/arch/powerpc/Makefile
@@ -331,6 +331,14 @@ PHONY += powernv_be_defconfig
powernv_be_defconfig:
$(call merge_into_defconfig,powernv_defconfig,be)
+PHONY += powernv_be_debug_defconfig
+powernv_be_debug_defconfig:
+ $(call merge_into_defconfig,powernv_defconfig,be debug)
+
+PHONY += powernv_debug_defconfig
+powernv_debug_defconfig:
+ $(call merge_into_defconfig,powernv_defconfig,debug)
+
PHONY += mpc85xx_defconfig
mpc85xx_defconfig:
$(call merge_into_defconfig,mpc85xx_basic_defconfig,\
diff --git a/arch/powerpc/configs/debug.config b/arch/powerpc/configs/debug.config
new file mode 100644
index 000000000000..a14ae1f20d60
--- /dev/null
+++ b/arch/powerpc/configs/debug.config
@@ -0,0 +1 @@
+CONFIG_SCOM_DEBUGFS=y
--
2.20.1
next reply other threads:[~2019-08-01 5:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 4:58 Andrew Donnellan [this message]
2019-10-30 12:14 ` [PATCH] powerpc/configs: Add debug config fragment Michael Ellerman
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=20190801045855.5822-1-ajd@linux.ibm.com \
--to=ajd@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).