public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Benjamin Larsson <benjamin.larsson@genexis.eu>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Christian Marangi <ansuelsmth@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, Xuegang Lu <xuegang.lu@airoha.com>
Subject: Re: [PATCH net-next 00/10] net: airoha: Support multiple net_devices connected to the same GDM port
Date: Mon, 30 Mar 2026 10:07:46 +0200	[thread overview]
Message-ID: <acovUgndujK08H-4@lore-desk> (raw)
In-Reply-To: <a64e0f7e-7073-4355-a3de-e8d93e2c795c@genexis.eu>

[-- Attachment #1: Type: text/plain, Size: 4580 bytes --]

> Hi.

Hi Ben,

> 
> On 29/03/2026 15:07, Lorenzo Bianconi wrote:
> > EN7581 or AN7583 SoCs support connecting multiple external SerDes (e.g.
> > Ethernet or USB SerDes) to GDM3 or GDM4 ports via a hw multiplexer that
> > manages the traffic in a TDM manner.
> 
> I think the word for this is arbiter. I think the common use of mux is as a
> more fixed data path selector.


ack, I will fix it in v2.

Regards,
Lorenzo

> 
> > As a result multiple net_devices can
> > connect to the same GDM{3,4} port and there is a theoretical "1:n"
> > relation between GDM ports and net_devices.
> >
> >             ┌─────────────────────────────────┐
> >             │                                 │    ┌──────┐
> >             │                         P1 GDM1 ├────►MT7530│
> >             │                                 │    └──────┘
> >             │                                 │      ETH0 (DSA conduit)
> >             │                                 │
> >             │              PSE/FE             │
> >             │                                 │
> >             │                                 │
> >             │                                 │    ┌─────┐
> >             │                         P0 CDM1 ├────►QDMA0│
> >             │  P4                     P9 GDM4 │    └─────┘
> >             └──┬─────────────────────────┬────┘
> >                │                         │
> >             ┌──▼──┐                 ┌────▼────┐
> >             │ PPE │                 │   MUX   │
> >             └─────┘                 └─┬─────┬─┘
> >                                       │     │
> >                                    ┌──▼──┐┌─▼───┐
> >                                    │ ETH ││ USB │
> >                                    └─────┘└─────┘
> >                                     ETH1   ETH2
> 
> A more representative picture is like the following and in the GDM2 path
> there is a real mux present(not relevant for this patch series though). Thus
> I think it is important to have the distinction between mux and arbiter.
> (Feel free to reuse the following illustration freely).
> 
>                 ┌─────────────────────────────────┐
>                 │                                 │    ┌──────┐
>    ┌─────────┐  │                         P1 GDM1 ├────►MT7530│
>    │   MUX   ├──│ P2 GDM2                         │    └──────┘
>    └─┬─────┬─┘  │                                 │      ETH0 (DSA conduit)
>      │     │    │                                 │
>   ┌──▼──┐┌─▼───┐│              PSE/FE             │
>   │ PON ││ PON ││                                 │
>   └─────┘└─────┘│                                 │
>    ETH5   XPON  │                                 │    ┌─────┐
>                 │                         P0 CDM1 ├────►QDMA0│
>                 │  P4      P3 GDM3        P9 GDM4 │    └─────┘
>                 └──┬──────────┬──────────────┬────┘
>                    │          │              │
>                 ┌──▼──┐  ┌────▼────┐    ┌────▼────┐
>                 │ PPE │  │   ARB   │    │   ARB   │
>                 └─────┘  └─┬─────┬─┘    └─┬─────┬─┘
>                            │     │        │     │
>                         ┌──▼──┐┌─▼───┐ ┌──▼──┐┌─▼───┐
>                         │PCIE0││PCIE1│ │ ETH ││ USB │
>                         └─────┘└─────┘ └─────┘└─────┘
>                           ETH3   ETH4    ETH1   ETH2
> 
> MvH
> Benjamin Larsson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

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

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-29 13:07 [PATCH net-next 00/10] net: airoha: Support multiple net_devices connected to the same GDM port Lorenzo Bianconi
2026-03-29 13:07 ` [PATCH net-next 01/10] dt-bindings: net: airoha: Add EN7581 ethernet-ports properties Lorenzo Bianconi
2026-03-29 13:07 ` [PATCH net-next 02/10] net: airoha: Rely on net_device pointer in airoha_dev_setup_tc_block signature Lorenzo Bianconi
2026-03-29 13:07 ` [PATCH net-next 03/10] net: airoha: Rely on net_device pointer in HTB callbacks Lorenzo Bianconi
2026-03-29 13:07 ` [PATCH net-next 04/10] net: airoha: Rely on net_device pointer in ETS callbacks Lorenzo Bianconi
2026-03-29 13:07 ` [PATCH net-next 05/10] net: airoha: Introduce airoha_gdm_dev struct Lorenzo Bianconi
2026-03-29 13:07 ` [PATCH net-next 06/10] net: airoha: Move airoha_qdma pointer in " Lorenzo Bianconi
2026-03-29 13:07 ` [PATCH net-next 07/10] net: airoha: Rely on airoha_gdm_dev pointer in airhoa_is_lan_gdm_port() Lorenzo Bianconi
2026-03-29 13:07 ` [PATCH net-next 08/10] net: airoha: Support multiple net_devices for a single FE GDM port Lorenzo Bianconi
2026-03-29 13:07 ` [PATCH net-next 09/10] net: airoha: Do not stop GDM port if it is shared Lorenzo Bianconi
2026-03-29 13:08 ` [PATCH net-next 10/10] net: airoha: Rename get_src_port_id callback in get_sport Lorenzo Bianconi
2026-03-29 13:40 ` [PATCH net-next 00/10] net: airoha: Support multiple net_devices connected to the same GDM port Benjamin Larsson
2026-03-30  8:07   ` Lorenzo Bianconi [this message]
2026-03-29 17:36 ` Jakub Kicinski
2026-03-30  8:08   ` Lorenzo Bianconi

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=acovUgndujK08H-4@lore-desk \
    --to=lorenzo@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=benjamin.larsson@genexis.eu \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    --cc=xuegang.lu@airoha.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