I would agree with this if your argument below is true (see below).- in-band status is an implementation delail, and it isSo by specifying "autoneg", you are not specific about the kind of
specific to a particular protocols. If you request the
in-band status for some protocol that doesn't support
it, perhaps you should get -EINVAL, because such a
config makes no sense. With autonegotiation, the rules
are not that strict: it can be "unimplemented", which doesn't
necessary mean nonsense in the config.
auto-negotiation protocol available, which is precisely my point: you
need to go down to that level of detail for this to be useful. So maybe
something like:
autoneg = "in-band-status" would actually be a better thing in terms of
description because then you would tell what can be made available/working?
"something else" is a big question here.- autonegotiation is a wider term, and may be implementedBut arguably, there could be another auto-negotiation method, which is
by some other means than the in-band status (which is
probably impossible for a fixed-link though).
- In the terms that the driver uses, it is autonegotiation, eg
MVNETA_GMAC_AUTONEG_CONFIG. And when you go down
the implementation details, you see MVNETA_GMAC_INBAND_AN_ENABLE,
which is just one AN bit of many.
not in-band status related, which means that you would need a way to
distinguish between using in-band status, or using something else or
nothing, would not you?