zombah has quit [Remote host closed the connection]
amitk has quit [Quit: leaving]
afaerber_ is now known as afaerber
zombah has joined #linux-exynos
afaerber has quit [Quit: Verlassend]
Tenkawa has joined #linux-exynos
Tenkawa has joined #linux-exynos
afaerber has joined #linux-exynos
Tenkawa has quit [Remote host closed the connection]
Tenkawa has joined #linux-exynos
Tenkawa has joined #linux-exynos
Tenkawa has quit [Quit: leaving]
bgamari has quit [Ping timeout: 256 seconds]
bgamari has joined #linux-exynos
liquidAcid has joined #linux-exynos
zombah has quit [Quit: Leaving]
aballier has quit [Quit: leaving]
Mahdi has joined #linux-exynos
<Mahdi>
is there any way to access memory controller?
<Mahdi>
is it possible to change some of its parameters?
Mahdi has quit []
<javier__>
ojn: it seems the imprecise abort error on exynos is caused by the exynos drm driver, I wonder why I'm not suprised...
afaerber has quit [Quit: Verlassend]
<ojn>
javier__: *headdesk* yeah, not surprised.
<liquidAcid>
javier__, is that a regression?
<javier__>
liquidAcid: I'm not sure if is a regression or a latent bug that got exposed after commit 6261b06de565 ("regulator: Defer lookup of supply to regulator_get")
afaerber has joined #linux-exynos
<javier__>
liquidAcid: since no other platform has issues after that commit I think the problem is with the regulator consumer driver (exynos drm)
<javier__>
liquidAcid: now that I know that exynos drm is the culprit, it will be easier for me to figure out