Linux-PHY Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: linux-phy@lists.infradead.org, Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Christophe Leroy <chleroy@kernel.org>,
	devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org,
	Ioana Ciornei <ioana.ciornei@nxp.com>,
	Vinod Koul <vkoul@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Tanjeff Moos <tanjeff.moos@westermo.com>,
	Michael Walle <mwalle@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>, Frank Li <Frank.Li@nxp.com>,
	linux-kernel@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v4 phy-next 0/9] RCW override for 10G Lynx dynamic protocol reconfiguration
Date: Thu, 30 Jul 2026 10:14:07 +0200	[thread overview]
Message-ID: <178539922189.574381.6258263697994334139.b4-ty@kernel.org> (raw)
In-Reply-To: <20260721231603.67865-1-vladimir.oltean@nxp.com>


On Wed, 22 Jul 2026 02:15:54 +0300, Vladimir Oltean wrote:
> Previous set "New Generic PHY driver for Lynx 10G SerDes":
> https://lore.kernel.org/linux-phy/20260610151952.2141019-1-vladimir.oltean@nxp.com/
> introduced the 10G Lynx SerDes driver with a reduced functionality set.
> Namely, only minor protocol changes are supported (1GbE <-> 2.5GbE).
> The major protocol changes need a procedure named RCW override,
> explained in more detail in commits 6/8 and 7/8.
> 
> [...]

Applied, thanks!

[1/9] soc: fsl: guts: perform fsl_guts_init() error teardown in reverse order of setup
      commit: c200e79a5e3a9af0ed368f2f60ecbe37c3077d48
[2/9] soc: fsl: guts: use a macro to encode the DCFG CCSR space
      commit: 77a46f8fa169b1c01940c4c12851dd4a07f8de4a
[3/9] soc: fsl: guts: add a global structure to hold state
      commit: 2c498f7254acf7ec0c0c589c0e42024ffdd6e81b
[4/9] soc: fsl: guts: add a central fsl_guts_read() function
      commit: 51749b225c21889e4c59c5850ec14c392b8d17b0
[5/9] soc: fsl: guts: make it easier to determine on which SoC we are running
      commit: 9ee864e5c28b30b97db03b9e94c1624484a46e30
[6/9] soc: fsl: guts: make fsl_soc_data available after fsl_guts_init()
      commit: 989c49a752850789eec8a79a68613210b11bc765
[7/9] dt-bindings: fsl: layerscape-dcfg: define DCFG_DCSR region
      commit: 086923eb1fef29995ffdf75cb7574dc947caf5e8
[8/9] soc: fsl: guts: implement the RCW override procedure
      commit: f1ab3e661b457937cc1cb975e9f2090f6b6de6d7
[9/9] phy: lynx-10g: use RCW override procedure for dynamic protocol change
      commit: 2e233235fd463c65188626b9cc5e272c5ee96c07

Best regards,
-- 
Christophe Leroy (CS GROUP) <chleroy@kernel.org>

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

      parent reply	other threads:[~2026-07-30  8:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 23:15 [PATCH v4 phy-next 0/9] RCW override for 10G Lynx dynamic protocol reconfiguration Vladimir Oltean
2026-07-21 23:15 ` [PATCH v4 phy-next 1/9] soc: fsl: guts: perform fsl_guts_init() error teardown in reverse order of setup Vladimir Oltean
2026-07-22  7:18   ` Michael Walle
2026-07-22  7:55     ` Vladimir Oltean
2026-07-22  9:15   ` Ioana Ciornei
2026-07-21 23:15 ` [PATCH v4 phy-next 2/9] soc: fsl: guts: use a macro to encode the DCFG CCSR space Vladimir Oltean
2026-07-21 23:15 ` [PATCH v4 phy-next 3/9] soc: fsl: guts: add a global structure to hold state Vladimir Oltean
2026-07-21 23:15 ` [PATCH v4 phy-next 4/9] soc: fsl: guts: add a central fsl_guts_read() function Vladimir Oltean
2026-07-21 23:15 ` [PATCH v4 phy-next 5/9] soc: fsl: guts: make it easier to determine on which SoC we are running Vladimir Oltean
2026-07-21 23:16 ` [PATCH v4 phy-next 6/9] soc: fsl: guts: make fsl_soc_data available after fsl_guts_init() Vladimir Oltean
2026-07-22  9:19   ` Ioana Ciornei
2026-07-21 23:16 ` [PATCH v4 phy-next 7/9] dt-bindings: fsl: layerscape-dcfg: define DCFG_DCSR region Vladimir Oltean
2026-07-21 23:16 ` [PATCH v4 phy-next 8/9] soc: fsl: guts: implement the RCW override procedure Vladimir Oltean
2026-07-22 11:01   ` Ioana Ciornei
2026-07-21 23:16 ` [PATCH v4 phy-next 9/9] phy: lynx-10g: use RCW override procedure for dynamic protocol change Vladimir Oltean
2026-07-22 11:03   ` Ioana Ciornei
2026-07-24  6:00   ` Vinod Koul
2026-07-23 15:01 ` [PATCH v4 phy-next 0/9] RCW override for 10G Lynx dynamic protocol reconfiguration Vladimir Oltean
2026-07-28 13:47   ` Vladimir Oltean
2026-07-28 15:30     ` Christophe Leroy (CS GROUP)
2026-07-30  8:14 ` Christophe Leroy (CS GROUP) [this message]

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=178539922189.574381.6258263697994334139.b4-ty@kernel.org \
    --to=chleroy@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ioana.ciornei@nxp.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mwalle@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=tanjeff.moos@westermo.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox