ChanServ changed the topic of #linux-msm to:
<shawnguo> aka_[m], yeah, I am
Daanct12 has joined #linux-msm
<bamse> rawoul: and you had a problem with an MDSS clock, which would imply that some parent isn't ticking properly...and if that parent is part of MDSS, it probably need MDSS_GDSC to be on, to be powered
<bamse> Mis012[m]: if, like many other platforms, MDSS_GDSC is powered by VDDCX, then that should be modelled such that MDSS_GDSC is a subdomain of the VDDCX power-domain, doing that will result in requests on the GDSC propagating up to the VDDCX as necessary
<bamse> Mis012[m]: but that's a rather recent thing we've been working on, so that's not going to be in place for 8998
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #linux-msm
<aka_[m]> shawnguo: I seen you were working on 8939 stuff, from what i see cci also uses 200mhz as safe clock, do you have any patch to set custom divider inside apcs-msm8916.c?
<aka_[m]> Rn it sets static 4
<shawnguo> aka_[m], I would point you to bryanodonoghue who is still working on 8939 recently
<aka_[m]> Ok, thanks.
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
<bryanodonoghue> aka_[m] Jun Nie and Leo Yan have done a whole bunch of CPR enabling work - including some CPR fuse settings for the CCI on 4.19 which we are actively working to release asap
<bryanodonoghue> I did a very quick pass at forward porting it to 5.x to release upstream but it didn't "just work" straight away so I dropped it
<bryanodonoghue> so we do have cpr code for the cci bus which testing in the wild has shown to be important to have
<bryanodonoghue> hope to publish something really relatively soon on 4.19
<bryanodonoghue> CPR feels like a big enough topic to separate out from the inital 8939 dtsi though
jhovold has joined #linux-msm
Danct12 has quit [Ping timeout: 480 seconds]
Danct12 has joined #linux-msm
Danct12 has quit [Ping timeout: 480 seconds]
Daanct12 has quit [Remote host closed the connection]
Danct12 has joined #linux-msm
<aka_[m]> Nice.
<aka_[m]> Tho cpr is hard to understand if you don't know how it works.
<aka_[m]> I had quite a lot of issues understanding 8976 dts part for it.
Danct12 has quit [Quit: Leaving]
pespin has joined #linux-msm
sergi has joined #linux-msm
Danct12 has joined #linux-msm
sergi has quit [Ping timeout: 480 seconds]
<aka_[m]> Do any of you qcom folks can say what is main difference between HF pll and HF2 one?
<aka_[m]> HF one is used on qcs404
<minecrell> aka_[m]: I don't think you should care about 200 vs 400mhz safe frequency unless it really noticeably breaks something. This might be just a random choice
<minecrell> The main important thing is that the CPU is temporarily switched from the PLL while it's being reconfigured
<minecrell> The frequency you use for that probably doesn't matter too much imho
<aka_[m]> well when it switches it to gpll0 it also set divider for this gpll0 source
<aka_[m]> maybe its about doing it on low enought freq so we won't break something if our CX is like low_svs or something
pespin has quit [Remote host closed the connection]
<minecrell> aka_[m]: the PLL provides the higher frequencies, so if you're reconfiguring it because you want to switch from $high-freq to $some-other-high-freq then CX should be already voted for $high-freq. And this should be more than sufficient for the $low-freqs of GPLL
<minecrell> just imho again though
<abhinav__> rawoul great to see the dpu support on 8998 and your WIP tree. Looking fwd to reviewing that on the list.
<abhinav__> not an expert on the power domains either
<abhinav__> but if that has been ruled out
<abhinav__> as the issue
<abhinav__> my next clue to you would be to look into the PLL driver
<abhinav__> for the rate you are setting
jhovold has quit [Ping timeout: 480 seconds]