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
cmeerw has joined #linux-msm
cmeerw has quit [Ping timeout: 480 seconds]
aka_ has joined #linux-msm
aka_ has quit []
pevik has quit [Remote host closed the connection]
pg12_ has quit [Ping timeout: 480 seconds]
pg12_ has joined #linux-msm
djakov has quit [Read error: Connection reset by peer]
djakov has joined #linux-msm
cmeerw has joined #linux-msm
svarbanov has joined #linux-msm
svarbanov has quit [Ping timeout: 480 seconds]
<deathmist> bamse: ping, would you mind tagging qrtr, pd-mapper, rmtfs & tqftpserv repos?
<bamse> deathmist: sorry, forgot about it again...i don't mind, but i would prefer to look at a bug i found recently in tqftpserv before just tagging that
<bamse> deathmist: to avoid forgetting it i've created a ticket in our jira thing and assigned to myself...
deathmist has quit [Remote host closed the connection]
<Tooniis[m]> there is currently this issue where slimbus-qcom-ngd-ctrl doesn't work if it's probed after adsp is powered on. It's because it relies on getting a ssr event to start, but it never gets its ssr notifier gets registered after adsp is powered on.
deathmist has joined #linux-msm
<Tooniis[m]> to fix it, I made some changes in remoteproc/qcom_common.c to keep track of the last ssr event issued and added a function to get this state, then made slimbus-qcom-ngd-ctrl call that function and start right away if it finds that adsp is already on
<Tooniis[m]> but I am not sure if this is the right approach
<Tooniis[m]> any comments?
<bamse> Tooniis[m]: i was worried that this would become an issue when i reviewed the ssr notification patches...
<bamse> Tooniis[m]: i don't like sprinkling getters for apis that are callback driven in nature, but i haven't spent enough thought on it yet...
<Tooniis[m]> I also thought of calling the notifier once when registered with the current state, but I am not sure if that might have some side effects
<bamse> Tooniis[m]: i fear all available options comes with side effects :/
<bamse> Tooniis[m]: but i haven't thought the details through
<bamse> Tooniis[m]: do you have the patch in your mailbox that broke this? (i.e. introduced the ssr notifier dependency)
<Tooniis[m]> I can look for it in the git history
<bamse> Tooniis[m]: would you be able to reply to that patch describing the problem, and make sure that you have Bjorn Andersson and Siddharth Gupta among the recipients?
<bamse> Siddharth must have run into this downstream...
<Tooniis[m]> I will look for it then
deathmist has quit [Remote host closed the connection]
deathmist has joined #linux-msm
<steev> Tooniis[m]: what does that look like in dmesg output? i think i see that (or similar?) on one of my c630's but not the other
<steev> Tooniis[m]: something along these lines? https://bpa.st/25YA
<Tooniis[m]> <steev "Tooniis: what does that look lik"> nothing on dmesg
<Tooniis[m]> it just does nothing
<steev> ahh, okay.
<steev> you mentioned ssr notifications and i remembered my dmesg output complaining about ssr
<steev> Tooniis[m]: well, for what its worth, i pulled in those two patches here to my 5.13 tree and that does get rid of my null pointer
cmeerw has quit [Ping timeout: 480 seconds]