Re: Feedback on hardware support for Odroid U3
Am Samstag, 13. Juni 2015, 15:09:32 schrieb Krzysztof Kozlowski: W dniu 12.06.2015 o 22:53, Thomas Pietrowski pisze: Hello again, first after fixing my booting problems I now get different warnings after boot. - config: http://pastebin.com/MHUu51pF - log: http://pastebin.com/9YMgMmFL - repo: arm-soc I read the last days that you are still working on the clk drivers, so as these warnings appear to be related to that you might be interested on them. You mean the warnings on clocks (starting from runtime PM and FIMC)? I hit them also on Trats2. Just need to find a person (or time) who will fix it... Ok then. I just don't remember that I had them when using 3.19.x code by Tobias Jakobi before. I'll test his latest code later. The reason I wanted to use code from arm-soc is that I thought his changes/patches are already here after two linux releases. However, in the past the CPU fan wasn't working at all (0 RPM) and /sys/class/thermal/[...]/temp reported more than 70°C (was compiling a newer kernel code at this moment). Don't believe it was healthy. Additionally my CPU fan it running at full RPM all the time. I checked the temperature just to be sure and it says it's 20°C. Is this problem known or can I help debugging it? After quick look at DTS, I think that on Exynos4412 Odroid family there is no fan defined. No fan so cooling is done only through CPU frequencies. The fan probably works on default setting from bootloader or default register values. Just something at this point which comes to my mind. Imagine we have the fan regulation/driver working. What happens when we simply disconnect the fan and the CPU hits higher temperatures? Will it still work on high frequencies or will it self-protect by using lower CPU frequencies? CPU throttling and CPU cooling should be two seperate processes, isn't it? The stock Odroid U3 has only passive cooler. That's true, but they (hardkernel) also sell a optional fan and the socket for is is still there when buying the board. See, http://www.hardkernel.com/main/products/prdt_info.php?g_code=G138760358261 for the optional fan. Therefore, it is not a hardware hack or whatever. Probably support for fan could be added... If you would like to take care of it, go for it! :) I just browsed Tobias Jakobi's linux-odroid repository at github and found out, that work is already made on that by people at Samsung :) https://github.com/tobiasjakobi/linux-odroid/commit/a2236c8f74321357e505be0a054032325a7e3a5d Hopefully both are also in this mailing list and interested in getting this upstream. In the mean time I'll test it based on tobiasjakobi's codebase again. Regards, Thomas -- 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
Boot hangs after Starting kernel... message [odroid u3]
Hello everyone, I'm just trying to get my kernel built for my Odroid U3, but no matter whether I use 4.0.x or the latest code from arm-soc repository 4.1.0-rc3, it ends at this message during boot: ### U-Boot 2015.07-rc1-00408-g012681b (May 30 2015 - 17:49:11 +) CPU:Exynos4412@1000MHz Model: Odroid based on Exynos4412 DRAM: 2 GiB ERROR: regulator-name of dev: ldo18, has nonunique value: nc at drivers/power/regulator/regulator-uclass.c:294/regulator_post_bind() ERROR: regulator-name of dev: ldo19, has nonunique value: nc at drivers/power/regulator/regulator-uclass.c:294/regulator_post_bind() ERROR: regulator-name of dev: ldo23, has nonunique value: nc at drivers/power/regulator/regulator-uclass.c:294/regulator_post_bind() ERROR: regulator-name of dev: ldo24, has nonunique value: nc at drivers/power/regulator/regulator-uclass.c:294/regulator_post_bind() ERROR: regulator-name of dev: ldo26, has nonunique value: nc at drivers/power/regulator/regulator-uclass.c:294/regulator_post_bind() ERROR: regulator-name of dev: buck9, has nonunique value: nc at drivers/power/regulator/regulator-uclass.c:294/regulator_post_bind() ldo20@VDDQ_EMMC_1.8V: set 180 uV; enabling ldo22@VDDQ_EMMC_2.8V: set 280 uV; enabling ldo21@TFLASH_2.8V: set 280 uV; enabling MMC: SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1 Net: No ethernet found. Hit any key to stop autoboot: 0 reading boot.scr 1143 bytes read in 18 ms (61.5 KiB/s) ## Executing script at 40408000 reading zImage-4.1 2497840 bytes read in 141 ms (16.9 MiB/s) reading exynos4412-odroidu3.dtb 54489 bytes read in 25 ms (2.1 MiB/s) Kernel image @ 0x40008000 [ 0x00 - 0x261d30 ] ## Flattened Device Tree blob at 41f0 Booting using the fdt blob at 0x41f0 reserving fdt memory region: addr=41f0 size=e000 Using Device Tree in place at 41f0, end 41f10fff Starting kernel ... ### The error messages during uboot loading just appear because there is something missing in it's RC, but don't think it is the reason, because a old build (3.19.x) just boots. Sadly my serial output does not give better error messages, so I'm asking here, because google'ing around didn't point me to any solutions. Do you have any hints why that happens? My .config can be found here - http://pastebin.com/qRLmtmmt . Is there a way to get early error messages during boot? Thanks! -- 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: Feedback on hardware support for Odroid U3
Am Freitag, 12. Juni 2015, 17:46:11 schrieb Mateusz Krawczuk: Could you send your config and log using gist.github.com, because pastebin.com is forbidden by company IT. Mateusz Krawczuk Samsung RD Institute Poland W dniu 12.06.2015 o 15:53, Thomas Pietrowski pisze: Hello again, first after fixing my booting problems I now get different warnings after boot. - config: http://pastebin.com/MHUu51pF - log: http://pastebin.com/9YMgMmFL - repo: arm-soc I read the last days that you are still working on the clk drivers, so as these warnings appear to be related to that you might be interested on them. Additionally my CPU fan it running at full RPM all the time. I checked the temperature just to be sure and it says it's 20°C. Is this problem known or can I help debugging it? Of course I can. Didn't know about this restriction. -config: https://gist.github.com/thopiekar/440059953391ccadc324 -log: https://gist.github.com/thopiekar/061d12802a4346eb783f -- 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
