ChanServ changed the topic of #linux-msm to:
marvin24 has joined #linux-msm
marvin24_ has quit [Ping timeout: 480 seconds]
jhovold has joined #linux-msm
pevik has joined #linux-msm
enok has quit [Remote host closed the connection]
enok has joined #linux-msm
pespin has joined #linux-msm
<Marijn[m]> calebccff Newbyte: Any progress on DSC testing or are we still fighting the generator/driver to provide an un-broken panel in the first place?
<Marijn[m]> calebccff: As far as I understood the panel behaves normally without resetting it; any luck with DSC? With/without PPS-sending?
<Newbyte> Marijn: Sorry, a bug in pylibfdt distracted me. I can try to look into it today.
<Newbyte> Are there any patches I should apply when testing this?
<Marijn[m]> Newbyte: no problem, it's a regular work week anyway so expect severely limited response from my side
<Marijn[m]> Newbyte: yes please, dsc patch series v3, all 10 patches
<Marijn[m]> And patch up your panel driver with the latest dsc stuff (I merged calebccff 's PR earlier today) so that it's compatible
<Newbyte> Marijn: I'm not very good at browsing lkml, could you link the patches? I saw you CC'd me on a response, but I don't understand how to get to the patches from that.
<Marijn[m]> I recommend `b4 shazam <lore url from any of the messages/replies in that thread>`
<Marijn[m]> Also I find lore.kernel.org much more usable than lkml
<Newbyte> Thanks, got it
<Marijn[m]> lore.kernel.org/linux-arm-msm for your convenience. Patches are at https://lore.kernel.org/linux-arm-msm/20221009184824.457416-1-marijn.suijten@somainline.org/T/#u
<Newbyte> Marijn: What do you prefer I use as base? linux-next? 6.1-rc1? sdm845-mainline?
<Marijn[m]> I based these on -next from a week or 2 ago
<Marijn[m]> Newbyte: whatever doesn't conflict and has the necessary DT to get display on your side. Note that this series doesn't apply cleanly without Dmitry's DSC cleanup series
<Newbyte> Thanks, I'll see about it
<Marijn[m]> Newbyte: thanks! When in doubt or running into conflicts, feel free to push the branch somewhere public and point me to it
<calebccff> Marijn[m]: I've been busy with other stuff... sorry! I'd be reasonably confident that the pixel 3 issues are more likely panel quirks than DSC bugs. I don't think it should be a blocker to get your DSC patches merged
<calebccff> and tbh I don't think I can commit a lot of time to debugging the pixel 3 panel at the minute
<Marijn[m]> calebccff: but it was working without resets, correct? Otherwise vkoul might be able to help out here despite not having access to the device anymore?
<Marijn[m]> Otherwise it's up to lumag and abhinav__ to decide on this, but I'd vouch for my device with a working panel driver to count as the golden sample if pixel3 cannot be trusted / relied on for now.
<Marijn[m]> I'm planning on sending the driver some time soon now that this dsc set had some time to mature
<lumag> Marijn[m], your patches look sane
<konradybcio> if p3 doesn't work after reset, I don't think it can be trusted
<konradybcio> bootloader may be setting different configuration
<konradybcio> as seen on xperias for example
<Marijn[m]> konradybcio: and half my patch series can't truly be tested if the whole pps part is kept out of the test cases
<Marijn[m]> lumag: calebccff: will you in any case take to the mailing lists and let abhinav__ know that pixel 3 testing seems out of the question, a t least for now, so that it doesn't become a necessary blocker?
<calebccff> Marijn[m]: I replied to the email you CC'd me on, hopefully that's ok
<lumag> Marijn[m], I don't think P3 is a blocker now.
<abhinav__> Marijn[m] lumag i never had concerns with the patch myself. Personally, I wanted to migrate to this API even when the DSC series was first pushed. the issues should have been properly root-caused that time itself. That being said, the onus is then on vinod / users of pixel3 to report/debug whatever issues arise out of this computation as noone
<abhinav__> seems to have one to test it atm. hence I have acked the change now.
<konradybcio> we have lots of test subjects for dsc
<konradybcio> though Marijn is working on getting command mode support to behave on newer socs first
jhovold has quit [Ping timeout: 480 seconds]
<Marijn[m]> abhinav__: understood, just thought it made sense to test on >1 panel/platform but better skip p3 if the driver is unreliable in the first place. I'll respin it with a reworded commit message and the test robot issue fixed.
pevik has quit [Ping timeout: 480 seconds]
<Newbyte> Marijn: Hi again, I'm having issues with the kernel hanging on G7 so I'm not sure I'll be able to test the DSC patches anytime soon unfortunately.
<Marijn[m]> Newbyte: thanks for trying anyway, looks like the series will be merged on good faith while I hopefully enable more (Sony) testing material "soon". Feel free to ping me if/whenever you get to it
<Newbyte> sounds good :)
pespin has quit [Remote host closed the connection]
<konradybcio> since it's so simple, might as well
<konradybcio> you won't make anybody angry with resending 5 loc probably :D
<calebccff> heh yeah right... v3 time
<steev> anyone happen to know why i might have stuck phys on sdm850 with completely vanilla 6.0.2?
<steev> i can't see anything in the dts that might be causing it, but didn't look at the phy files themselves
<steev> neither of those have been touched in the dts since 2020, so i'm assuming something elsewhere
<konradybcio> wasn't there major cleanups/rewrites to qmp phy code lately?
<steev> yeah, but i didn't think that was in 6.0
<konradybcio> any chance you could checkout the qmp driver(s) at 5.19 or whatever was the previous release and check?
<konradybcio> also, is there anything special regarding them in dmesg?
<steev> [ 1.570357] qcom-qmp-usb-phy 88e9000.phy: Registered Qcom-QMP phy
<steev> [ 1.570873] qcom-qmp-usb-phy 88eb000.phy: Registered Qcom-QMP phy
<steev> [ 16.379535] platform a600000.usb: deferred probe pending
<steev> [ 16.379505] platform a800000.usb: deferred probe pending
<steev> that's all there is for usb, phy has a few other lines, but nothing
<steev> blargh
<steev> it's the reverts
<steev> shot a mail off... maybe
bencrus[m] has joined #linux-msm