paulk-nyan-big has quit [Ping timeout: 276 seconds]
prahal has quit [Ping timeout: 276 seconds]
paulk-nyan-big has joined #linux-exynos
prahal has joined #linux-exynos
paulk-nyan-big has quit [Ping timeout: 260 seconds]
theblazehen82 has joined #linux-exynos
theblazehen has quit [Read error: Connection reset by peer]
amitk has quit [Ping timeout: 265 seconds]
amitk has joined #linux-exynos
amitk has quit [Quit: leaving]
afaerber has joined #linux-exynos
afaerber has quit [Ping timeout: 250 seconds]
afaerber has joined #linux-exynos
theblazehen82 has quit [Read error: Connection reset by peer]
theblazehen82 has joined #linux-exynos
pekka10 has joined #linux-exynos
<prahal>
s5p-mfc with dma debug on complains at boot , that we unmap what we do not own
<prahal>
seems the 13620000.sysmmu is the one that is properly assigned the offending pgtable at boot then unmap ... but in between
<prahal>
13620000.sysmmu is assigned other devices pgtables (fimc, codec, drm)
<prahal>
could each assignement overwrites the previous one (I end up with onl y the drm one attached to the 13620000.sysmmu when the unmap error tricgger)
krzk_ has joined #linux-exynos
<prahal>
well could also be : mfc has two devices bound to the same pgtable ... could be it dma unmap twice < this I can sort out
LiquidAcid has joined #linux-exynos
krzk_ has quit [Quit: leaving]
<prahal>
no it does not unmap twice.... but it umap only once ! I mean no unmap on all the