On 8/29/2024 12:42 AM, Krzysztof Kozlowski wrote: > On Wed, Aug 28, 2024 at 01:37:15PM -0700, Nikunj Kela wrote: >> Add "qcom,sa8255p-geni-se-qup" compatible for representing QUP on >> SA8255p. >> >> Clocks are being managed by the firmware VM and not required on >> SA8255p Linux VM hence removing it from required list. >> >> CC: Praveen Talari <quic_ptalari@xxxxxxxxxxx> >> Signed-off-by: Nikunj Kela <quic_nkela@xxxxxxxxxxx> >> --- >> .../bindings/soc/qcom/qcom,geni-se.yaml | 47 +++++++++++++++++-- >> 1 file changed, 43 insertions(+), 4 deletions(-) >> >> diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml b/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml >> index 7b031ef09669..40e3a3e045da 100644 >> --- a/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml >> +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml >> @@ -22,17 +22,16 @@ properties: >> enum: >> - qcom,geni-se-qup >> - qcom,geni-se-i2c-master-hub >> + - qcom,sa8255p-geni-se-qup > Same problems. If you decide to use generic compatibles, it means it > covers all devices. Otherwise it does not make any sense. Hi Krzysztof, SA8255p platform is not compatible with generic ones. At the time generic compatibles were added, no one thought of such platform will appear in future. Please advise what should we do in this case? Thanks, -Nikunj >> >> reg: >> description: QUP wrapper common register address and length. >> maxItems: 1 >> >> clock-names: >> - minItems: 1 > Huh? > > Best regards, > Krzysztof >