From: Andrew Lunn <andrew@lunn•ch>
To: Angelo Dureghello <angelo@kernel-space•org>
Cc: netdev@vger•kernel.org
Subject: Re: mv88e6321, dual cpu port
Date: Mon, 9 Jan 2023 22:33:31 +0100 [thread overview]
Message-ID: <Y7yIK4a8mfAUpQ2g@lunn.ch> (raw)
In-Reply-To: <5a746f99-8ded-5ef1-6b82-91cd662f986a@kernel-space.org>
On Mon, Jan 09, 2023 at 09:40:06PM +0100, Angelo Dureghello wrote:
> Hi All,
>
> using kernel 5.4.70,
> just looking for confirmation this layout
> can work:
>
> eth0 -> cpu port (port5, mii) bridging port3 and 4
> eth1 -> cpu port (port6, rgmii) bridging port0, 1, 2
>
> My devicetree actaully defines 2 cpu ports, it seems
> to work, but please let me know if you see any
> possible issue.
Dual CPU ports is not supported with 5.4.70. Everything will go over
the first cpu port in DT.
Andrew
next prev parent reply other threads:[~2023-01-09 21:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 20:40 mv88e6321, dual cpu port Angelo Dureghello
2023-01-09 21:33 ` Andrew Lunn [this message]
2023-01-10 10:23 ` Angelo Dureghello
2023-01-10 22:22 ` Vladimir Oltean
2023-01-10 23:02 ` Andrew Lunn
2023-01-23 8:52 ` Angelo Dureghello
2023-01-23 11:28 ` Vladimir Oltean
2023-01-23 13:26 ` Angelo Dureghello
2023-01-23 19:18 ` Vladimir Oltean
2023-01-23 20:08 ` Andrew Lunn
2023-01-24 7:21 ` Angelo Dureghello
2023-01-24 11:41 ` Vladimir Oltean
2023-01-24 13:57 ` Andrew Lunn
2023-01-25 9:04 ` Angelo Dureghello
2023-02-06 10:43 ` Angelo Dureghello
2023-02-06 13:24 ` Andrew Lunn
2023-02-16 11:20 ` Angelo Dureghello
2023-02-16 12:50 ` Vladimir Oltean
2023-02-16 12:59 ` Andrew Lunn
2023-02-16 15:31 ` Vladimir Oltean
2023-02-16 18:39 ` Angelo Dureghello
2023-02-18 13:30 ` Vladimir Oltean
2023-02-18 13:56 ` Russell King (Oracle)
2023-02-16 14:24 ` Angelo Dureghello
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=Y7yIK4a8mfAUpQ2g@lunn.ch \
--to=andrew@lunn$(echo .)ch \
--cc=angelo@kernel-space$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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