From: Aneesh V <aneesh-l0cyMroinI0@public.gmane.org>
To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-patch-review-uAqBSO/uNfhBDgjK7y7TUQ@public.gmane.org
Cc: Aneesh V <aneesh-l0cyMroinI0@public.gmane.org>,
santosh.shilimkar-l0cyMroinI0@public.gmane.org
Subject: [RFC PATCH 3/3] dt: EMIF and lpddr2 device tree data for OMAP4 boards
Date: Sat, 17 Dec 2011 18:50:52 +0530 [thread overview]
Message-ID: <1324128052-11220-4-git-send-email-aneesh@ti.com> (raw)
In-Reply-To: <1324128052-11220-1-git-send-email-aneesh-l0cyMroinI0@public.gmane.org>
Device tree data for the EMIF sdram controllers in OMAP4
and DDR memories attached to OMAP4 boards.
Cc: Rajendra Nayak <rnayak-l0cyMroinI0@public.gmane.org>
Cc: Benoit Cousson <b-cousson-l0cyMroinI0@public.gmane.org>
Signed-off-by: Aneesh V <aneesh-l0cyMroinI0@public.gmane.org>
---
arch/arm/boot/dts/omap-common-devices.dtsi | 64 ++++++++++++++++++++++++++++
arch/arm/boot/dts/omap4-panda.dts | 13 ++++++
arch/arm/boot/dts/omap4-sdp.dts | 13 ++++++
arch/arm/boot/dts/omap4.dtsi | 18 ++++++++
4 files changed, 108 insertions(+), 0 deletions(-)
create mode 100644 arch/arm/boot/dts/omap-common-devices.dtsi
diff --git a/arch/arm/boot/dts/omap-common-devices.dtsi b/arch/arm/boot/dts/omap-common-devices.dtsi
new file mode 100644
index 0000000..6cf3dfa
--- /dev/null
+++ b/arch/arm/boot/dts/omap-common-devices.dtsi
@@ -0,0 +1,64 @@
+/*
+ * Common devices used in different OMAP boards
+ */
+
+/ {
+ elpida_2GS4: ddr {
+ compatible = "jedec,lpddr2-s4";
+ density = "2Gb";
+ io-width = "x32";
+ manufacturer = "Elpida";
+
+ tRPab-min-tck = <3>;
+ tRCD-min-tck = <3>;
+ tWR-min-tck = <3>;
+ tRASmin-min-tck = <3>;
+ tRRD-min-tck = <2>;
+ tWTR-min-tck = <2>;
+ tXP-min-tck = <2>;
+ tRTP-min-tck = <2>;
+ tCKE-min-tck = <3>;
+ tCKESR-min-tck = <3>;
+ tFAW-min-tck = <8>;
+
+ timings_elpida_2GS4_400mhz: ddr-timings@1 {
+ min-freq = <10000000>;
+ max-freq = <400000000>;
+ tRPab-ps = <21000>;
+ tRCD-ps = <18000>;
+ tWR-ps = <15000>;
+ tRAS-min-ps = <42000>;
+ tRRD-ps = <10000>;
+ tWTR-ps = <7500>;
+ tXP-ps = <7500>;
+ tRTP-ps = <7500>;
+ tCKESR-ps = <15000>;
+ tDQSCK-max-ps = <5500>;
+ tFAW-ps = <50000>;
+ tZQCS-ps = <90000>;
+ tZQCL-ps = <360000>;
+ tZQinit-ps = <1000000>;
+ tRAS-max-ns = <70000>;
+ };
+
+ timings_elpida_2GS4_200mhz: ddr-timings@ {
+ min-freq = <10000000>;
+ max-freq = <200000000>;
+ tRPab-ps = <21000>;
+ tRCD-ps = <18000>;
+ tWR-ps = <15000>;
+ tRAS-min-ps = <42000>;
+ tRRD-ps = <10000>;
+ tWTR-ps = <10000>;
+ tXP-ps = <7500>;
+ tRTP-ps = <7500>;
+ tCKESR-ps = <15000>;
+ tDQSCK-max-ps = <5500>;
+ tFAW-ps = <50000>;
+ tZQCS-ps = <90000>;
+ tZQCL-ps = <360000>;
+ tZQinit-ps = <1000000>;
+ tRAS-max-ns = <70000>;
+ };
+ };
+};
diff --git a/arch/arm/boot/dts/omap4-panda.dts b/arch/arm/boot/dts/omap4-panda.dts
index c702657..69ff0de 100644
--- a/arch/arm/boot/dts/omap4-panda.dts
+++ b/arch/arm/boot/dts/omap4-panda.dts
@@ -8,6 +8,7 @@
/dts-v1/;
/include/ "omap4.dtsi"
+/include/ "omap-common-devices.dtsi"
/ {
model = "TI OMAP4 PandaBoard";
@@ -26,4 +27,16 @@
device_type = "memory";
reg = <0x80000000 0x40000000>; /* 1 GB */
};
+
+ ocp {
+ emif1: emif@0x4c000000 {
+ cs1-used;
+ ddr-handle = <&elpida_2GS4>;
+ };
+
+ emif2: emif@0x4d000000 {
+ cs1-used;
+ ddr-handle = <&elpida_2GS4>;
+ };
+ };
};
diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
index 066e28c..1481e98 100644
--- a/arch/arm/boot/dts/omap4-sdp.dts
+++ b/arch/arm/boot/dts/omap4-sdp.dts
@@ -8,6 +8,7 @@
/dts-v1/;
/include/ "omap4.dtsi"
+/include/ "omap-common-devices.dtsi"
/ {
model = "TI OMAP4 SDP board";
@@ -26,4 +27,16 @@
device_type = "memory";
reg = <0x80000000 0x40000000>; /* 1 GB */
};
+
+ ocp {
+ emif1: emif@0x4c000000 {
+ cs1-used;
+ ddr-handle = <&elpida_2GS4>;
+ };
+
+ emif2: emif@0x4d000000 {
+ cs1-used;
+ ddr-handle = <&elpida_2GS4>;
+ };
+ };
};
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 4c61c82..4e88ea5 100644
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -99,5 +99,23 @@
reg = <0x48241000 0x1000>,
<0x48240100 0x0100>;
};
+
+ emif1: emif@0x4c000000 {
+ compatible = "ti,emif-lpddr2";
+ ti,hwmods = "emif1";
+ hw-caps-read-idle-ctrl;
+ hw-caps-ll-interface;
+ hw-caps-temp-alert;
+ };
+
+ emif2: emif@0x4d000000 {
+ compatible = "ti,emif-lpddr2";
+ ti,hwmods = "emif2";
+ phy-type = "phy-type-omap4";
+ hw-caps-read-idle-ctrl;
+ hw-caps-ll-interface;
+ hw-caps-temp-alert;
+ };
+
};
};
--
1.7.1
prev parent reply other threads:[~2011-12-17 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 13:20 [RFC PATCH 0/3] dt: device tree bindigs and data for EMIF and DDR Aneesh V
[not found] ` <1324128052-11220-1-git-send-email-aneesh-l0cyMroinI0@public.gmane.org>
2011-12-17 13:20 ` [RFC PATCH 1/3] dt: device tree bindings for DDR memories Aneesh V
2011-12-17 13:20 ` [RFC PATCH 2/3] dt: device tree bindings for TI's EMIF sdram controller Aneesh V
2011-12-17 13:20 ` Aneesh V [this message]
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=1324128052-11220-4-git-send-email-aneesh@ti.com \
--to=aneesh-l0cymroini0@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-patch-review-uAqBSO/uNfhBDgjK7y7TUQ@public.gmane.org \
--cc=santosh.shilimkar-l0cyMroinI0@public.gmane.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).