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
<Tooniis[m]> well in any case its making converting the cpufreq-nvmem dt bindings to schema somewhat difficult
<Tooniis[m]> there isnt much overlap between it and the others
elroo_ has joined #linux-msm
<Tooniis[m]> yet it has enough overlap to make splitting it into a separate schema difficult
ahalaney has joined #linux-msm
ajhalaney[m] has joined #linux-msm
ahalaney has quit [Quit: Leaving]
ahalaney has joined #linux-msm
ahalaney has quit [Quit: Leaving]
flto has quit [Ping timeout: 480 seconds]
flto has joined #linux-msm
<DavidHeidelberg[m]> Tooniis: do you need some help with it?
<Tooniis[m]> David Heidelberg: Thanks. I think I got most things covered, but I still couldn't figure out a good way to make `required-opps` in OPPs a required property when there is a required power domain. I also couldn't find a way to make `opp-supported-hw` required when `nvmem-cells` is defined. I'm not sure if those things are even possible. In any case, this is what I've written so far:
<DavidHeidelberg[m]> Tooniis: heh, that's just thing I was wondering about for my schema yesterday
<DavidHeidelberg[m]> from browsing existing Documentation, `if: required:` could work, since it doesn't make other possible use
<DavidHeidelberg[m]> Tooniis: check `Documentation/devicetree/bindings/display/panel/sharp,lq101r1sx01.yaml`
<DavidHeidelberg[m]> `add check for required properties if link2 is present` (quote from commit message -> so it seems to do what we want, I'm going to test)
pevik_ has quit [Ping timeout: 480 seconds]
pevik_ has joined #linux-msm
pevik_ has quit []
pevik_ has joined #linux-msm
pevik_ has quit [Ping timeout: 480 seconds]