[PATCH net] net: pcs: xpcs-rk: limit advertised interfaces

[Coia Prant]

Andrew Lunn <andrew at lunn.ch> 于2026年11月3日周二 21:09写道：
>
> > >Are there any registers which describe how the PCS was configured at
> > >syntheses time?
> > >
> > >     Andrew
> >
> > Hi Andrew,
> >
> > Yes, looking at the `xpcs_identity` code, the core does probe different
> > MMDs to get the rough type: PMA/PMD MMD for C73 and VEND2 MMD for C37.
> >
> > However, even if we determine it's a C37 or C73 block, that only gives
> > us the rough family, not the exact feature set.
>
> You might want to try reaching out to Synopsys. There are sometimes
> feature bits in VEND1/2 which list the exact configuration
> synthesised.  And since it is a core part of the licensed IP, it
> should be safe to trust it, independent of the platform it has been
> integrated into.
>
>       Andrew

Hi Andrew,

Thanks for the suggestion. I looked into reaching out to Synopsys, but
it seems the original maintainer is no longer active in mainline.

I also tried registering on the Synopsys website to look for the
databook, but the registration was rejected with:

  "We couldn't find your email domain in our records. Please verify
   your email address and try again."

It seems they only accept corporate emails or existing NDA holders.
Without the databook, guessing the VEND1/VEND2 feature bit layout is
risky, as it could lead to silent misdetection of capabilities.

Since Wangxun (Jiawen Wu) and NXP (Clark Wang) already have their own
XPCS PMA configurations and quirks in the tree, they must have access
to the vendor integration manuals that document the VEND1/VEND2 layout.

Do you think it would be appropriate if I post a query to the netdev
list (CCing them) asking if they can share the feature bit definitions?
Or is there a better channel for this kind of vendor coordination?

For this v3 patch, the glue-level intersection remains the safe
interim solution.

Coia