On Wed, Oct 21, 2020 at 5:09 PM Andrew Lunn <and...@lunn.ch> wrote:
>
> > Signed-off-by: Alexandru Ardelean <alexandru.ardel...@analog.com>
>
removed my typo-ed email
> Hi Alexandru
>
> Overall, this looks good.
>
> > +static int adin_cable_test_report_trans(int result)
> > +{
> > + int mask;
> > +
> > + if (result & ADIN1300_CDIAG_RSLT_GOOD)
> > + return ETHTOOL_A_CABLE_RESULT_CODE_OK;
> > + if (result & ADIN1300_CDIAG_RSLT_OPEN)
> > + return ETHTOOL_A_CABLE_RESULT_CODE_OPEN;
> > +
> > + /* short with other pairs */
> > + mask = ADIN1300_CDIAG_RSLT_XSHRT3 |
> > + ADIN1300_CDIAG_RSLT_XSHRT2 |
> > + ADIN1300_CDIAG_RSLT_XSHRT1;
> > + if (result & mask)
> > + return ETHTOOL_A_CABLE_RESULT_CODE_CROSS_SHORT;
>
> The nice thing about the netlink API is that it is extendable without
> breaking backwards compatibility. You could if you want add another
> attribute, indicating what pair it is shorted to.
That would be an idea.
Actually, I'd also be interested [for this PHY], to report a
"significance impedance" detection, which is similar to the
short-detection that is already done.
At first, this report would sound like it could be interesting; but
feel free to disagree with me.
And there's also some "busy" indicator; as-in "unknown activity during
diagnostics"; to-be-honest, I don't know what this is yet.
I'd need to check, but odds are that I'd need to also ask about it.
So, I don't think I'd implement this.
>
> Andrew
