On 19/08/2022 16:08, Krzysztof Kozlowski wrote: > On 19/08/2022 15:58, Martin Povišer wrote: >> >>> On 19. 8. 2022, at 14:54, Martin Povišer <povik+lin@xxxxxxxxxxx> wrote: >>> >>> Add binding schema for MCA I2S transceiver found on Apple M1 and other >>> chips. >>> >>> Signed-off-by: Martin Povišer <povik+lin@xxxxxxxxxxx> >>> --- >>> .../devicetree/bindings/sound/apple,mca.yaml | 131 ++++++++++++++++++ >>> 1 file changed, 131 insertions(+) >>> create mode 100644 Documentation/devicetree/bindings/sound/apple,mca.yaml >>> >>> diff --git a/Documentation/devicetree/bindings/sound/apple,mca.yaml b/Documentation/devicetree/bindings/sound/apple,mca.yaml >>> new file mode 100644 >>> index 000000000000..7b4f348c2be3 >>> --- /dev/null >>> +++ b/Documentation/devicetree/bindings/sound/apple,mca.yaml >>> @@ -0,0 +1,131 @@ >> >> >>> +properties: >>> + compatible: >>> + items: >>> + - enum: >>> + - apple,t8103-mca >>> + - apple,t6000-mca >> >> Since it was brought up last time but I didn’t respond: the >> nonalphabetical order is as the chips were introduced (and >> matches other schemas). > > Sure, just keep that order for future compatibles as well - so always > put them according to verifiable time of market introduction... > > This is very poor reason, instead of alphabetical order. Even worse > reason is repeating wrong pattern just because someone else did it. Ah, and the alphabetical order has clear advantage - reduces conflicts. "Time" has clear disadvantage - increases conflicts. So switch to alphabetical order. Best regards, Krzysztof
