From: Andrew Lunn <andrew@lunn.ch>
To: Coia Prant <coiaprant@gmail.com>
Cc: Maxime Chevallier <maxime.chevallier@bootlin.com>,
Jakub Kicinski <kuba@kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: pcs: xpcs-rk: limit advertised interfaces
Date: Tue, 3 Nov 2026 14:09:09 +0100 [thread overview]
Message-ID: <f554dcc0-14ea-4721-9517-dc0337c47426@lunn.ch> (raw)
In-Reply-To: <27E466B0-72FD-47BA-B952-68BF4A817A04@gmail.com>
> >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
next prev parent reply other threads:[~2026-11-03 13:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 9:49 Coia Prant
2026-10-29 9:56 ` netdev-bot+sinfo
2026-10-29 10:23 ` Coia Prant
2026-10-30 20:44 ` Maxime Chevallier
2026-10-30 21:08 ` Coia Prant
2026-11-03 2:54 ` Andrew Lunn
2026-11-03 6:11 ` Coia Prant
2026-11-03 13:09 ` Andrew Lunn [this message]
2026-11-03 14:54 ` Coia Prant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f554dcc0-14ea-4721-9517-dc0337c47426@lunn.ch \
--to=andrew@lunn.ch \
--cc=coiaprant@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®