linux-kernel - [PATCH v2 8/9] ARM: i.MX6: use generic on-chip SRAM allocator driver for OCRAM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1346405224-20399-9-git-send-email-p.zabel@pengutronix.de>
Date:	Fri, 31 Aug 2012 11:27:03 +0200
From:	Philipp Zabel <p.zabel@...gutronix.de>
To:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	Grant Likely <grant.likely@...retlab.ca>,
	Rob Herring <rob.herring@...xeda.com>,
	Paul Gortmaker <paul.gortmaker@...driver.com>,
	Shawn Guo <shawn.guo@...aro.org>,
	Richard Zhao <richard.zhao@...escale.com>,
	Huang Shijie <shijie8@...il.com>,
	Dong Aisheng <dong.aisheng@...aro.org>, kernel@...gutronix.de,
	devicetree-discuss@...ts.ozlabs.org
Cc:	Philipp Zabel <p.zabel@...gutronix.de>
Subject: [PATCH v2 8/9] ARM: i.MX6: use generic on-chip SRAM allocator driver for OCRAM

Signed-off-by: Philipp Zabel <p.zabel@...gutronix.de>
---
 arch/arm/boot/dts/imx6q.dtsi |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/boot/dts/imx6q.dtsi b/arch/arm/boot/dts/imx6q.dtsi
index 9cb0b50..1e463c4 100644
--- a/arch/arm/boot/dts/imx6q.dtsi
+++ b/arch/arm/boot/dts/imx6q.dtsi
@@ -111,8 +111,8 @@
 		       status = "disabled";
 		};
 
-		ocram@...00000 {
-			compatible = "fsl,imx-ocram";
+		ocram: ocram@...00000 {
+			compatible = "fsl,imx-ocram", "sram";
 			reg = <0x00900000 0x3f000>;
 		};
 
-- 
1.7.10.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/