devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Kaiser <martin@kaiser.cx>
To: Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <kernel@pengutronix.de>,
	Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Martin Kaiser <martin@kaiser.cx>
Subject: [PATCH 2/2] ARM: i.MX25: globally disable supervisor protect
Date: Tue, 31 Jan 2017 20:20:02 +0100	[thread overview]
Message-ID: <1485890402-22974-2-git-send-email-martin@kaiser.cx> (raw)
In-Reply-To: <1485890402-22974-1-git-send-email-martin@kaiser.cx>

The problem described in 6befda9a272b98bfb1dc772efc3564644cbfb270
for the i.MX53 platform applies to i.MX25 as well.

E.g. CSPI1+SDMA and SSI1+SDMA are not working with the default AIPS
configuration. Modifiy the AIPS configuration to allow access to the bus
by SDMA and peripherals.

Signed-off-by: Martin Kaiser <martin@kaiser.cx>
---
 arch/arm/mach-imx/mach-imx25.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/arch/arm/mach-imx/mach-imx25.c b/arch/arm/mach-imx/mach-imx25.c
index 32dcb5e..353b86e 100644
--- a/arch/arm/mach-imx/mach-imx25.c
+++ b/arch/arm/mach-imx/mach-imx25.c
@@ -23,6 +23,11 @@ static void __init imx25_init_early(void)
 	mxc_set_cpu_type(MXC_CPU_MX25);
 }
 
+static void __init imx25_dt_init(void)
+{
+	imx_aips_allow_unprivileged_access("fsl,imx25-aips");
+}
+
 static void __init mx25_init_irq(void)
 {
 	struct device_node *np;
@@ -41,6 +46,7 @@ static const char * const imx25_dt_board_compat[] __initconst = {
 
 DT_MACHINE_START(IMX25_DT, "Freescale i.MX25 (Device Tree Support)")
 	.init_early	= imx25_init_early,
+	.init_machine	= imx25_dt_init,
 	.init_late      = imx25_pm_init,
 	.init_irq	= mx25_init_irq,
 	.dt_compat	= imx25_dt_board_compat,
-- 
2.1.4

  reply	other threads:[~2017-01-31 19:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 19:20 [PATCH 1/2] ARM: dts: i.MX25: add AIPS control registers Martin Kaiser
2017-01-31 19:20 ` Martin Kaiser [this message]
     [not found] ` <1485890402-22974-1-git-send-email-martin-XxZfDwE/svGeZLLa646FqQ@public.gmane.org>
2017-02-01  7:09   ` Sascha Hauer
2017-02-01 22:16   ` [PATCH v2] " Martin Kaiser
     [not found]     ` <1485987378-27784-1-git-send-email-martin-XxZfDwE/svGeZLLa646FqQ@public.gmane.org>
2017-02-02  7:09       ` Sascha Hauer
2017-02-03 12:59   ` [PATCH v3] " Martin Kaiser
     [not found]     ` <1486126792-28186-1-git-send-email-martin-XxZfDwE/svGeZLLa646FqQ@public.gmane.org>
2017-02-03 17:27       ` Sascha Hauer
2017-04-03 19:47   ` [PATCH 1/2 v4] " Martin Kaiser
2017-04-03 19:47     ` [PATCH 2/2 v2] ARM: i.MX25: globally disable supervisor protect Martin Kaiser
     [not found]       ` <1491248825-23041-2-git-send-email-martin-XxZfDwE/svGeZLLa646FqQ@public.gmane.org>
2017-04-04 13:14         ` Shawn Guo
     [not found]     ` <1491248825-23041-1-git-send-email-martin-XxZfDwE/svGeZLLa646FqQ@public.gmane.org>
2017-04-04 13:13       ` [PATCH 1/2 v4] ARM: dts: i.MX25: add AIPS control registers Shawn Guo

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=1485890402-22974-2-git-send-email-martin@kaiser.cx \
    --to=martin@kaiser.cx \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.trumtrar@pengutronix.de \
    --cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).