ChanServ changed the topic of #linux-msm to:
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
junari has joined #linux-msm
vbijnljhgxryz has joined #linux-msm
vbijnljhgxryz is now known as still-alive
junari has quit [Remote host closed the connection]
still-alive has quit [Remote host closed the connection]
ungeskriptet is now known as Guest7586
ungeskriptet has joined #linux-msm
Guest7586 has quit [Ping timeout: 480 seconds]
jhovold has joined #linux-msm
mripard has joined #linux-msm
ungeskriptet has quit [Ping timeout: 480 seconds]
ungeskriptet has joined #linux-msm
ungeskriptet has quit [Ping timeout: 480 seconds]
<konradybcio> luka177: what does it show if you use the test pattern generator? (https://github.com/SoMainline/linux/commit/1c33e7b01038542b359a5bb6e386df6face89781)
<Marijn[m]> lumag: what do you think about moving the TPG behind a compiler define or a module parameter (or even `const bool`)? There's no up-to-date documentation explaining _from where_ to call this method
<lumag> Marijn[m], we should probably hook it through the debugfs
<konradybcio> debugfs +1
<Marijn[m]> That's an even better option to dynamically turn it on and off at runtime
ldts_ has joined #linux-msm
ungeskriptet has joined #linux-msm
<abhinav__> lumag Marijn[m] if you hook it up to debugfs, then it will take effect in the next suspend/resume
<abhinav__> because the screen would have already turned on with the usual display pipeline
<abhinav__> so i am guessing you plan to do something like 1) echo 1 > tpg 2) mode_active "0" and mode_active "1" ?
jbg has joined #linux-msm