quarkyalice_ has joined #tegra
quarkyalice_ has quit [Ping timeout: 268 seconds]
TundraMan has joined #tegra
TundraMan has quit [Ping timeout: 252 seconds]
marvin24 has quit [Ping timeout: 255 seconds]
marvin24 has joined #tegra
quarkyalice_ has joined #tegra
quarkyalice_ has quit [Remote host closed the connection]
quarkyalice_ has joined #tegra
quarkyalice_ has quit [Client Quit]
p2-mate has quit [Ping timeout: 252 seconds]
p2-mate has joined #tegra
torez has joined #tegra
torez has quit [*.net *.split]
torez has joined #tegra
<DavidHeidelberg> digetx do u think it's possible that Nexus 7 2012 and 2013 has same TS? elan,ektf3624? Since in DTS for 2013 was defined ekth3500, but drivers supplied with android is for elan-ktf3 and seems like it does use _NORMAL2 which is implemented onl for EKTF
gouchi has joined #tegra
marvin24 has quit [Ping timeout: 255 seconds]
marvin24 has joined #tegra
<digetx> doesn't touchscreen work on 2013?
<DavidHeidelberg> digetx yes and no, it's in mainline, but it was having hack, which is currently legit codepath for ektf3624 since 5.12
<DavidHeidelberg> .. and using compatible ekth3500, I switched to ektf3624 and still works as expected without any hacks
<digetx> internet suggests it should be eKTH3258 for 2013
<DavidHeidelberg> cool, so I'll just add compatible
<digetx> it's probably compatible with 3500 and then you shouldn't need extra compatibles
<DavidHeidelberg> it's except that there is if which gives _NORMAL2 touch only to ektf3624
<DavidHeidelberg> so, maybe only remove the condition, since it can be used on both?
<digetx> it may depend on firmware version
<DavidHeidelberg> exactly
<DavidHeidelberg> so it doesn't matter much which version is it, more firmware ver
<digetx> yes, it's likely that all those elan chips are very similar hardware-wise and it's only fw that differs depending on issue date
<digetx> but we don't know for sure, elantek doesn't share any docs and fw sources, elan people also were not willing to talk when we upstreamed 3624 support
<DavidHeidelberg> anyway, I think I can assume, that the if == 3624 can be taken out, if someone will have issues after that, adding FW detection and whitelisting it for my FW would be solution
<digetx> the if == 3624 was requested by the input/ maintainer
<digetx> we didn't have it in the first version of the patches
digetx has quit [Read error: Connection reset by peer]
digetx has joined #tegra
digetx has quit [Read error: Connection reset by peer]
digetx has joined #tegra
digetx has quit [Read error: Connection reset by peer]
digetx has joined #tegra
torez has quit [Remote host closed the connection]
digetx has quit [Read error: Connection reset by peer]
digetx has joined #tegra
gouchi has quit [Remote host closed the connection]