Hi Chester and Linus,

quoted

quoted

If you have the compatible, surely you know these indexes from that 
compatible string?

The nxp,pins property is more like a common language that both kernel 
and u-boot can share with. Of course hardcoding indexes can be 
achieved as well but that also means the index matrices in both kernel 
driver and u-boot driver must be revised and synchronized if new 
boards may have different reg and nxp,pins.

Is it new *BOARDS* that need a new table really or new *SOC:s*?

I was under the impression that this is per-soc and then it can be derived from the compatible string and should be in the driver.

Yes, the "nxp,pins" property only depends on the SoC. It will not change from board to board(boards using the same SoC). It can be derived from the compatible string.

Best regards,
Andrei
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel