ChanServ changed the topic of #linux-msm to:
marvin24 has quit [Ping timeout: 480 seconds]
marvin24 has joined #linux-msm
Daaanct12 has quit [Remote host closed the connection]
Daaanct12 has joined #linux-msm
jhovold has joined #linux-msm
bhsharma- has joined #linux-msm
bhsharma- has quit []
brgl0 has joined #linux-msm
bhsharma- has joined #linux-msm
mani_s- has joined #linux-msm
brgl0 has quit [Quit: The Lounge - https://thelounge.chat]
mani_s- has quit []
bhsharma- has quit [Quit: ZNC 1.7.2 - https://znc.in]
brgl0 has joined #linux-msm
bryanodonoghue4 has joined #linux-msm
bhsharma- has joined #linux-msm
brgl0 has quit [Quit: The Lounge - https://thelounge.chat]
bryanodonoghue4 has quit []
bhsharma- has quit [Quit: ZNC 1.7.2 - https://znc.in]
pespin has joined #linux-msm
<aka_[m]> Marijn: so i took some opportunity to check DS code for nvt-ts
<aka_[m]> turns out DS sets defaults and does not ret when get_fw_info fails
<aka_[m]> decided to try this way and i do get touch initialized
<aka_[m]> however
<aka_[m]> its fucked
<aka_[m]> FW registers TS in full resolution so 1080x2246 but device is 720x1520
<aka_[m]> i believe we could do with resolution props inside dts which will be parsed into data
<aka_[m]> not FW but driver have hardcoded resolution
<aka_[m]> my bad
<aka_[m]> i have some issues with pins too
<aka_[m]> i need to lock->unlock screen to get it to register touch
<aka_[m]> does touchscreen-size-x work in such situation? i cannot really find this binding anywhere via bootlin
jhovold has quit [Ping timeout: 480 seconds]
pespin has quit []