All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Jardin <vjardin@free.fr>
To: Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: Vinod Koul <vkoul@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	netdev@vger.kernel.org, Vladimir Oltean <vladimir.oltean@nxp.com>
Subject: Re: [PATCH 0/3] phy: lynx: add support for downstream retimer PHYs
Date: Thu, 19 Nov 2026 16:57:05 +0100	[thread overview]
Message-ID: <av8cUZ2F4_iw2fQV@L30177.local> (raw)
In-Reply-To: <20261118163134.2149894-1-ioana.ciornei@nxp.com>

Hi Ioana,

> This patch set adds support in the Lynx SerDes PHY drivers for
> retimer PHYs which can be found on the board downstream of the SerDes
> lane towards any connector such as an SFP cage.

It is a good idea, it can be used then to leverage other retimers
on those serdes too (like a ds250).

So, two questions:
 - in patch 3, a downstream PHY without .validate fails every mode of
the lane. Could it be stated in the binding or in a kernel doc ? A
minimal retimer driver would take the port down.

 - for 100G and 40G ports that are 4 lanes under one MAC, and the
Lynx 28G driver has no lane mode for them, so set_mode would never reach
their retimers. What's the plan ?

One more point: we need to be able to tune the equalization and run PRBS
on these chips from userspace. A driver that selects a channel and then
writes would race with such tools. The retimer driver
would have to deal with it. What could the proper design be ?

thank you,
  Vincent

WARNING: multiple messages have this Message-ID (diff)
From: Vincent Jardin <vjardin@free.fr>
To: Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: Vinod Koul <vkoul@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	netdev@vger.kernel.org, Vladimir Oltean <vladimir.oltean@nxp.com>
Subject: Re: [PATCH 0/3] phy: lynx: add support for downstream retimer PHYs
Date: Thu, 19 Nov 2026 16:57:05 +0100	[thread overview]
Message-ID: <av8cUZ2F4_iw2fQV@L30177.local> (raw)
In-Reply-To: <20261118163134.2149894-1-ioana.ciornei@nxp.com>

Hi Ioana,

> This patch set adds support in the Lynx SerDes PHY drivers for
> retimer PHYs which can be found on the board downstream of the SerDes
> lane towards any connector such as an SFP cage.

It is a good idea, it can be used then to leverage other retimers
on those serdes too (like a ds250).

So, two questions:
 - in patch 3, a downstream PHY without .validate fails every mode of
the lane. Could it be stated in the binding or in a kernel doc ? A
minimal retimer driver would take the port down.

 - for 100G and 40G ports that are 4 lanes under one MAC, and the
Lynx 28G driver has no lane mode for them, so set_mode would never reach
their retimers. What's the plan ?

One more point: we need to be able to tune the equalization and run PRBS
on these chips from userspace. A driver that selects a channel and then
writes would race with such tools. The retimer driver
would have to deal with it. What could the proper design be ?

thank you,
  Vincent

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

  parent reply	other threads:[~2026-11-19 15:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-18 16:31 [PATCH 0/3] phy: lynx: add support for downstream retimer PHYs Ioana Ciornei
2026-11-18 16:31 ` Ioana Ciornei
2026-11-18 16:31 ` [PATCH 1/3] dt-bindings: phy: lynx: allow downstream phys on the lane nodes Ioana Ciornei
2026-11-18 16:31   ` Ioana Ciornei
2026-11-18 16:31 ` [PATCH 2/3] phy: lynx: get the PHYs listed in " Ioana Ciornei
2026-11-18 16:31   ` Ioana Ciornei
2026-11-18 16:31 ` [PATCH 3/3] phy: lynx: forward the phy_ops to the downstream PHYs of a lane Ioana Ciornei
2026-11-18 16:31   ` Ioana Ciornei
2026-11-19  9:25 ` [PATCH 0/3] phy: lynx: add support for downstream retimer PHYs Vladimir Oltean
2026-11-19  9:25   ` Vladimir Oltean
2026-11-19 16:15   ` Ioana Ciornei
2026-11-19 16:15     ` Ioana Ciornei
2026-11-19 15:57 ` Vincent Jardin [this message]
2026-11-19 15:57   ` Vincent Jardin
2026-11-19 17:25   ` Ioana Ciornei
2026-11-19 17:25     ` Ioana Ciornei

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=av8cUZ2F4_iw2fQV@L30177.local \
    --to=vjardin@free.fr \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ioana.ciornei@nxp.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=mani@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=netdev@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=vkoul@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.