<aka_[m]>
Dt-bindings+dt and in that way it cries about compatible being too long
<krzk>
qcom,adsp.yaml
<krzk>
aka_[m]: use fallback if it makes sense (devices are compatible)
<aka_[m]>
But what about checker complaining?
<aka_[m]>
Aren't I supposed to be sure there is no warnings/errors
<konradybcio>
aka_: I meant to say: if you choose to use e.g. msm8996 as fallback for e.g. msm1234, you need to do "qcom,msm1234-asdf", "qcom,msm8996-adsf"
<krzk>
aka_[m]: yes, you are supposed to. I don't understand the question.
<krzk>
bindings, DTS and drivers must match. You cannot add something in one palce and cause errors in other places...
<aka_[m]>
konradybcio: and then dt bindings check says 'compatible is too long'
<konradybcio>
aka_: did you define a new entry in bindings?
<aka_[m]>
Obv
<konradybcio>
can you show us your dfif?
<konradybcio>
diff*
<aka_[m]>
You have commits in repo I linked few msgs up
<aka_[m]>
And now I'm slowly heading to job so far from pc
<krzk>
aka_[m]: message suggests you did not define a list in the bindings
<konradybcio>
you need an entry like items: - const: new-compatible - const: old-compatible
<krzk>
the bindings say you have one compatible, but you want (as expressed in DTS) two compatibles, so you need to write it differently in the binidngs
<konradybcio>
fwiw items means "all of the following", enum means "one of the following"
<aka_[m]>
so if i want to go fallback only i need to modify schema more
<aka_[m]>
sad, i almos have no idea how it works but probably i need some nesting
<aka_[m]>
i guess i can take a look on others and copy&test
irungentoo has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
irungentoo has joined #linux-msm
<konradybcio>
Danct12: as I said, on this platform you need the interconnect driver
<Danct12>
oh that's a requirement now.. i see
<calebccff>
Marijn[m]: did some further digging, after the first DRM client starts I can "chvt 2" and get a single frame of TTY, but then no more vblank interrupts