Just omit the interrupt property if you don't want interrupts and
add it if you do.
How does that work together with "the device tree describes
the hardware and not the configuration". The interrupt line
is there, its just broken sometimes and thus it's disabled
by default for these PHY revisions/firmwares. With this
flag the user can say, "hey on this hardware it is not
relevant because we don't have shared interrupts or because
I know what I'm doing".
Yeah, that's a good question. In your case broken interrupts could be
understood the same as "not connected", so property not present. When
things are broken, you do not describe them fully in DTS for the
completeness of hardware description, right?
Specifically you can't do the following: Have the same device
tree and still being able to use it with a future PHY firmware
update/revision. Because according to your suggestion, this
won't have the interrupt property set. With this flag you can
have the following cases:
(1) the interrupt information is there and can be used in the
future by non-broken PHY revisions,
(2) broken PHYs will ignore the interrupt line
(3) except the system designer opts-in with this flag (because
maybe this is the only PHY on the interrupt line etc).
I am not sure if I understand the case. You want to have a DTS with
interrupts and "maxlinear,use-broken-interrupts", where the latter will
be ignored by some future firmware?
Isn't then the property not really correct? Broken for one firmware
on the same device, working for other firmware on the same device?
I would assume that in such cases you (or bootloader or overlay)
should patch the DTS...