From: Andreas Fenkart <andreas.fenkart@streamunlimited.com>
To: paul@pwsan.com, tony@atomide.com
Cc: linux@arm.linux.org.uk, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, afzal@ti.com, hvaibhav@ti.com,
daniel@zonque.org,
Andreas Fenkart <andreas.fenkart@streamunlimited.com>
Subject: [PATCH] ARM: OMAP2+: am33xx: preserve JTAG clock aka debugss_ick.
Date: Thu, 7 Mar 2013 14:13:27 +0100 [thread overview]
Message-ID: <1362662007-13782-2-git-send-email-andreas.fenkart@streamunlimited.com> (raw)
This fixes JTAG support on am33xx.
Signed-off-by: Andreas Fenkart <andreas.fenkart@streamunlimited.com>
---
arch/arm/Kconfig.debug | 6 ++++++
arch/arm/mach-omap2/cclock33xx_data.c | 11 ++++++++---
2 files changed, 14 insertions(+), 3 deletions(-)
diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
index acdddda..8120940 100644
--- a/arch/arm/Kconfig.debug
+++ b/arch/arm/Kconfig.debug
@@ -632,4 +632,10 @@ config PID_IN_CONTEXTIDR
additional instructions during context switch. Say Y here only if you
are planning to use hardware trace tools with this kernel.
+config JTAG
+ bool "Enable JTAG clock"
+ depends on SOC_AM33XX
+ help
+ Enable or keep JTAG clock enabled
+
endmenu
diff --git a/arch/arm/mach-omap2/cclock33xx_data.c b/arch/arm/mach-omap2/cclock33xx_data.c
index 476b820..b7470de 100644
--- a/arch/arm/mach-omap2/cclock33xx_data.c
+++ b/arch/arm/mach-omap2/cclock33xx_data.c
@@ -429,9 +429,14 @@ DEFINE_STRUCT_CLK(smartreflex1_fck, dpll_core_ck_parents, clk_ops_null);
* - usbotg_fck (its additional clock and not really a modulemode)
* - ieee5000
*/
-DEFINE_CLK_GATE(debugss_ick, "dpll_core_m4_ck", &dpll_core_m4_ck, 0x0,
- AM33XX_CM_WKUP_DEBUGSS_CLKCTRL, AM33XX_MODULEMODE_SWCTRL_SHIFT,
- 0x0, NULL);
+#ifdef CONFIG_JTAG
+#define DEBUGSS_FLAGS CLK_IGNORE_UNUSED
+#else
+#define DEBUGSS_FLAGS 0x0
+#endif
+DEFINE_CLK_GATE(debugss_ick, "dpll_core_m4_ck", &dpll_core_m4_ck,
+ DEBUGSS_FLAGS, AM33XX_CM_WKUP_DEBUGSS_CLKCTRL,
+ AM33XX_MODULEMODE_SWCTRL_SHIFT, 0x0, NULL);
DEFINE_CLK_GATE(mmu_fck, "dpll_core_m4_ck", &dpll_core_m4_ck, 0x0,
AM33XX_CM_GFX_MMUDATA_CLKCTRL, AM33XX_MODULEMODE_SWCTRL_SHIFT,
--
1.7.10.4
next reply other threads:[~2013-03-07 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 13:13 Andreas Fenkart [this message]
2013-03-07 13:20 ` Bedia, Vaibhav
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=1362662007-13782-2-git-send-email-andreas.fenkart@streamunlimited.com \
--to=andreas.fenkart@streamunlimited.com \
--cc=afzal@ti.com \
--cc=daniel@zonque.org \
--cc=hvaibhav@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=paul@pwsan.com \
--cc=tony@atomide.com \
/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®