<lumag_>
konradybcio, kholk[m] could you please check/confirm that old eDP driver is not used on your hardware?
<lumag_>
I've sent a patch to remove it, but would like to have a confirmation that it's not used (or not planned to be used at some point in future) on some obscure hardware
<konradybcio>
the last meaningful soc that used it was msm8974 (other than 8998 which already has the 10nm dp hw so i guess it could use the new driver instead?)
<lumag_>
konradybcio, yeah, I think it was 8974 and 8984(?).
<konradybcio>
8084, sd805
<konradybcio>
which is a 8974proplusmax
<konradybcio>
(with a4xx)
<konradybcio>
the 8974 xperias did have display out though, but i believe mhi uses hdmi..
<konradybcio>
the only 8974 device that could ma-a-a-aybe use edp would be the lumia 2520 tablet, but considering it's not a laptop, it may as well be DSI
<konradybcio>
and probably only like 3 people still have it
<lumag_>
:-D
<konradybcio>
btw lumag_, do you have dsi working on anything newer than 845?
<lumag_>
8064 uses HDMI for the slimport
<konradybcio>
it does not work for us on 6125, 6350, 8250
<lumag_>
konradybcio, yes, 8250. Using it regularly
<konradybcio>
video mode panel?
<lumag_>
video panel and dsi-> HDMI bridge
<konradybcio>
that's what I thought..
<konradybcio>
all of our problematic devices have cmd
<lumag_>
konradybcio, any cheap/popular devices showing this error?
<konradybcio>
ugh no sony phone can be considered cheap heh
<konradybcio>
even the 10iii which is a chinese odm device stamped with a sony logo
<konradybcio>
it's so cheap in fact, the stock rom has force reboot instructions in the power menu
<konradybcio>
cheap as in bad quality, because it's still like 110 kebabs here
<konradybcio>
actually, even more :P
<lumag_>
what about second hand market / older phones?
<lumag_>
ah, 10iii is from 2014?
<konradybcio>
no, 2021
<konradybcio>
hm to be fair there are a bunch of xiaomi phones with 6125
<konradybcio>
but i have no idea whether they use cmd or vid
<konradybcio>
probably a mix of both, considering their cost-cutting measures
* lumag_
is not going to spend 400 usd on the 'just testing' device
<konradybcio>
redmi note 8 has sd665 (sm6125) and is a touch over 100e new
<konradybcio>
but then i still have no idea about the panel type used
<konradybcio>
+ on xiaomi you have to register a mi account with an active sim card AND wait 2 weeks to unlock..
<konradybcio>
that was supposed to be a plus sign as the first character, element is stupid sometimes
<lumag_>
it is in the hexchat
<konradybcio>
fun stuff
<lumag_>
konradybcio, just to be sure: are those phones expected to work w/o DSC?
<lumag_>
also do you use dpu or mdp5 for 6125?
<konradybcio>
5 II does have dsc, but i am almost sure it's only enabled for 120fps, as simplefb works normally
<konradybcio>
dpu for all of these platforms
<konradybcio>
5II -> pdx206 -> 8250
<konradybcio>
if dsc was enabled on all modes, i'd expect simplefb to be totally garbled
<lumag_>
konradybcio, why? IIRC it doesn't have any dynamic configuration
<lumag_>
konradybcio, I can try using CMD mode with the kwaek's display bundle on RB5.
<konradybcio>
because passing raw data to hardware expecting compressed data should not work
<konradybcio>
otherwise we wouldn't need that big patchset from Vinod to have pixel3 working
<konradybcio>
unless I misunderstand something
<lumag_>
not for the simplefb (= keep setup from the bootloader)
<lumag_>
I do not know if the bootoader has support for DSC
<konradybcio>
the other devices don't have dsc though
<konradybcio>
and all have the same timeout error
<lumag_>
konradybcio, as I wrote, I can try using CMD mode with the ls060t1sx01 (driven by nt35695). msm-4.9 has a dtsi for dsi-panel-nt35695b-truly-fhd-cmd
<lumag_>
so I'd guess cmd mode _might_ work
<lumag_>
but I'm not sure if hw supports that.
<lumag_>
I think TE signal is not connected
<konradybcio>
please do, so that we can narrow it down..
<lumag_>
konradybcio, is this a new thing or 'it never worked'?
<konradybcio>
it never worked
lumag_ has quit [Quit: Leaving]
sboyd has quit [Ping timeout: 480 seconds]
hfink has quit [Ping timeout: 480 seconds]
arnd has quit [Ping timeout: 480 seconds]
CosmicPenguin has quit [Ping timeout: 480 seconds]
dianders has quit [Ping timeout: 480 seconds]
jessica_24 has quit [Ping timeout: 480 seconds]
abhinav__ has quit [Ping timeout: 480 seconds]
agross_ has joined #linux-msm
robclark_ has joined #linux-msm
pundir_ has joined #linux-msm
jstultz has quit [Ping timeout: 480 seconds]
pundir has quit [Ping timeout: 480 seconds]
jhugo has quit [Ping timeout: 480 seconds]
robclark has quit [Ping timeout: 480 seconds]
jessica_24 has joined #linux-msm
jstultz has joined #linux-msm
agross has quit [Ping timeout: 480 seconds]
agross_ is now known as agross
sboyd has joined #linux-msm
CosmicPenguin has joined #linux-msm
abhinav__ has joined #linux-msm
robclark_ has quit []
robclark_ has joined #linux-msm
arnd has joined #linux-msm
dianders has joined #linux-msm
hfink has joined #linux-msm
jhugo has joined #linux-msm
robclark_ has quit []
marvin24 has joined #linux-msm
marvin24_ has quit [Ping timeout: 480 seconds]
robclark_ has joined #linux-msm
cmeerw has joined #linux-msm
Danct12 has quit [Read error: Connection reset by peer]
Danct12 has joined #linux-msm
<Marijn[m]>
<lumag_> "also do you use dpu or mdp5 for..." <- I wrote a dpu config for sm6125 - and it's now running into the exact same "failed wait_for_idle" errors as our 6350 and 8250 platforms
<Marijn[m]>
<lumag_> "is not going to spend 400 usd on..." <- Don't worry, we can test and try things out too
<calebccff>
does anyone know who is maintainer of the qcom,spmi-pmic-arb and qcom,spmi-pmic dt-binding docs?
lumag_ has joined #linux-msm
robclark_ is now known as robclark
<minecrell>
lumag_: Hehe, the msleep() checkpatch warnings in your panel driver happened exactly in the part that wasn't made by the generator :D
<minecrell>
It has magic to use usleep_range() when needed