From: timur@codeaurora.org (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] hvc_dcc: disable user-space access to DCC
Date: Tue, 30 Jun 2015 16:23:07 -0500 [thread overview]
Message-ID: <1435699387-32591-4-git-send-email-timur@codeaurora.org> (raw)
In-Reply-To: <1435699387-32591-1-git-send-email-timur@codeaurora.org>
If the DCC driver loads, then disable user-space access to the DCC so that
we don't have two entities trying to access the DCC at the same time.
Signed-off-by: Timur Tabi <timur@codeaurora.org>
---
arch/arm/include/asm/dcc.h | 15 +++++++++++++++
arch/arm64/include/asm/dcc.h | 11 +++++++++++
drivers/tty/hvc/hvc_dcc.c | 2 ++
3 files changed, 28 insertions(+)
diff --git a/arch/arm/include/asm/dcc.h b/arch/arm/include/asm/dcc.h
index b74899d..c50056b 100644
--- a/arch/arm/include/asm/dcc.h
+++ b/arch/arm/include/asm/dcc.h
@@ -9,8 +9,11 @@
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*/
+#ifndef __ASM_DCC_H
+#define __ASM_DCC_H
#include <asm/barrier.h>
+#include <asm/hardware/cp14.h>
static inline u32 __dcc_getstatus(void)
{
@@ -39,3 +42,15 @@ static inline void __dcc_putchar(char c)
: "r" (c));
isb();
}
+
+static inline void __dcc_initialize(void)
+{
+ u32 val;
+
+ /* Disable user-space access to DCC */
+ val = MRC14(0, c0, c1, 0);
+ val |= 1 << 12; /* DSCR[Comms] */
+ MCR14(val, 0, c0, c1, 0);
+}
+
+#endif
diff --git a/arch/arm64/include/asm/dcc.h b/arch/arm64/include/asm/dcc.h
index fcb8d7d..7843e62 100644
--- a/arch/arm64/include/asm/dcc.h
+++ b/arch/arm64/include/asm/dcc.h
@@ -49,4 +49,15 @@ static inline void __dcc_putchar(char c)
isb();
}
+static inline void __dcc_initialize(void)
+{
+ u32 val;
+
+ /* Disable user-space access to DCC */
+ asm ("mrs %0, mdscr_el1\n"
+ " orr %0, %0, #4096\n" /* Set the TDCC bit */
+ " msr mdscr_el1, %0\n"
+ : "=r" (val));
+}
+
#endif
diff --git a/drivers/tty/hvc/hvc_dcc.c b/drivers/tty/hvc/hvc_dcc.c
index f8b8cf2..5ccafa4 100644
--- a/drivers/tty/hvc/hvc_dcc.c
+++ b/drivers/tty/hvc/hvc_dcc.c
@@ -231,6 +231,8 @@ static int __init hvc_dcc_console_init(void)
if (!hvc_dcc_check())
return -ENODEV;
+ __dcc_initialize();
+
/* Returns -1 if error */
ret = hvc_instantiate(0, 0, &hvc_dcc_get_put_ops);
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2015-06-30 21:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 21:23 [PATCH 1/4] hvc_dcc: bind driver to core0 for reads and writes Timur Tabi
2015-06-30 21:23 ` [PATCH 2/4] hvc_dcc: don't ignore errors during initialization Timur Tabi
2015-07-01 23:54 ` Stephen Boyd
2015-07-03 14:46 ` Timur Tabi
2015-06-30 21:23 ` [PATCH 3/4] [v3] ARM64: TTY: hvc_dcc: Add support for ARM64 dcc Timur Tabi
2015-06-30 21:23 ` Timur Tabi [this message]
2015-07-02 0:00 ` [PATCH 4/4] hvc_dcc: disable user-space access to DCC Stephen Boyd
2015-07-03 14:53 ` Timur Tabi
2015-07-01 1:37 ` [PATCH 1/4] hvc_dcc: bind driver to core0 for reads and writes Stephen Boyd
2015-07-01 1:57 ` Timur Tabi
2015-07-01 23:38 ` Stephen Boyd
2015-07-03 14:42 ` Timur Tabi
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=1435699387-32591-4-git-send-email-timur@codeaurora.org \
--to=timur@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).