<macromorgan>
mmind00: I'm updating some YAML files for the rockchip rk808 series of PMICs... did you say that I needed to support what is in mainline today even if it doesn't match the datasheets?
<macromorgan>
best example is the RK808... the datasheet says it only goes up to VCC12, but I have some devicetrees with VCC13 & VCC14 (like the pinebook pro).
<robmur01>
and we want schema to catch errors like that :)
<robmur01>
those are nonsense, not part of the current binding, and not consumed either
<robmur01>
if there's anything not in the current rk808.txt binding that *is* being consumed by a driver, that's more of a judgement call
<macromorgan>
it's not being consumed by a driver
<macromorgan>
nor is it on the schematic
<macromorgan>
also what does this mean: clock-output-names: ['xin32k'] is too short
<macromorgan>
(I'm trying to lint and test my yaml files and getting that error along with the vcc13 and vcc14 issues for the rk809)
<macromorgan>
also I think I have the battery driver ready for the rk817, but it will need a lot of testing and eyes on it from someone who knows more than I do...
<robmur01>
guessing you've defined clock-output-names as a list of 2 items? That should make it expect 2 unless you explicitly say "minItems: 1", which in that case seems right since it's legitimate for boards to use 0, 1, or 2 of the clock outputs
<macromorgan>
okay thanks
<macromorgan>
clock-output-names is set to maxItems 2
<macromorgan>
I'll set minItems 1 and see if that fixes it
<macromorgan>
that fixed it, now I can successfully complete the tests for all yaml files except the rk809, which is failing for a legitimate reason (the devicetrees are wrong, NOT the YAML file!)
<macromorgan>
I'm going to upstream this now, thank you
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
camus has quit [Remote host closed the connection]