Re: [PATCH v2] ARM: dts: Add dts file for odroid XU3 board
Sjoerd Simons sjoerd.sim...@collabora.co.uk writes: On Wed, 2015-01-07 at 23:49 +, Jonathan Stone -SISA wrote: On On Wed, 2015-01-07 at 18:37 +, Sjoerd Simons writes wrote: On Wed, 2015-01-07 at 18:37 +, Anand Moon wrote: [...] Only 4 core cpu's are on my board. Also CpuFreq is not working. Can you share some point on this. The defconfig is using the bL switcher, which pairs up big and little cores to make them appear as one core.. So for 8 real cores, you'll get 4 virtual cores. That configuration is appropriate for the 5420, which allegedly has a hardware bug in the cache-coherence between the Cortex-A7 block and the Cortex-A15 block. Newer Exynos 5 SoCs -- 5422/5800, 5620, etc -- don't have that bug. The scheduler should configured to do HMP on all 8 (or 6) cores. I don't have a 5410, but I assume it has the same bug as the 5420. Yes the kernel/scheduler could be configured like that, but exynos_defconfig turns on bL rather then HMP. Now it's not unthinkable to add code/dts properties to select the right/preferred scheduling strategy depending on the board (HMP vs. bL). But proper HMP scheduling is still a work in progress in mainline Yes, HMP scheduling is not yet ready for mainline, which is why the switcher is enabled by default. If you turn the switcher off, you will indeed get all 8 cores, but you may get some rather strange and sub-optimal results with performance since from the scheduler perspective, it will balance tasks across all 8 CPUs as if they were identical. and iirc specifically on the XU3 there are open issue wrt. MCPM and its secure firmware. I've added Kevin to the CC as he's been working on this topic so should know the status a lot better then i do. The broken firmware issues don't affect scheduling directly, but affect the low-power states that are available to the kernel. Since the firwmware doesn't allow proper access to CCI, low-power states that require MCPM are not available, which, among other things, means the clusters can not be powered down. The XU3 kernel supplied by HardKernel shows all 8 cores, and does HMP scheduling across all 8. Yes, that's independant of the dts though as mentioned above. Also there are still opne issues to booting up all cores on an XU3 afaik. See http://www.spinics.net/lists/linux-samsung-soc/msg39523.html I haven't looked closely at the hardkernel tree to see what HMP scheduling patches they're using, but it must be something out of tree. 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 v2] ARM: dts: Add dts file for odroid XU3 board
On Wed, 2015-01-07 at 23:49 +, Jonathan Stone -SISA wrote: On On Wed, 2015-01-07 at 18:37 +, Sjoerd Simons writes wrote: On Wed, 2015-01-07 at 18:37 +, Anand Moon wrote: [...] Only 4 core cpu's are on my board. Also CpuFreq is not working. Can you share some point on this. The defconfig is using the bL switcher, which pairs up big and little cores to make them appear as one core.. So for 8 real cores, you'll get 4 virtual cores. That configuration is appropriate for the 5420, which allegedly has a hardware bug in the cache-coherence between the Cortex-A7 block and the Cortex-A15 block. Newer Exynos 5 SoCs -- 5422/5800, 5620, etc -- don't have that bug. The scheduler should configured to do HMP on all 8 (or 6) cores. I don't have a 5410, but I assume it has the same bug as the 5420. Yes the kernel/scheduler could be configured like that, but exynos_defconfig turns on bL rather then HMP. Now it's not unthinkable to add code/dts properties to select the right/preferred scheduling strategy depending on the board (HMP vs. bL). But proper HMP scheduling is still a work in progress in mainline and iirc specifically on the XU3 there are open issue wrt. MCPM and its secure firmware. I've added Kevin to the CC as he's been working on this topic so should know the status a lot better then i do. The XU3 kernel supplied by HardKernel shows all 8 cores, and does HMP scheduling across all 8. Yes, that's independant of the dts though as mentioned above. Also there are still opne issues to booting up all cores on an XU3 afaik. See http://www.spinics.net/lists/linux-samsung-soc/msg39523.html I tried v1.0 of the Odroid-XU3 DTB patch, applied to linux-next 20150107. I'm only seeing 1 core running on my Odroid-XU3. The USB 3.0 port works (great!) but I'm not getting any HDMI output. I didn't try DisplayPort. I'll gladly try v2 of the patch on an XU3; is there a better base to apply the patch to? HDMI output is broken on all exynos boards in mainline atm. For exynos 5, see the thread here: http://www.spinics.net/lists/linux-samsung-soc/msg40708.html As far as a i know with the DTS as posted (just posted v3 with a small improvement), all base functionality that can work on mainline (MMC/SD, network, USB2, USB3) works. Some less important bits (fan control power sensors) are outstanding, but that really shouldn't block the merge of the DTS. -- Sjoerd Simons sjoerd.sim...@collabora.co.uk Collabora Ltd. smime.p7s Description: S/MIME cryptographic signature
Re: [PATCH v2] ARM: dts: Add dts file for odroid XU3 board
On 01/08/15 17:49, Sjoerd Simons wrote: On Wed, 2015-01-07 at 23:49 +, Jonathan Stone -SISA wrote: On On Wed, 2015-01-07 at 18:37 +, Sjoerd Simons writes wrote: On Wed, 2015-01-07 at 18:37 +, Anand Moon wrote: [...] Only 4 core cpu's are on my board. Also CpuFreq is not working. Can you share some point on this. The defconfig is using the bL switcher, which pairs up big and little cores to make them appear as one core.. So for 8 real cores, you'll get 4 virtual cores. That configuration is appropriate for the 5420, which allegedly has a hardware bug in the cache-coherence between the Cortex-A7 block and the Cortex-A15 block. Newer Exynos 5 SoCs -- 5422/5800, 5620, etc -- don't have that bug. The scheduler should configured to do HMP on all 8 (or 6) cores. I don't have a 5410, but I assume it has the same bug as the 5420. Yes the kernel/scheduler could be configured like that, but exynos_defconfig turns on bL rather then HMP. Now it's not unthinkable to add code/dts properties to select the right/preferred scheduling strategy depending on the board (HMP vs. bL). But proper HMP scheduling is still a work in progress in mainline and iirc specifically on the XU3 there are open issue wrt. MCPM and its secure firmware. I've added Kevin to the CC as he's been working on this topic so should know the status a lot better then i do. The XU3 kernel supplied by HardKernel shows all 8 cores, and does HMP scheduling across all 8. Yes, that's independant of the dts though as mentioned above. Also there are still opne issues to booting up all cores on an XU3 afaik. See http://www.spinics.net/lists/linux-samsung-soc/msg39523.html I tried v1.0 of the Odroid-XU3 DTB patch, applied to linux-next 20150107. I'm only seeing 1 core running on my Odroid-XU3. The USB 3.0 port works (great!) but I'm not getting any HDMI output. I didn't try DisplayPort. I'll gladly try v2 of the patch on an XU3; is there a better base to apply the patch to? HDMI output is broken on all exynos boards in mainline atm. For exynos 5, see the thread here: http://www.spinics.net/lists/linux-samsung-soc/msg40708.html As far as a i know with the DTS as posted (just posted v3 with a small improvement), all base functionality that can work on mainline (MMC/SD, network, USB2, USB3) works. Some less important bits (fan control power sensors) are outstanding, but that really shouldn't block the merge of the DTS. Sjoerd, thanks. I'll take your updated patch once you submit version3. - Kukjin -- 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 v2] ARM: dts: Add dts file for odroid XU3 board
On On Wed, 2015-01-07 at 18:37 +, Sjoerd Simons writes wrote: On Wed, 2015-01-07 at 18:37 +, Anand Moon wrote: [...] Only 4 core cpu's are on my board. Also CpuFreq is not working. Can you share some point on this. The defconfig is using the bL switcher, which pairs up big and little cores to make them appear as one core.. So for 8 real cores, you'll get 4 virtual cores. That configuration is appropriate for the 5420, which allegedly has a hardware bug in the cache-coherence between the Cortex-A7 block and the Cortex-A15 block. Newer Exynos 5 SoCs -- 5422/5800, 5620, etc -- don't have that bug. The scheduler should configured to do HMP on all 8 (or 6) cores. I don't have a 5410, but I assume it has the same bug as the 5420. The XU3 kernel supplied by HardKernel shows all 8 cores, and does HMP scheduling across all 8. I tried v1.0 of the Odroid-XU3 DTB patch, applied to linux-next 20150107. I'm only seeing 1 core running on my Odroid-XU3. The USB 3.0 port works (great!) but I'm not getting any HDMI output. I didn't try DisplayPort. I'll gladly try v2 of the patch on an XU3; is there a better base to apply the patch to?
Re: [PATCH v2] ARM: dts: Add dts file for odroid XU3 board
On Wed, 2015-01-07 at 18:37 +, Anand Moon wrote: Hi Sjoerd, I am using 3.18.0 kernel on my odroidxu3 board. Using exynos_defconfig I am able to boot the board. Are you able to get all the 8 core CPU up and running ? Only 4 core cpu's are on my board. Also CpuFreq is not working. Can you share some point on this. The defconfig is using the bL switcher, which pairs up big and little cores to make them appear as one core.. So for 8 real cores, you'll get 4 virtual cores. root@odroid-xu3:/usr/src/odroidxu3-3.18.y-debug# cat /proc/cpuinfo | grep processor processor : 0 processor : 5 processor : 6 processor : 7 Below are the logs of the board. [9.720905] Registering SWP/SWPB emulation handler [9.725457] big.LITTLE switcher initializing [9.729518] CPU0 paired with CPU4 [9.732805] CPU5 paired with CPU3 [9.736069] CPU6 paired with CPU2 [9.739386] CPU7 paired with CPU1 [9.742688] GIC ID for CPU 0 cluster 1 is 4 [9.746816] GIC ID for CPU 0 cluster 0 is 0 [9.800575] IRQ153 no longer affine to CPU1 [9.803065] CPU1: shutdown [9.813482] GIC ID for CPU 1 cluster 0 is 1 [9.869776] IRQ154 no longer affine to CPU2 [9.872218] CPU2: shutdown [9.879985] GIC ID for CPU 2 cluster 0 is 2 [9.924656] IRQ155 no longer affine to CPU3 [9.927094] CPU3: shutdown [9.935544] GIC ID for CPU 3 cluster 0 is 3 [9.989578] IRQ160 no longer affine to CPU4 [9.991787] CPU4: shutdown [ 10.001003] GIC ID for CPU 1 cluster 1 is 5 [ 10.003812] GIC ID for CPU 2 cluster 1 is 6 [ 10.007976] GIC ID for CPU 3 cluster 1 is 7 [ 10.015308] big.LITTLE switcher initialized [ 10.031368] registered taskstats version 1 [ 10.038110] pinctrl core: add 2 pinmux maps [ 10.038374] samsung-pinctrl 1340.pinctrl: found group selector 39 for gpx3-7 [ 10.038541] samsung-pinctrl 1340.pinctrl: found group selector 39 for gpx3-7 [ 10.038586] samsung-pinctrl 1340.pinctrl: request pin 39 (gpx3-7) for 1453.hdmi [ 10.039440] of_get_named_gpiod_flags: parsed 'hpd-gpio' property of node '/hdmi@1453[0]' - status (0) [ 10.040227] exynos-hdmi 1453.hdmi: Looking up vdd-supply from device tree [ 10.042869] exynos-hdmi 1453.hdmi: Looking up vdd_osc-supply from device tree [ 10.044700] exynos-hdmi 1453.hdmi: Looking up vdd_pll-supply from device tree [ 10.046528] exynos-hdmi 1453.hdmi: Looking up hdmi-en-supply from device tree [ 10.046558] exynos-hdmi 1453.hdmi: Looking up hdmi-en-supply property in node /hdmi@1453 failed [ 10.048281] samsung-pinctrl 1340.pinctrl: request pin 39 (gpx3-7) for gpx3:39 [ 10.071915] exynos-mixer 1445.mixer: probe start [ 10.076942] exynos-sysmmu 1465.sysmmu: Enabled [ 10.076975] exynos-mixer 1445.mixer: exynos_iommu_attach_device: Attached IOMMU with pgtable 0x42264000 [ 10.077570] exynos-drm exynos-drm: bound 1445.mixer (ops mixer_component_ops) [ 10.089655] exynos-drm exynos-drm: bound 1453.hdmi (ops hdmi_component_ops) [ 10.095639] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 10.102242] [drm] No driver support for vblank timestamp query. [ 10.161814] cma: cma_alloc(cma c11c3218, count 2025, align 8) [ 10.256074] cma: cma_alloc(): returned ef6cd400 [ 10.457934] Console: switching to colour frame buffer device 274x77 [ 10.511095] exynos-drm exynos-drm: fb0: frame buffer device [ 10.516212] exynos-drm exynos-drm: registered panic notifier [ 10.537871] [drm] Initialized exynos 1.0.0 20110530 on minor 0 [ 10.545873] s3c-rtc 101e.rtc: setting system clock to 2015-01-07 17:50:09 UTC (1420653009) [ 10.553979] power-domain: Power-off latency exceeded, new value 388375 ns [ 10.560076] power-domain: Power-off latency exceeded, new value 6221750 ns [ 10.567225] power-domain: Power-off latency exceeded, new value 248791 ns [ 10.573666] power-domain: Power-off latency exceeded, new value 6502916 ns [ 11.093083] MAIN_DC: disabling [ 11.099738] ALSA device list: [ 11.101347] No soundcards found. [ 11.117975] Freeing unused kernel memory: 1732K (c079b000 - c094c000) [ 11.775702] systemd-udevd[1676]: starting version 204 [ 15.298783] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ 17.878286] init: plymouth-upstart-bridge main process (1732) terminated with status 1 [ 17.885458] init: plymouth-upstart-bridge main process ended, respawning [ 18.211733] init: plymouth-upstart-bridge main process (1741) terminated with status 1 [ 18.219007] init: plymouth-upstart-bridge main process ended, respawning [ 18.432104] init: plymouth-upstart-bridge main process (1745) terminated with status 1 [ 18.439365] init: plymouth-upstart-bridge main process ended, respawning [ 22.612268] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro [ 26.072597]
Re: [PATCH v2] ARM: dts: Add dts file for odroid XU3 board
Hi Sjoerd,
On 12/05/2014 04:27 AM, Sjoerd Simons 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
---
Changes since v1:
* Add chosen/linux,stdout-path to point the serial console device
* Change memory start offset to 0x4000 to match the vendors DTS (pointed
out by Heesub Shin)
* Declare base address size for the memory banks to be used by the MFC
Kevin, Tyler, even though the changes are small i didn't want to just stick
your Tested-By on. Could you both be so kind to retest this on your XU3's ?
Heesub, I would still love to know the reason for having the memory start
address at 0x4000 for this board?
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/exynos5422-odroidxu3.dts | 332
+
2 files changed, 333 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..0dc9cf8
--- /dev/null
+++ b/arch/arm/boot/dts/exynos5422-odroidxu3.dts
@@ -0,0 +1,332 @@
+/*
+ * 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 = 0x4000 0x8000;
+ };
+
+ chosen {
+ linux,stdout-path = serial_2;
+ };
+
+ 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 {
+
Re: [PATCH v2] ARM: dts: Add dts file for odroid XU3 board
On Mon, 2015-01-05 at 17:18 +0900, Joonyoung Shim wrote:
Hi Sjoerd,
On 12/05/2014 04:27 AM, Sjoerd Simons 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
---
Changes since v1:
* Add chosen/linux,stdout-path to point the serial console device
* Change memory start offset to 0x4000 to match the vendors DTS
(pointed
out by Heesub Shin)
* Declare base address size for the memory banks to be used by the MFC
Kevin, Tyler, even though the changes are small i didn't want to just stick
your Tested-By on. Could you both be so kind to retest this on your XU3's ?
Heesub, I would still love to know the reason for having the memory start
address at 0x4000 for this board?
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/exynos5422-odroidxu3.dts | 332
+
2 files changed, 333 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
+
+hdmi {
+ status = okay;
+ hpd-gpio = gpx3 7 0;
+ pinctrl-names = default;
+ pinctrl-0 = hdmi_hpd_irq;
+
+ vdd_osc-supply = ldo10_reg;
+ vdd_pll-supply = ldo8_reg;
+ vdd-supply = ldo8_reg;
ldo10 and ldo8 are right? I think ldo7 and ldo6 are related with hdmi
from schematic.
Nice catch. I followed hardkernels dts here, which refers to ldo10
ldo8, however double-checking the schematics indeed indicate that ldo7
and ldo6 are used the HDMI supplies.
I'll do some testing and follow-up
--
Sjoerd Simons sjoerd.sim...@collabora.co.uk
Collabora Ltd.
smime.p7s
Description: S/MIME cryptographic signature
[PATCH v2] 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
---
Changes since v1:
* Add chosen/linux,stdout-path to point the serial console device
* Change memory start offset to 0x4000 to match the vendors DTS (pointed
out by Heesub Shin)
* Declare base address size for the memory banks to be used by the MFC
Kevin, Tyler, even though the changes are small i didn't want to just stick
your Tested-By on. Could you both be so kind to retest this on your XU3's ?
Heesub, I would still love to know the reason for having the memory start
address at 0x4000 for this board?
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/exynos5422-odroidxu3.dts | 332 +
2 files changed, 333 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..0dc9cf8
--- /dev/null
+++ b/arch/arm/boot/dts/exynos5422-odroidxu3.dts
@@ -0,0 +1,332 @@
+/*
+ * 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 = 0x4000 0x8000;
+ };
+
+ chosen {
+ linux,stdout-path = serial_2;
+ };
+
+ 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;
+
Re: [PATCH v2] ARM: dts: Add dts file for odroid XU3 board
On 4 December 2014 at 11:27, 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-20141204, both on exynos_defconfig and multi_v7_defconfig. All configurations boot fine on my odroid-xu3 board. Cheers, 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 v2] 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 --- Changes since v1: * Add chosen/linux,stdout-path to point the serial console device * Change memory start offset to 0x4000 to match the vendors DTS (pointed out by Heesub Shin) * Declare base address size for the memory banks to be used by the MFC Kevin, Tyler, even though the changes are small i didn't want to just stick your Tested-By on. Could you both be so kind to retest this on your XU3's ? Tested-by: Kevin Hilman khil...@linaro.org Tested on top of linux-next(ish) and Javier's dp-integ branch and it's booting fine including HDMI display output. 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
