From: "Alvin Šipraga" <alvin.sipraga@analog.com>
To: Mieczyslaw Nalewaj <namiltd@yahoo.com>,
Johan Alvarado <contact@c127.dev>
Cc: linusw@kernel.org, andrew@lunn.ch, 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:46:31 +0100 [thread overview]
Message-ID: <au3xgDo0y17pbvEA@analog.com> (raw)
In-Reply-To: <b9778e4c-fe81-4305-b764-8ebf4ff8add6@yahoo.com>
On Fri, Nov 06, 2026 at 03:56:10PM +0100, Mieczyslaw Nalewaj wrote:
> Subject: Re: [PATCH net-next v7 08/10] net: dsa: realtek: rtl8365mb: re-latch the family D SerDes
>
> On Fri, Nov 06, 2026 at 03:28:30PM +0100, Alvin Šipraga wrote:
> > I don't understand this at all, should it be obvious what you mean by
> > "edge" and "latch" here? I would assume you are talking about interrupts
> > but it's not clear.
>
> Sorry, the wording was unclear, and no interrupts are involved. "Edge"
> is the SDS_MISC mode field changing from DISABLE to HSGMII, and "latch"
> is the SerDes receiver locking onto the incoming signal. It locks on
> that change, not on the value, and only if the far end is already
> sending.
>
> > Is the shortcoming/issue you are addressing one of DSA when a SerDes is
> > used in the CPU link? Or is it rather some hardware oddity?
>
> As far as I can tell, a hardware oddity. If the change happens before
> the far-end MAC is up, the receiver does not lock and nothing retries.
> Both ends then report 2.5Gbps/Full while no frames pass.
>
> > Can we use interrupts instead of polling?
>
> I do not know. I have no datasheet, and the vendor API I have does not
> expose an interrupt for the SerDes state.
>
> > I'm basically wondering here if this is not something that DSA or
> > phylink could help with?
>
> pcs_config() and pcs_link_up() run seconds before the far-end MAC
> starts, and phylink never calls rtl8365mb_pcs_get_state() for this
> port: mb->pcs.poll only arms polling for in-band links, and the CPU
> port is a fixed link. The only event I found that tells the driver the
> far end is starting is the CPU conduit coming up, reported through
> ->conduit_state_change().
OK. Unfortunately I'm a bit out of my depth here, not having worked with
SerDes links before. My gut tells me this patch is overkill. I hope
somebody else with more experience can chip in. Adding Johan to the
mail, as he added SGMII support and might have some opinters.
Kind regards,
Alvin
next prev parent reply other threads:[~2026-11-06 15:47 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 [this message]
2026-11-06 15:49 ` Andrew Lunn
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=au3xgDo0y17pbvEA@analog.com \
--to=alvin.sipraga@analog.com \
--cc=andrew@lunn.ch \
--cc=contact@c127.dev \
--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®