U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Jardin <vjardin@free.fr>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: u-boot@lists.u-boot-project.org, Peng Fan <peng.fan@nxp.com>,
	Tom Rini <trini@konsulko.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Wasim Khan <wasim.khan@nxp.com>,
	Priyanka Jain <priyanka.jain@nxp.com>,
	Meenakshi Aggarwal <meenakshi.aggarwal@nxp.com>,
	Ioana Ciornei <ioana.ciornei@nxp.com>
Subject: Re: [PATCH v4 09/10] doc: lx2160a: document the sd1 hwconfig option
Date: Tue, 29 Sep 2026 00:13:37 +0200	[thread overview]
Message-ID: <arrmkcl3utxe2X8E@L30177.local> (raw)
In-Reply-To: <20260928151032.uwtmyj75xics6viz@skbuf>

Hi Vladimir,

> > +		mode        dpmac.2 port   dpmac.1 port
> > +		2x100g      100GE          100GE
> > +		100g4x25g   100GE          4x 25G: dpmac.3 to dpmac.6
> > +		2x40g       40GE           40GE
> > +		40g4x10g    40GE           4x XFI: dpmac.3 to dpmac.6
> > +		100g4x10g   100GE          4x XFI: dpmac.3 to dpmac.6
> 
> How much do you plan to extend this, really?

That's it. They are the 5 scenarios I am interested in for my use cases.
I did briefly try some others split of the first 4 lanes instead of 100G
and 40G, it seems workable.

I'll leave those to who ever needs it.

> Do you ever plan to support a mode with multiple 'from' modes?
> 
> Like for example, 100g4x25g can come either from 2x100g, or from 100g4x10g.
> The sd1_enter() recursion and graph traversal becomes quite a bit more
> complicated.

I do not think it is needed starting from a uboot/boot settings.
At the current states, SD1 is always from RCW 13 (or 20).
It means that sd1 cannot be in 100G+4x10G when 100G+4x25G is requested.

> But in principle, there's nothing saying you can transition to one
> SerDes protocol just from a single source. In that sense, I think your
> choices are rather arbitrary and may not suit everyone, so talking about
> multiple sources now seems rather adequate.

I guess you are right that more transitions should be possible, but I'd
like to leave those for a later design. I guess, based on the current
user uboot shell and env/hwconfig, we can still reshuffle it later for
more scenarios.

best regards,
  Vnincent

  reply	other threads:[~2026-09-28 22:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 10:13 [PATCH v4 00/10] board: lx2160a: runtime SD 1 lane configuration for LX2160A boards Vincent Jardin
2026-09-28 10:13 ` [PATCH v4 01/10] board: lx2160a: serdes: drop the split subcommand Vincent Jardin
2026-09-28 11:17   ` Vladimir Oltean
2026-09-28 10:13 ` [PATCH v4 02/10] board: lx2160a: serdes: rename serdes1:split to serdes1:100g4x25g Vincent Jardin
2026-09-28 11:18   ` Vladimir Oltean
2026-09-28 10:13 ` [PATCH v4 03/10] board: lx2160a: serdes: set SD1 with a table Vincent Jardin
2026-09-28 12:02   ` Vladimir Oltean
2026-09-28 10:13 ` [PATCH v4 04/10] board: lx2160a: serdes: report unknown SD1 cases Vincent Jardin
2026-09-28 14:29   ` Vladimir Oltean
2026-09-28 10:13 ` [PATCH v4 05/10] board: lx2160a: serdes: no SD1 config once MC runs Vincent Jardin
2026-09-28 14:50   ` Vladimir Oltean
2026-09-28 10:13 ` [PATCH v4 06/10] board: lx2160a: serdes: add serdes1:2x40g Vincent Jardin
2026-09-28 10:13 ` [PATCH v4 07/10] board: lx2160a: serdes: add serdes1:40g4x10g Vincent Jardin
2026-09-28 10:13 ` [PATCH v4 08/10] board: lx2160a: serdes: add serdes1:100g4x10g Vincent Jardin
2026-09-28 10:13 ` [PATCH v4 09/10] doc: lx2160a: document the sd1 hwconfig option Vincent Jardin
2026-09-28 15:05   ` Vladimir Oltean
2026-09-28 15:10   ` Vladimir Oltean
2026-09-28 22:13     ` Vincent Jardin [this message]
2026-09-28 10:13 ` [PATCH v4 10/10] board: nbxv3: apply sd1 hwconfig before MC starts Vincent Jardin
2026-09-28 15:07   ` Vladimir Oltean
2026-09-28 19:14 ` [PATCH v4 00/10] board: lx2160a: runtime SD 1 lane configuration for LX2160A boards Tom Rini
2026-09-28 20:59   ` Vincent Jardin
2026-09-28 21:15     ` Tom Rini

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=arrmkcl3utxe2X8E@L30177.local \
    --to=vjardin@free.fr \
    --cc=hemant.agrawal@nxp.com \
    --cc=ioana.ciornei@nxp.com \
    --cc=meenakshi.aggarwal@nxp.com \
    --cc=peng.fan@nxp.com \
    --cc=priyanka.jain@nxp.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.u-boot-project.org \
    --cc=vladimir.oltean@nxp.com \
    --cc=wasim.khan@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