Re: [PATCH] ARM: dts: Add dts file for odroid XU3 board
Sjoerd Simons sjoerd.sim...@collabora.co.uk writes: Add DTS for the Hardkernel Odroid XU3. The name of the DTS file is kept the same as the vendors naming, which means it's prefixed with exynos5422 instead of exynos5800 as the SoC name even though it includes the exyno5800 dtsi. Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk Tested-by: Kevin Hilman khil...@linaro.org Tried this on top of linux-next (next-20141125 and next20141203) and boots fine on my odroid-xu3. Thanks for doing this, I've been meaning to get a DTS upstream for this platform myself. I also noticed that the imprecise aborts I've been seeing when booting this board with the smdk5420 DTS are gone, so I don't have to dig into those now either. Thanks! :) Kevin -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] ARM: dts: Add dts file for odroid XU3 board
On 1 December 2014 at 04:59, Sjoerd Simons sjoerd.sim...@collabora.co.uk wrote: Add DTS for the Hardkernel Odroid XU3. The name of the DTS file is kept the same as the vendors naming, which means it's prefixed with exynos5422 instead of exynos5800 as the SoC name even though it includes the exyno5800 dtsi. Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk Tested-by: Tyler Baker tyler.ba...@linaro.org Tested this atop of next-20141203 both on exynos_defconfig and multi_v7_defconfig. All configurations boot fine on my odroid-xu3 board, no imprecise aborts observed either. Thanks! Tyler -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] ARM: dts: Add dts file for odroid XU3 board
On Wed, 2014-12-03 at 11:53 -0800, Kevin Hilman wrote: Sjoerd Simons sjoerd.sim...@collabora.co.uk writes: Tried this on top of linux-next (next-20141125 and next20141203) and boots fine on my odroid-xu3. Thanks for doing this, I've been meaning to get a DTS upstream for this platform myself. I also noticed that the imprecise aborts I've been seeing when booting this board with the smdk5420 DTS are gone, so I don't have to dig into those now either. Thanks! :) For completeness, the problem with running the smdk5420 DTS on the XU3 is that the XU3 runs secure firmware while the SMD5420 doesn't.. Hence the imprecise aborts you were seeing. -- Sjoerd Simons sjoerd.sim...@collabora.co.uk Collabora Ltd. smime.p7s Description: S/MIME cryptographic signature
Re: [PATCH] ARM: dts: Add dts file for odroid XU3 board
Sjoerd Simons sjoerd.sim...@collabora.co.uk writes: On Wed, 2014-12-03 at 11:53 -0800, Kevin Hilman wrote: Sjoerd Simons sjoerd.sim...@collabora.co.uk writes: Tried this on top of linux-next (next-20141125 and next20141203) and boots fine on my odroid-xu3. Thanks for doing this, I've been meaning to get a DTS upstream for this platform myself. I also noticed that the imprecise aborts I've been seeing when booting this board with the smdk5420 DTS are gone, so I don't have to dig into those now either. Thanks! :) For completeness, the problem with running the smdk5420 DTS on the XU3 is that the XU3 runs secure firmware while the SMD5420 doesn't.. Hence the imprecise aborts you were seeing. OK, that's what I suspected but didn't take the time to verify. Thanks for the update. BTW, I'll have some DTS updates for the xu3 to enable the on-board INA2xx current sensors for easy power measurements without external instrumentation. Will send a patch for those soon. Kevin -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] ARM: dts: Add dts file for odroid XU3 board
On Tue, 2014-12-02 at 15:17 +0900, Heesub Shin wrote:
Hello Simons,
On 12/01/2014 09:59 PM, Sjoerd Simons wrote:
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+*/
+
+/dts-v1/;
+#include exynos5800.dtsi
Looking at exynos5800.dtsi, it derives from exynos5420.dtsi and seems
having differences on clock and mfc. Is it proper to include
exynos5800.dtsi here, instead of exynos5420.dtsi? It's just my curiosity
as I am not in a position to know detailed things on the soc. Only
semiconductor guys could answer this.
I would love to get a conclusive answer on this one as the exynos 5422
vs. exynos 5800 question seems to keep coming up (both on this list and
the u-boot one where XU3 support is being added as well).
As far as i understand things the Exynos 5800 is a variant of the
Exynos 5422 for chromebooks[0]. I suspect things are just being called
5800 in the kernel and u-boot as the chromebooks were the first boards
based on this SoC to reach mainline...
Which led to interesting things like:
#define EXYNOS5800_SOC_ID 0xE5422000
Iotw, the identifier for the 5800 is 0x5422, which doesn't really make
things more clear.
I'm working on the assumption that this SoC variation doesn't expose
differences to the OS. I did not yet test the MFC, but should get round
to that later this week, which should help in verifying the MFC side of
things at least.. I haven't yet seen any issues caused due to the
differences in clock setup between samsung,exynos5800-clock and
samsung,exynos5420-clock
+
+/ {
+ model = Hardkernel Odroid XU3;
+ compatible = hardkernel,odroid-xu3, samsung,exynos5800,
samsung,exynos5;
+
+ memory {
+ reg = 0x2000 0x8000;
+ };
Start address above should be 0x4000, not 0x2000.
Indeed, the Hardkernel DTS also starts at 0x4000, I missed that.
Looking at the other exynos5800/5420 based boards in the kernel they all
have their start offset at 0x2000, is this different for the XU3
because it runs with secure firmware or is there some other reason
behind this?
One more thing, having bootargs which specifies 'console=xxx' would be
better.
Hrm, i've got a dislike for chosen/bootargs as they typically seem
rather random/inconsistent (not sure who they're meant for). However, I
should indeed specify chosen/stdout-path to point to the serial console.
Thanks for your review!
0: See table at the bottom of
http://www.samsung.com/global/business/semiconductor/minisite/Exynos/w/solution.html#?v=octa_5422
--
Sjoerd Simons sjoerd.sim...@collabora.co.uk
Collabora Ltd.
smime.p7s
Description: S/MIME cryptographic signature
[PATCH] ARM: dts: Add dts file for odroid XU3 board
Add DTS for the Hardkernel Odroid XU3. The name of the DTS file is kept the
same as the vendors naming, which means it's prefixed with exynos5422
instead of exynos5800 as the SoC name even though it includes the
exyno5800 dtsi.
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/exynos5422-odroidxu3.dts | 325 +
2 files changed, 326 insertions(+)
create mode 100644 arch/arm/boot/dts/exynos5422-odroidxu3.dts
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 38c89ca..0a898cc 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -86,6 +86,7 @@ dtb-$(CONFIG_ARCH_EXYNOS) += exynos4210-origen.dtb \
exynos5420-arndale-octa.dtb \
exynos5420-peach-pit.dtb \
exynos5420-smdk5420.dtb \
+ exynos5422-odroidxu3.dtb \
exynos5440-sd5v1.dtb \
exynos5440-ssdk5440.dtb \
exynos5800-peach-pi.dtb
diff --git a/arch/arm/boot/dts/exynos5422-odroidxu3.dts
b/arch/arm/boot/dts/exynos5422-odroidxu3.dts
new file mode 100644
index 000..fe37004
--- /dev/null
+++ b/arch/arm/boot/dts/exynos5422-odroidxu3.dts
@@ -0,0 +1,325 @@
+/*
+ * Hardkernel Odroid XU3 board device tree source
+ *
+ * Copyright (c) 2014 Collabora Ltd.
+ * Copyright (c) 2013 Samsung Electronics Co., Ltd.
+ * http://www.samsung.com
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+*/
+
+/dts-v1/;
+#include exynos5800.dtsi
+
+/ {
+ model = Hardkernel Odroid XU3;
+ compatible = hardkernel,odroid-xu3, samsung,exynos5800,
samsung,exynos5;
+
+ memory {
+ reg = 0x2000 0x8000;
+ };
+
+ fimd@1440 {
+ status = okay;
+ };
+
+ firmware@02073000 {
+ compatible = samsung,secure-firmware;
+ reg = 0x02073000 0x1000;
+ };
+
+ fixed-rate-clocks {
+ oscclk {
+ compatible = samsung,exynos5420-oscclk;
+ clock-frequency = 2400;
+ };
+ };
+
+ hsi2c_4: i2c@12CA {
+ status = okay;
+
+ s2mps11_pmic@66 {
+ compatible = samsung,s2mps11-pmic;
+ reg = 0x66;
+ s2mps11,buck2-ramp-delay = 12;
+ s2mps11,buck34-ramp-delay = 12;
+ s2mps11,buck16-ramp-delay = 12;
+ s2mps11,buck6-ramp-enable = 1;
+ s2mps11,buck2-ramp-enable = 1;
+ s2mps11,buck3-ramp-enable = 1;
+ s2mps11,buck4-ramp-enable = 1;
+
+ s2mps11_osc: clocks {
+ #clock-cells = 1;
+ clock-output-names = s2mps11_ap,
+ s2mps11_cp, s2mps11_bt;
+ };
+
+ regulators {
+ ldo1_reg: LDO1 {
+ regulator-name = vdd_ldo1;
+ regulator-min-microvolt = 100;
+ regulator-max-microvolt = 100;
+ regulator-always-on;
+ };
+
+ ldo3_reg: LDO3 {
+ regulator-name = vdd_ldo3;
+ regulator-min-microvolt = 180;
+ regulator-max-microvolt = 180;
+ regulator-always-on;
+ };
+
+ ldo5_reg: LDO5 {
+ regulator-name = vdd_ldo5;
+ regulator-min-microvolt = 180;
+ regulator-max-microvolt = 180;
+ regulator-always-on;
+ };
+
+ ldo6_reg: LDO6 {
+ regulator-name = vdd_ldo6;
+ regulator-min-microvolt = 100;
+ regulator-max-microvolt = 100;
+ regulator-always-on;
+ };
+
+ ldo7_reg: LDO7 {
+ regulator-name = vdd_ldo7;
+ regulator-min-microvolt = 180;
+ regulator-max-microvolt = 180;
+ regulator-always-on;
+ };
+
+
Re: [PATCH] ARM: dts: Add dts file for odroid XU3 board
Hello Simons,
On 12/01/2014 09:59 PM, Sjoerd Simons wrote:
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+*/
+
+/dts-v1/;
+#include exynos5800.dtsi
Looking at exynos5800.dtsi, it derives from exynos5420.dtsi and seems
having differences on clock and mfc. Is it proper to include
exynos5800.dtsi here, instead of exynos5420.dtsi? It's just my curiosity
as I am not in a position to know detailed things on the soc. Only
semiconductor guys could answer this.
+
+/ {
+ model = Hardkernel Odroid XU3;
+ compatible = hardkernel,odroid-xu3, samsung,exynos5800,
samsung,exynos5;
+
+ memory {
+ reg = 0x2000 0x8000;
+ };
Start address above should be 0x4000, not 0x2000.
One more thing, having bootargs which specifies 'console=xxx' would be
better.
regards,
heesub
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
