Le 29/03/2016 12:06, Krzysztof Kozlowski a écrit : > Please look at this thread: > http://lists.infradead.org/pipermail/linux-arm-kernel/2015-July/359806.html > > Unfortunately I do not have any more details about this. So I understand MCT and Arch Timer use the same hardware timer and there were issues when the MCT interface reset it at boot and during resume and the Arch Timer consumers didn't expect it. In this thread there were links [1] to a patch to have the MCT not writing the timer anymore, thus allowing the two interfaces to co-exist. This patch was applied in commit 1d80415db64b. So no problem is to be expected when using both interfaces at the same time. I can see exynos5250 got its Arch Timer definition for KVM: - From the description of commit 2b7da98870bc ARM: dts: Add architected timer nodes for exynos5250 [...] This is required by KVM. So is there something else blocking adding this definition for 542x/5800 considering its effect is enabling KVM ? [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-May/257350.html => https://chromium-review.googlesource.com/#/c/200298/ => https://chromium-review.googlesource.com/#/c/201143/ for 3.8 [2] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-May/258622.html best regards, Adel -- 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
 |