public inbox for linux-phy@lists.infradead.org
 help / color / mirror / Atom feed
From: Tanjeff Moos <Tanjeff.Moos@westermo.com>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Sean Anderson <sean.anderson@seco.com>,
	"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>
Subject: Re: Lynx 10G SerDes Driver on my kernel
Date: Thu, 5 Feb 2026 17:47:12 +0100	[thread overview]
Message-ID: <1e508f4e-d9a7-4e06-8308-e2d67099e927@westermo.com> (raw)
In-Reply-To: <20251205124423.gddjli3jtqlvkrkv@skbuf>

Hello Vladimir,

I wish you a great year 2026!

Meanwhile I ported some of your code and I got my networking partially 
running. Details follow, but first I have a question.


== Question ==

The lynx-10g driver disables the managed lanes in lynx_10g_init(), and 
they are never enabled afterwards. Probably I didn't port the associated 
code, but can't find where it is.

I modified lynx_10g_init() to leave the lane enabled, which solves the 
problem, but this is a dirty hack.

Question: How is the lane supposed to be enabled?


== Status of my work ==

In case you are interested I provide some details here.

I ported only part of your code (tag lf-6.12.49-2.2.0), mainly the 
lynx-10g driver plus some changes you did in pcs-lynx.c, phy-core.c, 
guts.c, the dpaa drivers plus their associated header files. I 
deliberately omitted code dealing with c72 autonegotiation (for 
backplane), as I don't need it. I'm still working with kernel 6.6.119 
plus OpenWRT patches and cannot easily upgrade.

So far, I have a 2.5 GbE PHY and can run the following modes:
- 100M : SGMII
- 1G:    SGMII
- 2.5G:  2500BaseX

Switching forth and back the modes works seamlessly (with my dirty hack 
to power on the lane!). But I didn't test RCW rewriting as it is not 
needed in this scenario.

Kind regards so far, Tanjeff



-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

  parent reply	other threads:[~2026-02-05 16:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02 11:12 Lynx 10G SerDes Driver on my kernel Tanjeff Moos
2025-12-02 16:29 ` Vladimir Oltean
2025-12-03 11:41   ` Tanjeff Moos
2025-12-03 12:26     ` Vladimir Oltean
2025-12-03 16:25       ` Tanjeff Moos
2025-12-03 18:00         ` Vladimir Oltean
2025-12-04 19:01           ` Tanjeff Moos
2025-12-04 19:34             ` Vladimir Oltean
2025-12-05 11:38               ` Tanjeff Moos
2025-12-05 12:44                 ` Vladimir Oltean
2025-12-08 16:50                   ` Tanjeff Moos
2026-02-05 16:47                   ` Tanjeff Moos [this message]
2026-02-08 13:42                     ` Vladimir Oltean
2026-02-12  8:30                       ` Tanjeff Moos

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=1e508f4e-d9a7-4e06-8308-e2d67099e927@westermo.com \
    --to=tanjeff.moos@westermo.com \
    --cc=linux-phy@lists.infradead.org \
    --cc=sean.anderson@seco.com \
    --cc=vladimir.oltean@nxp.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