ChanServ changed the topic of #linux-msm to:
<lumag> strongtz[m], Yes, I had to retract v2. I think I'm done with v3, which not seems to work. I want to run more tests and post it, likely tomorrow.
shawnguo has joined #linux-msm
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
danylo has quit [Ping timeout: 480 seconds]
danylo has joined #linux-msm
<steev> lumag: i'm excited to see v3, i saw you post v2, but when i was about to apply it i saw your own reply saying a v3 was coming
marvin24 has joined #linux-msm
marvin24_ has quit [Ping timeout: 480 seconds]
junari has quit [Remote host closed the connection]
jhovold has joined #linux-msm
sumits has joined #linux-msm
mripard has joined #linux-msm
pespin has joined #linux-msm
<aka_[m]> lumag: i feel defeated by schema... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/xkgUjbtolydSIpKQgdmULEgA>)
<lumag> aka_[m], you don't even need oneOf
<lumag> properties: compatible: items: - const: qcom,adreno-306.0 - const: qcom,adreno
<lumag> If you have more than one compatible SoC, you'd need to replace first - const with -enum
<aka_[m]> lumag: still im somehow failing it keeps querying for other compats
<aka_[m]> might that come from:... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/hNaRBWHcpnHjbNrkAVwPnrBf>)
<lumag> aka_[m], might be
<aka_[m]> removed and still its same
<lumag> aka_[m], let me check
<lumag> krzk, could you suggest something? I have checked, this happens because several schema files declare qcom,adreno as a second compatible string.
<aka_[m]> lumag: probably we could do later -if and then redefine pickup list
<aka_[m]> but plan was to remove ifs
<aka_[m]> as you say it seems there is issue when more than one yaml define same compat
<krzk> lumag: how can I help?
<lumag> krzk, is it possible to have two schema files, each of them listing qcom,adreno as a fallback?
<krzk> if wrong schema is selected, usually you need custom select:
<krzk> See arm,primecell as typical example
<lumag> krzk, thanks!
<lumag> aka_[m], ^^
<aka_[m]> i tried select before too
<aka_[m]> still not sure about placement of refs
<aka_[m]> linked yaml have it under allOf:
<aka_[m]> would it look like this?
<aka_[m]> im very not getting "-" part
<aka_[m]> sometimes there are 4 spaces after enum and sometimes 2
<krzk> aka_[m]: there are never different amout of spaces after enum...
<krzk> although depends from where do you count...
<krzk> aka_[m]: the select looks ok
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
jessica_240 has joined #linux-msm
jessica_240 is now known as jessica_24
jhovold has quit [Ping timeout: 480 seconds]
<lumag> For pd-mapper. I'd really love some feedback from sm6350 / sm6375 owners. Especially the JSN files would be handy.
<aka_[m]> Luca Weiss:
<aka_[m]> JIaxyga: maybe?
<JIaxyga[m]> aka_[m]: Hah, msm8953, sm7150 and sm8475 only
<JIaxyga[m]> konradybcio: I think you had sm6350
<konradybcio> correct, very far away
<JIaxyga[m]> konradybcio: btw you are a little late with the interconnect review. It was applied, but Rob didnt leave a message
<JIaxyga[m]> Im still confused. Adrian was able to get a working SSC on sm7150 with some hacks. This should probably work for sm6350/sm7225 as well
<JIaxyga[m]> I also wrote a simple fuel gauge driver based on qcom-fg from tooniis for qg. For now this only works based on the current voltage. So it is only suitable for community forks
<konradybcio> is qg very far away from pmic4/pmic5?
<konradybcio> i.e. pmi8996/8/friends
<JIaxyga[m]> konradybcio: Pmic3/4 afair
<JIaxyga[m]> pm6150/pm7250b
<z3ntu> lumag: Just the .jsn files? For FP4 they're here https://github.com/FairBlobs/FP4-firmware/
<z3ntu> FP4 is sm7225 (=sm6350)
pespin has quit [Remote host closed the connection]
<lumag> z3ntu, thank you!