Hi Rob, On Tue, 30 Jul 2024 13:36:35 -0600 Rob Herring <robh@xxxxxxxxxx> wrote: ... > > + > > +patternProperties: > > + '^channel@([0-9]|[1-5][0-9]|6[0-3])$': > > Unit-addresses are typically in hex. I thought it was more related to the reg value. In our case, the reg value is just the channel number from 0 to 63. Should I change to a hex format? ... > > + > > + compatible: > > compatible goes first in the list. Yes, I will move it to the first position in the next iteration. > > > + items: > > + - enum: > > + - fsl,mpc8321-ucc-qmc-hdlc > > + - const: fsl,qe-ucc-qmc-hdlc > > + - const: fsl,qmc-hdlc > > Really need 3 compatibles? > The QMC is handled by the QUICC Engine (QE) companion. The QE can be available in several SOCs. The first one is the exact device (SOC MPC8321 + UCC QMC) The second one references the QUICC Engine family instead of the SOC. The last one is the fallback one just referencing the QMC. This one matches all QMCs whatever the SOC and the companion. On QMC handled by the CPM1 companion, we have these tree compatibles: - fsl,mpc885-scc-qmc-hdlc or fsl,mpc866-scc-qmc-hdlc - fsl,cpm1-scc-qmc-hdlc - fsl,qmc-hdlc IMHO, I think it makes sense to have the 3 compatibles. Best regards, Hervé
