> +properties:
> + compatible:
> + enum:
> + - ethernet-phy-id0180.dc40
> + - ethernet-phy-id0180.dd00
> + - ethernet-phy-id0180.dc80
> + - ethernet-phy-id001b.b010
> + - ethernet-phy-id001b.b031
This shows the issues with using a compatible. The driver has:
#define PHY_ID_TJA_1120 0x001BB031
PHY_ID_MATCH_MODEL(PHY_ID_TJA_1120),
which means the lowest nibble is ignored. The driver will quite happy
also probe for hardware using 001b.b030, 001b.b032, 001b.b033,
... 001b.b03f
Given you are inside NXP, do any of these exist? Was 001b.b030 too
broken it never left the QA lab? Are there any hardware issues which
might result in a new silicon stepping?
Does ethernet-phy-id0180.dc41 exist? etc.
Andrew
