ChanServ changed the topic of #linux-msm to:
davidinux is now known as Guest8650
davidinux has joined #linux-msm
Guest8650 has quit [Ping timeout: 480 seconds]
marvin24 has joined #linux-msm
marvin24_ has quit [Ping timeout: 480 seconds]
Danct12 is now known as Guest8665
Danct12 has joined #linux-msm
Danct12 has quit [Quit: WeeChat 4.0.2]
Danct12 has joined #linux-msm
<Rayyan> How long should I wait before submitting a v2?
dliviu has quit [Ping timeout: 480 seconds]
dliviu has joined #linux-msm
<aka_[m]> this is more of a qcom,agg-ports port right?
<aka_[m]> not qport = X,Y one
davidinux has quit [Quit: WeeChat 3.5]
<konradybcio> yes
Danct12 has quit [Quit: WeeChat 4.0.2]
<Nia[m]> hey all- sorry to butt in and unsure if this is the right place to ask but, I've been working on an sm8350 device (oneplus-lemonadep) and have been getting really weird behaviour out of the usb controller that I haven't seen reported of other sm8350 devices; for some reason, the gdsc driver errors on trying to power on said controller (`usb30_{prim, sec}_gdsc status stuck at 'off'` followed by a trace). I've tried a known-working kernel tree
<Nia[m]> don't have UART unfortunately so can only read logs via framebuffer and pulling them from storage post-mortem
<Nia[m]> for a very similar device with no luck so I'm assuming some kind of firmware bug in my device? everything else I've tried to enable (ufs, display, etc) has been flawless though. no luck researching this issue since it seems very device-specific, and attempting to debug what exactly goes wrong has been utterly fruitless so far. does someone here know what vague direction I could look in to debug this? can provide kernel & config if relevant. I
<konradybcio> on my 8350 xperia usb works
<konradybcio> and i presume the xiaomi guy who submitted his 8350 phone a few days back also has it running with no issues
<konradybcio> would that change if you added clk_ignore_unused pd_ignore_unused?
<Nia[m]> haven't tried the latter, let me see
<Rayyan> konradybcio: I've been fixing some of the errors from check_dtbs but I can't figure out this one
<Rayyan> the same thing is done in lg-lenok
<konradybcio> Rayyan: this is very random but try this https://pastebin.com/raw/6W3BNFBp
<konradybcio> also sm8450 defines additionalProperties above patternProperties
<konradybcio> worth giving a shot
<Rayyan> >patch does not apply
<Rayyan> argh
<konradybcio> doing it by hand is faster ;)
<Rayyan> yeah the additionalproperties things fixes it
<Rayyan> guess that's another patch?
<konradybcio> yep
<Rayyan> hmm how do i describe it
<Rayyan> i have no clue why reordering it fixes it
<Nia[m]> <konradybcio> "would that change if you added..." <- forgot to update but still no change
<Rayyan> i put those changes into a commit, ran the check again and the issue somehow came back
<Rayyan> w h y
<DylanVanAssche> srinik: I'm trying to get Bluetooth HFP working with SDM845 and WCN3990. This involves adding SLIMBUS_7 and SLIMBUS_8 to the audio drivers. It uses a separate `qcom,slim-ngd-v2.1.0` thing to send audio to the Bluetooth chip
<DylanVanAssche> srinik: However, it seems that adding twice a driver with compatible `qcom,slim-ngd-v2.1.0` heaviyl crashes the device since it said something about 'already registered' in dmeesg. The device crashes heavily so I cannot extract more from the logs
<DylanVanAssche> srinik: Do you have any idea or know how to add Bluetooth HFP support? This would make SDM845 phones really useful for Bluetooth headsets and car multimedia systems
<DylanVanAssche> srinik: These are my patches on top of 6.5: https://gitlab.com/dylanvanassche/linux-torvalds/-/commits/bt-sco-hfp-6.5
<DylanVanAssche> srinik: Could you also please reply to this e-mail thread so we can move further with the SDSP SDM845 support in FastRPC? https://lore.kernel.org/linux-arm-msm/20230511141146.30465-2-me@dylanvanassche.be/T/