Re: [PATCH 1/3] dt-bindings: firmware: scm: Refactor compatibles and clocks

2018-08-30 Thread Stephen Boyd
Quoting Bjorn Andersson (2018-08-29 16:15:03) > When the binding was written all "future" platforms required three > clocks, so the default compatible (qcom,scm) was defined to require > this. But as history shows all "future" platforms actually lack required > clocks. Given how the binding is

Re: [PATCH 1/3] dt-bindings: firmware: scm: Refactor compatibles and clocks

2018-08-30 Thread Stephen Boyd
Quoting Bjorn Andersson (2018-08-29 16:15:03) > When the binding was written all "future" platforms required three > clocks, so the default compatible (qcom,scm) was defined to require > this. But as history shows all "future" platforms actually lack required > clocks. Given how the binding is

[PATCH 1/3] dt-bindings: firmware: scm: Refactor compatibles and clocks

2018-08-29 Thread Bjorn Andersson
When the binding was written all "future" platforms required three clocks, so the default compatible (qcom,scm) was defined to require this. But as history shows all "future" platforms actually lack required clocks. Given how the binding is written these compatibles have to be added as an

[PATCH 1/3] dt-bindings: firmware: scm: Refactor compatibles and clocks

2018-08-29 Thread Bjorn Andersson
When the binding was written all "future" platforms required three clocks, so the default compatible (qcom,scm) was defined to require this. But as history shows all "future" platforms actually lack required clocks. Given how the binding is written these compatibles have to be added as an