On 07.07.2015 23:30, Kukjin Kim wrote: > Krzysztof Kozlowski wrote: >> >> On 06.07.2015 23:12, Chanho Park wrote: >>> The odroid-xu3 board which is based on exynos5422 not exynos5800 is >>> booted from cortex-a7 core unlike exynos5800. The odroid-xu3's cpu order >>> is quite strange. cpu0 and cpu5-7 are cortex-a7 cores and cpu1-4 are >>> cortex-a15 cores. To correct this mis-odering, I added exynos5422.dtsi >>> and reversing cpu orders from exynos5420. Now, cpu0-3 are cortex-a7 and >>> cpu4-7 are cortex-a15. >>> >>> Reviewed-by: Krzysztof Kozlowski <k.kozlowski@xxxxxxxxxxx> >>> Signed-off-by: Chanho Park <chanho61.park@xxxxxxxxxxx> >>> --- >>> Changes from v4: >>> - Remove temporal patch in e-mail body >>> >>> Changes from v3: >>> - include this exynos5422-cpus.dtsi in the exynos5422-odroidxu3-common.dtsi >>> >>> Changes from v2: >>> - drop inclusion of exynos5420.dtsi from exynos5422-cpus.dtsi >>> - drop compatibles from exynos5422-cpus.dtsi >>> >>> Changes from v1: >>> - rename exynos5422.dtsi to exynos5422-cpus.dtsi >>> - include the dtsi file top of the exynos5422-odroidxu3.dts >>> >>> Secondary cpu booting problem[1] is not resolved yet. Need more investigations >>> to work booting 8 cores correctly. >>> >>> [1]: http://www.spinics.net/lists/linux-samsung-soc/msg45525.html >>> >>> arch/arm/boot/dts/exynos5422-cpus.dtsi | 81 ++++++++++++++++++++++ >>> arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi | 1 + >>> 2 files changed, 82 insertions(+) >>> create mode 100644 arch/arm/boot/dts/exynos5422-cpus.dtsi >> >> Thanks, applied to my tree. I'll sent it to Kukjin later for 4.3 unless >> he picks it up from LKML. >> > Hi Krzysztof, > > If you're OK, I'd like to pick this up into Samsung tree with your ack based on > 4.2-rc1. Yes, please go ahead. It already has my reviewed-by tag. However the sob does not match author so it should be resent once again. Best regards, Krzysztof -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |