ChanServ changed the topic of #linux-msm to:
marvin24 has joined #linux-msm
marvin24_ has quit [Ping timeout: 480 seconds]
pevik has joined #linux-msm
jhovold has joined #linux-msm
pevik has quit [Ping timeout: 480 seconds]
pevik has joined #linux-msm
pevik has quit [Remote host closed the connection]
pevik has joined #linux-msm
svarbanov has joined #linux-msm
pespin has joined #linux-msm
pespin has quit [Ping timeout: 480 seconds]
dliviu has quit [Quit: Going away]
dliviu has joined #linux-msm
lumag_ has joined #linux-msm
lumag__ has joined #linux-msm
lumag_ is now known as Guest55
lumag__ is now known as lumag_
lumag has quit [Killed (NickServ (This nickname is registered and protected))]
Guest55 has quit [Ping timeout: 480 seconds]
lumag has joined #linux-msm
djakov_ has quit [Remote host closed the connection]
djakov has joined #linux-msm
djakov has quit [Remote host closed the connection]
djakov has joined #linux-msm
djakov has quit [Remote host closed the connection]
djakov has joined #linux-msm
pespin has joined #linux-msm
pespin has quit [Remote host closed the connection]
pespin has joined #linux-msm
pevik has quit [Ping timeout: 480 seconds]
jhovold has quit [Ping timeout: 480 seconds]
pevik has joined #linux-msm
pespin has quit [Remote host closed the connection]
lumag_ has quit [Read error: No route to host]
lumag_ has joined #linux-msm
<lumag_> Marijn[m], wow, thanks for completing the DSI PHY conversion!
<Marijn[m]> lumag_: no worries, it was pretty trivial to get this done on my train rides... :) Now I can continue on other things :)
<Marijn[m]> lumag_: shall I add a separate patch to uniformly use two extra indents for function arguments on newlines? That makes it a bit cleaner. Note that changing function arguments does require me to reflow them otherwise
<Marijn[m]> lumag_: I don't think there have been any unintentional syntactical changes though
<deathmist> hey, is iwd (https://iwd.wiki.kernel.org/) known to be broken on ath10k_snoc? on MSM8998 I had to set ControlPortOverNL80211=false to stop the modem from crashing when trying to establish a connection...
<Marijn[m]> lumag_: do you mind if I fold the vco_name removal into the same patch though?
<lumag_> Marijn[m], syntax = whitespace/newlines
<lumag_> I'd prefer to have separate patches, one for the parent_hw, another one for the linebreaks,where that is sensible.
<lumag_> Feel free to fold vco_name into thee same patch, or into a separate patch, whichever is cleaner.
<lumag_> deathmist, I'm not sure.
<lumag_> Does plain iw work for you? I've been using in on the rb3
<deathmist> lumag_: if it involves running wpa_supplicant it most likely will yes, I can use NetworkManager successfully
<deathmist> just iwd has given me issues
<deathmist> I'd just like to narrow down where the issue might be: 1. my firmware, 2. my SoC in general (MSM8998 isn't the best supported SoC), 3. the ath10k_snoc driver in general
<lumag_> deathmist, I'd suggest asking kvalo
<lumag_> drop a message to ath10k@ ML
<deathmist> lumag_: I suppose I can do that tomorrow, was just hoping someone here using ath10k_snoc on another SoC than MSM8998 could give iwd a try and see if modem remoteproc starts crashing, I have a feeling I'm in a rather special position due to needing https://gitlab.com/msm8998-mainline/linux/-/commit/927111b0f5bf in my tree :/
<lumag_> deathmist, a strange question. On other platforms (8096 & others) I had modem crashing if I dind't have RMTFS kernel & userspace drives
<lumag_> Do you have them enabled and running?
<lumag_> I can test iwd in one of the next few days on rb3 (sdm845).
<deathmist> lumag_: yep, afaik all of pd-matter, rmtfs, tqftpserv (and diag-router in case of MSM8998) have to be running for WLAN to work
<bamse> deathmist: regarding diag-router, i had the same problem on sm8150...until i added a vote for the QDSS clock...which i think on 8998 would be <&rpmcc RPM_SMD_QDSS_CLK>
<bamse> deathmist: the missing msa_ready...jhugo was fighting that state machine on 8998 a long time ago, not sure if it's the same issue though...or if he got that resolved
<Mis012[m]> bamse: is 8998 supposed to be fused for MSA as a blank? surely not
<Mis012[m]> mine sadly is, but I suspect the stupid error of ODM provisioning qrd sec partition
<diederik> deathmist: ask on #iwd? The main devs were online there when I was last there (a few months ago)