From: Andrew Lunn <andrew@lunn.ch>
To: "Alvin Šipraga" <alvin.sipraga@analog.com>
Cc: Mieczyslaw Nalewaj <namiltd@yahoo.com>,
linusw@kernel.org, olteanv@gmail.com, kuba@kernel.org,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
linux@armlinux.org.uk, luizluca@gmail.com,
maxime.chevallier@bootlin.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v7 08/10] net: dsa: realtek: rtl8365mb: re-latch the family D SerDes
Date: Fri, 6 Nov 2026 16:49:43 +0100 [thread overview]
Message-ID: <c5881bc0-8773-434a-8aad-2346a58bb146@lunn.ch> (raw)
In-Reply-To: <au3hdMxLSilNxhnK@analog.com>
> > pcs_config() runs seconds before the far-end MAC even starts
> > configuring, so a single edge driven from there is not enough: the
> > receiver has nothing to latch onto yet. Neither is pcs_link_up(),
> > which is seconds early for the same reason. phylink does not help
> > either - it never calls rtl8365mb_pcs_get_state() for this port in
> > the first place, since mb->pcs.poll only arms phylink's own poll for
> > in-band links, and this CPU port is a fixed link.
Sorry, not been following this patch series.
One thing which might help here. Russell once said it should be
possible to use phylink with pcs to pcs links, rather than use
fixed-link. You then get all the phylink machinery, which might
trigger the pcs negotiation and get your link up?
I don't know of any board which actually does this, so i've no idea if
it really does work.
Andrew
next prev parent reply other threads:[~2026-11-06 15:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3bf4dd70-9771-497b-8c27-e925e0ef81eb.ref@yahoo.com>
2026-11-02 14:34 ` [PATCH net-next v7 0/10] net: dsa: realtek: rtl8365mb: add support for RTL8367S-VB Mieczyslaw Nalewaj
2026-11-02 14:36 ` [PATCH net-next v7 01/10] dt-bindings: net: dsa: realtek: add RTL8367S-VB Mieczyslaw Nalewaj
2026-11-02 14:37 ` [PATCH net-next v7 02/10] net: dsa: realtek: rtl8365mb: add chip family infrastructure Mieczyslaw Nalewaj
2026-11-02 14:38 ` [PATCH net-next v7 03/10] net: dsa: realtek: rtl8365mb: set speed for family D Mieczyslaw Nalewaj
2026-11-04 12:20 ` Alvin Šipraga
2026-11-02 14:39 ` [PATCH net-next v7 04/10] net: dsa: realtek: rtl8365mb: set RGMII mode " Mieczyslaw Nalewaj
2026-11-04 12:39 ` Alvin Šipraga
2026-11-05 7:56 ` Mieczyslaw Nalewaj
2026-11-05 12:39 ` Alvin Šipraga
2026-11-05 15:27 ` Mieczyslaw Nalewaj
2026-11-06 13:50 ` Alvin Šipraga
2026-11-06 14:56 ` Mieczyslaw Nalewaj
2026-11-06 15:15 ` Alvin Šipraga
2026-11-06 16:43 ` Mieczyslaw Nalewaj
2026-11-06 15:11 ` Mieczyslaw Nalewaj
2026-11-02 14:40 ` [PATCH net-next v7 05/10] net: dsa: realtek: rtl8365mb: set and get vlan 4k " Mieczyslaw Nalewaj
2026-11-04 12:45 ` Alvin Šipraga
2026-11-02 14:41 ` [PATCH net-next v7 06/10] net: dsa: realtek: rtl8365mb: use raw VID for PVID on " Mieczyslaw Nalewaj
2026-11-02 14:42 ` [PATCH net-next v7 07/10] net: dsa: realtek: rtl8365mb: add family D SDS13 PCS support Mieczyslaw Nalewaj
2026-11-02 14:43 ` [PATCH net-next v7 08/10] net: dsa: realtek: rtl8365mb: re-latch the family D SerDes Mieczyslaw Nalewaj
2026-11-04 12:57 ` Alvin Šipraga
2026-11-05 7:18 ` Mieczyslaw Nalewaj
2026-11-05 8:52 ` Alvin Šipraga
2026-11-05 10:24 ` Mieczyslaw Nalewaj
2026-11-05 12:09 ` Alvin Šipraga
2026-11-06 14:28 ` Alvin Šipraga
2026-11-06 14:56 ` Mieczyslaw Nalewaj
2026-11-06 15:46 ` Alvin Šipraga
2026-11-06 15:49 ` Andrew Lunn [this message]
2026-11-02 14:44 ` [PATCH net-next v7 09/10] net: dsa: realtek: rtl8365mb: make L2/LUT access work on family D Mieczyslaw Nalewaj
2026-11-03 15:36 ` Alvin Šipraga
2026-11-03 16:44 ` Mieczyslaw Nalewaj
2026-11-02 14:45 ` [PATCH net-next v7 10/10] net: dsa: realtek: rtl8365mb: add support for RTL8367S-VB Mieczyslaw Nalewaj
2026-11-03 22:52 ` Alvin Šipraga
2026-11-03 23:41 ` Mieczyslaw Nalewaj
2026-11-04 9:40 ` Mieczyslaw Nalewaj
2026-11-04 13:14 ` Alvin Šipraga
2026-11-04 16:37 ` Mieczyslaw Nalewaj
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=c5881bc0-8773-434a-8aad-2346a58bb146@lunn.ch \
--to=andrew@lunn.ch \
--cc=alvin.sipraga@analog.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=luizluca@gmail.com \
--cc=maxime.chevallier@bootlin.com \
--cc=namiltd@yahoo.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--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®