All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <vladimir.oltean@nxp.com>
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
Subject: Re: [PATCH 0/3] phy: lynx: add support for downstream retimer PHYs
Date: Thu, 19 Nov 2026 11:25:01 +0200	[thread overview]
Message-ID: <av6-ROH48bJTSp04@skbuf> (raw)
In-Reply-To: <20261118163134.2149894-1-ioana.ciornei@nxp.com>

On Wed, Nov 18, 2026 at 06:31:31PM +0200, Ioana Ciornei wrote:
> One thing to note here is that the forwarding code is kept rather
> grouped in phy-fsl-lynx-core.c rather than in the individual Lynx10G and
> Lynx28G drivers so that in the future, if necessary, it can be moved
> internally into the Generic PHY framework. This leads to the consequence
> that the actual phy_ops with which the PHY is created cannot be const
> since the .owner field needs to be copied from the structure received
> from the actual PHY driver.

Have you evaluated the possibility to land retimer support in the core
PHY framework directly? What would the obstacles be?

WARNING: multiple messages have this Message-ID (diff)
From: Vladimir Oltean <vladimir.oltean@nxp.com>
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
Subject: Re: [PATCH 0/3] phy: lynx: add support for downstream retimer PHYs
Date: Thu, 19 Nov 2026 11:25:01 +0200	[thread overview]
Message-ID: <av6-ROH48bJTSp04@skbuf> (raw)
In-Reply-To: <20261118163134.2149894-1-ioana.ciornei@nxp.com>

On Wed, Nov 18, 2026 at 06:31:31PM +0200, Ioana Ciornei wrote:
> One thing to note here is that the forwarding code is kept rather
> grouped in phy-fsl-lynx-core.c rather than in the individual Lynx10G and
> Lynx28G drivers so that in the future, if necessary, it can be moved
> internally into the Generic PHY framework. This leads to the consequence
> that the actual phy_ops with which the PHY is created cannot be const
> since the .owner field needs to be copied from the structure received
> from the actual PHY driver.

Have you evaluated the possibility to land retimer support in the core
PHY framework directly? What would the obstacles be?

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

  parent reply	other threads:[~2026-11-19  9:25 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 ` Vladimir Oltean [this message]
2026-11-19  9:25   ` [PATCH 0/3] phy: lynx: add support for downstream retimer PHYs Vladimir Oltean
2026-11-19 16:15   ` Ioana Ciornei
2026-11-19 16:15     ` Ioana Ciornei
2026-11-19 15:57 ` Vincent Jardin
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=av6-ROH48bJTSp04@skbuf \
    --to=vladimir.oltean@nxp.com \
    --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 \
    /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.