From: Fred Chen <fredchen.openbmc@gmail.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 3/5] ARM: dts: aspeed: santabarbara: Add JTAG GPIO line names
Date: Fri, 7 Aug 2026 16:34:06 +0800 [thread overview]
Message-ID: <20260807083415.672008-4-fredchen.openbmc@gmail.com> (raw)
In-Reply-To: <20260807083415.672008-1-fredchen.openbmc@gmail.com>
Label the GPIO lines used for the CPU JTAG debug interface
(TDI/TCK/TMS/TDO and CPLD DBREQ/TRST). These lines are driven from
userspace via GPIO bit-banging to emulate JTAG signals for CPU
debugging, so naming them lets userspace request the lines by name.
Signed-off-by: Fred Chen <fredchen.openbmc@gmail.com>
---
.../boot/dts/aspeed/aspeed-bmc-facebook-santabarbara.dts | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-santabarbara.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-santabarbara.dts
index 04fa9a5e0d04..9d334a01d407 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-santabarbara.dts
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-santabarbara.dts
@@ -199,7 +199,9 @@ &gpio0 {
/*F0-F7*/ "","","","","","","","",
/*G0-G7*/ "FM_MUX1_SEL_R","","","","","","","",
/*H0-H7*/ "","","","","","","","",
- /*I0-I7*/ "","","","","","","","",
+ /*I0-I7*/ "","JTAG_1_BMC_TDI",
+ "JTAG_1_BMC_TCK","JTAG_1_BMC_TMS",
+ "JTAG_1_BMC_TDO","","","",
/*J0-J7*/ "","","","","","","","",
/*K0-K7*/ "","","","","","","","",
/*L0-L7*/ "","","","","","","","",
@@ -1911,8 +1913,8 @@ &sgpiom0 {
"FM_IOEXP_U541_INT_N","FM_MODULE_PWR_EN_N_3B",
/*H4-H7 line 120-127*/
"FM_IOEXP_PDB2_U1003_INT_N","FM_MODULE_PWR_EN_N_4B",
- "","",
- "","",
+ "","JTAG_CPLD_DBREQ",
+ "","JTAG_CPLD_TRST",
"FM_MAIN_PWREN_RMC_EN_ISO_R","",
/*I0-I3 line 128-135*/
"","","","",
--
2.52.0
next prev parent reply other threads:[~2026-08-07 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 8:34 [PATCH v3 0/5] ARM: dts: aspeed: santabarbara: Add system monitoring GPIOs Fred Chen
2026-08-07 8:34 ` [PATCH v3 1/5] " Fred Chen
2026-08-07 8:34 ` [PATCH v3 2/5] ARM: dts: aspeed: santabarbara: Disable power monitor nodes Fred Chen
2026-08-07 8:34 ` Fred Chen [this message]
2026-08-07 8:34 ` [PATCH v3 4/5] ARM: dts: aspeed: santabarbara: Add SGPIO line names Fred Chen
2026-08-07 8:34 ` [PATCH v3 5/5] ARM: dts: aspeed: santabarbara: Add leak cable present IO expander Fred Chen
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=20260807083415.672008-4-fredchen.openbmc@gmail.com \
--to=fredchen.openbmc@gmail.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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